PXE Boot Problem - bzImage Connection Reset

[maciej12203]

@george1421
I have had some time and I went to the room where the server was placed and I looked at the code you asked.
Everything looks good but maybe you better look it over. I enclose the whole code.

#!ipxe
set fog-ip 192.168.4.70
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
cpuid --ext 29 && set arch x86_64 || set arch i386
goto get_console
:console_set
colour --rgb 0x00567a 1 ||
colour --rgb 0x00567a 2 ||
colour --rgb 0x00567a 4 ||
cpair --foreground 7 --background 2 2 ||
goto MENU
:alt_console
cpair --background 0 1 ||
cpair --background 1 2 ||
goto MENU
:get_console
console --picture http://192.168.4.70/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console
:MENU
menu
colour --rgb 0xff0000 0 ||
cpair --foreground 1 1 ||
cpair --foreground 0 3 ||
cpair --foreground 4 4 ||
item --gap Host is NOT registered!
item --gap -- -------------------------------------
item fog.local Boot from hard disk
item fog.memtest Run Memtest86+
item fog.reginput Perform Full Host Registration and Inventory
item fog.reg Quick Registration and Inventory
item fog.deployimage Deploy Image
item fog.multijoin Join Multicast Session
item fog.sysinfo Client System Information (Compatibility)
choose --default fog.local --timeout 3000 target && goto ${target}
:fog.local
sanboot --no-describe --drive 0x80 || goto MENU
:fog.memtest
kernel memdisk initrd=memtest.bin iso raw
initrd memtest.bin
boot || goto MENU
:fog.reginput
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.4.70/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.4.70:/images/ storageip=192.168.4.70 loglevel=4 mode=manreg
imgfetch init_32.xz
boot || goto MENU
:fog.reg
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.4.70/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.4.70:/images/ storageip=192.168.4.70 loglevel=4 mode=autoreg
imgfetch init_32.xz
boot || goto MENU
:fog.deployimage
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.multijoin
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param sessionJoin 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fog.sysinfo
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.4.70/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.4.70:/images/ storageip=192.168.4.70 loglevel=4 mode=sysinfo
imgfetch init_32.xz
boot || goto MENU
:bootme
chain -ar http://192.168.4.70/fog/service/ipxe/boot.php##params ||
goto MENU
autoboot

[george1421]

@maciej12203 said in PXE Boot Problem - bzImage Connection Reset:

192.168.4.70

Is this the IP address of your fog server?

[maciej12203]

@george1421 Yes, this is a statically set address

[Sebastian Roth]

@maciej12203 As the kernel (bzImage) is being downloaded via HTTP by iPXE could you please check the apache error logs. See my signature on where to find the log on your FOG server.

[maciej12203]

@Sebastian-Roth
Thank you for your hint. I will definitely check.
And when logs do not show anything.
@george1421 Are there any other suggestions that could still be checked on the server side?

[sanman]

I would like to add that I just did a fresh install of fog 1.4 on Ubuntu 16.04 and this same issue is happening. I made a static bond interface then installed fog. The register didn’t work so left it over night and the next day it was working. Now today (a week later) it is giving the same error. My apache error log is also blank. My bzimage gets to 99% then I receive error that the connection reset. I will be happy to provide any info you need.

I have used fog for years and this is the first time I have an issue I can’t fix.

[maciej12203]

@sanman
I see we have a similar problem. I also reinstalled the server, but the problem is still the same.
However, there may be someone who has an idea how to solve the problem. I recently used FOG server, installed it on my home network and everything worked as it should. When I moved my idea to the school network came the problem.

[Tom Elliott]

Please check FOG Configuration Page->FOG Settings->General Settings-FOG_WEB_ROOT

Set to /fog/ and this should be corrected for. I’m guessing the connection reset came from the 401/403 error being presented to something missed in the Schema settings. This would typically happen on “fresh” installs and shouldn’t have impacted already working systems.

[maciej12203]

@Tom-Elliott
In configuration after installing FOG server there was nothing to change. I’m pretty sure that FOG_WEB_ROOT is set to / fog / . Is it possible that the server itself has some options?
I have installed many times a server in my environment either virtual or physical, and somehow there was no problem with different options for FOG server side setting .

