PXE Boot Problem - bzImage Connection Reset

[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!

[Sebastian Roth]

@sanman Well done. Thanks for letting us know. Might be helpful for other users as well. Marking this solved.