Posts made by mhanna

@Tom-Elliott

The IP the machine is getting both in PXE and when selecting any menu option is 192.168.91.242… within the specified range for that vlan. FOG server is on 192.168.91.243. No, the nic is an onboard broadcom nic on a dell optiplex 580

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

55.255.255.192

It is supposed to be .192. This is also reflected on the fog server as well as all DHCP clients on that vlan.

@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.

@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

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.

@Tom-Elliott

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

@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

Yes, valid IP and netmask.

@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

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

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.

@Tom-Elliott

Yes, when watching the information scroll up the screen I can see the line where it indicates lease of 192.168.91.x was obtained… this is the same vlan/network on which the Fog server is located. It then shows it is deleting routers and then adding the DNS servers on the 172.30.1.x VLAN. It then goes right back to udhcpc: started and begins the loop again.

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

f the 1.4.0-RC-9.3? There was work in

I upgraded as suggested and the behavior is identical… nothing changed that I can see.

Server

• FOG Version: 1.3.5
• OS: CentoOS 7

Description

Here is the situation I am having… I’ve been scouring the internet for a few days now with no luck solving so I’m hoping someone can point me in the right directions. I have a network with 3 vlans each with a different network. I have routers in place that route between the vlans/networks just fine. I previously had Fog 1.20 running on Ubuntu just fine with this setup but I stood up a new Fog server on CentOS and am having an odd issues I cant figure out. The Fog server is on a vlan/network 192.168.91.X. There is a Windows DHCP server on this VLAN that dishes out IP’s just fine. Clients on this VLAN are given DNS servers in the 172.30.10.X VLAN and all clients can access DNS just fine. I’ve setup DHCP option 66 and 67 as specified and clients pxe boot into the Fog menu just fine. Just to clarify the clients are on the 192.168.91.x vlan (same vlan as Fog server). The issues start when I try to do anything from this point on. For example when doing a full host registration there are multiple lines of udhcpc stating that a lease of 192.168.91.x was obtained. Followed deleting routers, adding dns 172.30.1.x. After this it goes to sending discover and sending select for the IP which was obtained by DHCP. At this point the whole process starts again and it just keeps looping until it finally bugs out and says no DHCP response on interface eth0. I’m not really sure where the issue is or what to look at so any friendly pointers in the right direction would be appreciated.