Probably you are right, because I noticed that it gets access to the GUI just as I enter - http://192.168.4.70/fog/
When I enter http://192.168.4.70 or http://192.168.4.70/ unfortunately, the GUI will not trigger.
Of course I do not know myself so well and I will check this option when I have access to the server.

[maciej12203]

I checked everything and was configured correctly. The server still did not work as it should, so I decided to install FOG server again. Maybe I made some mistake when installing the server. I have one more question as to its installation to be 100 percent sure.
I did not want to set up a separate topic so I’m asking a question here. I found on the Wiki page information about how to install for the type of network. Which is not too much access to change anything because it is in the school server to which it does not have access.
All the computers in the room are connected to the switch, the switch itself on the router in the server room.
The network already exists for a year and is fully operational.

What type of installation would you like to do? [N] n

What is the IP address to be used by this FOG Server? [current address]192.168.4. 70 ( Static Address )

Would you like to setup a router address for the DHCP server? [Y/n] n

Would you like to setup a DNS address for the DHCP server and client boot image? [Y/n] n

Would you like to change the default network interface from eth0?
If you are not sure, select No. [y/N] n

Would you like to use the FOG server for dhcp service? [Y/n] Y

Thank you for your help.

[george1421]

@maciej12203 Lets take a step back here.

Does your network have an existing dhcp server?
If so are you allowed to make adjustments to this dhcp server?
Is your FOG server on a different subnet than your pxe booting client computers?

[maciej12203]

@george1421

1. The network is running a DHCP server and assigns IP addresses.
2. I have no rights or access to modify this server.
3. The FOG server is on the same subnet as the PXE boot clients

[george1421]

@maciej12203 OK now we have something we can work with.

Since your have an existing dhcp server you do not want to run a FOG dhcp server because you will get conflicts.

If you can not modify the dhcp server configuration or request that the configuration can be changed we still have a way to make this work. On your fog server DO NOT enable the dhcp server, that will only cause you a head ache with the clients.

Since your FOG server and pxe booting clients are on the same subnet we will use dnsmasq to provide ProxyDHCP information for your location. The ProxyDHCP will supply the missing information that your main dhcp server can not provide. This ProxyDHCP server will supply the boot file and pxe booting server information to your clients.

Understand that running a ProxyDHCP server is a last choice option. The best solution is to get your dhcp server configured properly. I understand there are conditions where you can not do this, that is why FOG supports ProxyDHCP (dnsmasq) configurations.

[maciej12203]

@george1421 So I know how it all works and what is DNSMASQ.
I tested this at home and everything was fine. When I tried to move it to the existing network at school, problems began to appear, which until now have not resolved. At first, after configuring FOG and DNSMASQ, clients could call the menu where they had options to choose , what I wrote about before.
Unfortunately today I checked the effect without any previous changes and I got the error as in the picture.

[george1421]

@maciej12203 Sorry i read too many threads to remember where we are in each one.

I remember this now your FOG server is rejecting the http request.

two things come to mind

1. Your http server is not running.
2. You have your linux firewall still running.
3. (I guess) someone forgot to switch selinux to permissive.

I would test from a windows browser see if you can connect to http://192.168.4.70/fog/service/ipxe/boot.php
I’m interested in if anything is returned.

[george1421]

@george1421 Never mind we already did this down below in the thread.

[george1421]

@george1421 Next steps: https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

But for you I want you to use this filter: tcpdump -w output.pcap port 67 or port 68 or port 69 or port 4011 or port 80

capture the pcap file and upload it here. I want to find out exactly what the client is being told to do. I feel you have something in your business environment that is causing strange reactions from the client.

[maciej12203]

This post is deleted!

[sanman]

@george1421 Since I think I’m having the same issue and don’t want to create a new thread, here is my pcap. This capture is during registration. bzimage gets to 99% and then times out with a connection reset error. If you think this a different problem, I’ll create a new thread. The pcap is too large to upload so here is a link to download it (7.6mb).

Download PCAP

[sanman]

So I think I figured it out in my case. We have a MX64 Firewall (Meraki) and after getting off of tech support with them they recommended I turn off AMP (Malware Protection). After doing this everything started working perfect. Hope this helps!