Updated to Fog 7575 TFTP issue
-
Hello,
I wiped my server and started fresh. I installed Fog using SVN so it’s easier to get the latest and greatest. Seems like everything installed correctly. No hiccups. So I created a new image that I wanted to capture from a laptop and didn’t seem to get past the TFTP part. It’s asking for the tftp server address I think? So I tried the server address but didn’t work. Connection timed out. Here’s the link to a picture of it.
https://gyazo.com/6d249327d63e0cd92c6b6c93aae55e5d
https://gyazo.com/54ca945ccfde5754ad147e46d6928b53Hope it’s nothing crazy.
At the top of the Fog page says Fog 7575 and the SVN revision is 5432.
-
I also just read up on this thread but I don’t think it’s the same scenario as mine. https://forums.fogproject.org/topic/7349/fog-boot-menu-only-works-once/18
I’m using the Fog server as my DHCP server.
-
For the TFTP issue, read through this for background: https://forums.fogproject.org/topic/7349/fog-boot-menu-only-works-once/18
But, you may have two DHCP services serving the particular broadcast domain you’re operating within.If you have two, turn one off and properly configure the remaining one. If the remaining one is the fog server, it should be configured for you already. If it’s a Windows DHCP you can configure it via these instructions: https://wiki.fogproject.org/wiki/index.php?title=Modifying_existing_DHCP_server_to_work_with_FOG
Please give us more information about your network and DHCP servers!
-
I think my coworker messed up on the firebox. I believe he has a 10.0.4.X network bleeding into the 192. network. Pretty sure he doesn’t even know he did it, haha. So I’ll get that resolved tomorrow. Even though everything looks like it’s looking at the correct network and grabbing the correct IPs within my range that other DHCP can break the tftp? Because of that’s the case then this is probably solved.
-
@adame Normally, when the TFTP address is asked for, it’s two or more DHCP servers serving one broadcast domain - and one or more of them being improperly configured to support FOG.
To fix THAT issue, turn off the un-needed ones, or properly configure them. Either works.
-
Normally, when the TFTP address is asked for, it’s two or more DHCP servers serving one broadcast domain - and one or more of them being improperly configured to support FOG.
Either that or the DHCP server does not provide next-server information when iPXE is asking for it. This case is kind of unusual because the PXE ROM got the correct info or it wouldn’t be able to load iPXE. But if I remember correctly I have seen a case where a DHCP server would not give next-server to iPXE requesting it (possibly because of the DHCP option iPXE is sending in its request - option 175 that is I think).
-
Tagging this for addition to tftp troubleshooting. wiki
-
This has been added to the wiki here: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_TFTP#Please_enter_tftp_server:
