@Uncle-Frank That did it … you fixed it! Awesome! I’m going to start up/down-loading shortly to test everything. Just for future reference, can you share what you changed in the file? Good work you guys are doing here - thank you.
Posts made by mjcrane
-
RE: default.ipxe timeout
-
RE: default.ipxe timeout
@Uncle-Frank Still not working for me. I could see that it’s pointing to 192.168.0.111/default.ipxe but I’m getting the same timeout error. I also made sure Crucible is removed from my environment. Here’s the latest tcpdump in case you need it.issue_151027c.pcap
-
RE: default.ipxe timeout
@Uncle-Frank - I tried this as well as @Wayne-Workman’s Crucible option. Sadly neither worked for me. Then again my knowledge of all this is very limited so I may not have been doing it right! I’m hoping you could look at my tcpdump and help figure out what’s going wrong and how to fix it. I captured this using the original ltsp.conf settings I started with. Thanks in advance guys!
-
RE: default.ipxe timeout
@Wayne-Workman Thanks for replying. I will explore those options when time permits and will get back to the forum with the results. Appreciate your help.
-
RE: default.ipxe timeout
Router’s provided by ISP. Running dnsmasq in Kubuntu 14.04 under VM Workstation.
-
default.ipxe timeout
Please help. I’m getting this message “tftp://192.168.0.1/default.ipxe…” right before a connection timeout. I can see why it’s timing out - that IP is my router. The FOG/tftp server is at 192.168.0.111. On bootup, it appears like undionly.kpxe is being read properly but then the client reverts to the router IP after. Does anyone have any advice on how to fix this? Thanks.