No DHCP response (Multiple VLAN setup)

[mhanna]

@Tom-Elliott

I’ll double check all my firewall rules and routing one more time to make sure I didnt miss something there. If I find nothing I’ll do as suggested and report my finding.

[mhanna]

@Tom-Elliott said in No DHCP response (Multiple VLAN setup):

isdebug=yes

Ok, I’ve verified I have no firewall rules at all in place that would block clients that are both on the 192.168.91.x subnet from communicating. Where is exactly do I add the isdebug=yes… in the boot options for the registration? If so are the options comma seperated? Once added what are my next steps?

[Tom Elliott]

@mhanna they’re space separated.

The “easiest” but applies to ALL things (menu, taskings, etc…) would be to add isdebug=yes to:

FOG Configuration Page->FOG Settings->General Settings->FOG_KERNEL_ARGS

Save and restart your client machine and you should see it load into debug mode (after failing to do the ip stuff).

[mhanna]

@Tom-Elliott

Ok, I am sitting at debug windows now… any steps you suggest I perform. ifconfig looks as it should. Its on the same vlan as fog server with correct netmask. No errors, no drops.

[Tom Elliott]

@mhanna Can you run:
curl -Ifso /dev/null http://fogserverip/fog/management/index.php --connect-timeout 5

Change fogserverip with your fogserver’s IP address.

What comes back?

[mhanna]

@Tom-Elliott

The command executed. Didn’t generate anything… just ran and nothing. I’m not able to ping from the client to fog server or the other way around. Which is odd because I can ping from the fog serve to every other IP on the VLAN that I’ve attempted.

[Tom Elliott]

@mhanna But ifconfig returns with a valid IP Address?

You could try:

udhcpd -i eth0 (I don’t remember the syntax off the top of my head sorry).

[george1421]

@Tom-Elliott While I understand this will not help right now. I was able to duplicate this condition in my home dev environment last week. I was able to also correct it, it was simple and stupid. I’m sure I communicated with you via chat what I found. But at this point I can’t remember for the life of me what it was.

I was using a virtual box vm and pxe booting it going to test either uefi of dnsmasq and I got that boot loop in FOS. It was a fos thing where it would get the address and then deallocate it and then try again, eventually giving up with the message the OP posted.

[mhanna]

@Tom-Elliott

Yes, valid IP and netmask.

[Tom Elliott]

@mhanna now if you run the curl command followed immediately by:

echo $? it should print a number

[mhanna]

@Tom-Elliott

I added to the end of the curl command you sent me and it still just drops me back at the command line with no output.

[Tom Elliott]

@mhanna so you did:

curl request
echo $?

Or you did:

curl request echo $?

The first form is what I mean sorry for the confusion.

[mhanna]

@Tom-Elliott

Sorry, I did the second… after doing it the correct way the number 7 was returned.

[Tom Elliott]

@mhanna Well your ping command seems to indicate an issue here as well.

And for reference:

CURLE_COULDNT_CONNECT (7)

Failed to connect() to host or proxy.

So both sides seem to point in the same direction. For whatever reason, this vlan is not able to locally communicate.

[Tom Elliott]

Useful for all I suppose:

Curl Error List is found here.

[mhanna]

@Tom-Elliott

Based on what I see that would appear to be the case… except I know its not the case. When the system is pxe booting I am able to ping from the fog server to the client. While at the main fog menu I am able to ping from fog server to client. The moment I select full host registration I am no longer able to ping from fog server to client.

[george1421]

@mhanna said in No DHCP response (Multiple VLAN setup):

When the system is pxe booting I am able to ping from the fog server to the client. While at the main fog menu I am able to ping from fog server to client.

This is because the iPXE (fog menu kernel is running at this point in the booting process)

The moment I select full host registration I am no longer able to ping from fog server to client.

At this point, the FOS engine is running and not able to pick up (or think’s it can’t pick up) a dhcp address.

[mhanna]

@george1421

Understood. I was trying to illustrate that there did not appear to be a communication issue between devices on the vlan in question by stateing that they communicate just fine up to a certain point.

[Tom Elliott]

The question here, is more about if the client can ping the FOG Server.

When you are at the FOG PXE Menu, IP Helpers within the route help direct the traffic on where to get an IP Address. This will typically work, but requires the route be accessible by the FOG Server. The Same, however, path must be setup in reverse.

So it’s fully possible to enable a DHCP server to receive dhcp, but the client side receiving that IP still needs a way to communicate to the fog server.

You’re certain the iPXE IP Address issued is the same scope the FOS Engine is receiving?

I ask the questions because, you state the FOG Server can ping the host machine when it’s in PXE mode, but in the FOS System, it’s unable to communicate to the Client Machine anymore. This leads me to think it’s getting an IP Address that can’t route anywhere.

[mhanna]

@Tom-Elliott said in No DHCP response (Multiple VLAN setup):

the host machine when it’s in PXE mode, but in the FOS System, it’s unable to communicate to the Client Machine anymore. This leads me to think it’s getting an IP Address that can’t route anywhere.

Its getting the same IP in PXE mode as it is when I select the option to register host. They exact same IP. Which is in the same vlan as the fog server… they are actually only 1 IP apart. I can have a continuous ping going and from the FOG server I can get replies up to the point there I select the register host option. At that point the replies stop. I can then reboot the client and once it start the PXE boot process the pings start replying again… from the same IP. Its really odd… while in PXE it gets DHCP with all the correct information… but once we go anywhere in the Fog menu we lose all connectivity. When running the route command on the client once in debug I see the following:

Destination Gateway Genmask
default 192.168.91.193 0.0.0.0
192.168.91.192 * 255.255.255.192

192.168.91.193 is the correct gateway for this vlan but is unpingable from the client at this point.