DHCP and FOG
-
This post is deleted! -
Everything looks good even until the last screen shot. iPXE is loading so we know its getting past your dhcp server settings. So we can almost rule out any configuration settings you made to isc-dhcp server.
Your next server in your dhcp server setting is pointing to 10.10.2.65, which is also where iPXE is trying to load the FOG iPXE menu (kick started by default.ipxe). I assume that file is present in /tftpboot and if you view that file from the linux console it also has 10.10.2.65 hard coded into the file? The only way this would get changed/be incorrect is if you changed the IP address of the fog server after FOG was installed.
-
@cary1102 As mentioned in the other thread you need to push the
option routers x.x.x.xto your clients or they won’t be able to reach the server that is in a different subnet. It’s as simple as that!You seem to have already added the option but commented it again. Why? Don’t you have a router/gateway that can forward the traffic between those two subnets?
-
@george1421 The IP of my server has remained the same before and after installation
-
@Sebastian-Roth I will uncomment the option routers and see what I can do. Thank you guys for the help. I will post my solution when I find it.
-
@Sebastian-Roth Thank you for your advice. What you said seemed to be my issue. All I did was uncomment option routers and replace the IP with my DHCP server IP. I can get into the FOG splash screen now. Thanks!