TFTP hangs in PXE boot, resulting in PXE session ending.
-
@Sebastian-Roth Nice.
-
@Sebastian-Roth Ah, it must be our DHCP for our public WiFi! So you think option 66 is active on that? I’ll go check! Hopefully I have access. Thanks so much.
@Wayne-Workman Thanks for the suggestions! Though, all of them were right. So I think Sebastian might be onto something.
-
We have seen home routers sending out option 66 for no reason. I really hope that you can find and stop this device from answering on the LAN altogether.
-
@Sebastian-Roth Hmm… So we could possibly have a rogue AP? I’ll have to ask my coworkers and see if they know anything about it.
-
@Sebastian-Roth Also, as a student of networking I have to ask… How do you go about analyzing PCAP? Can you just open it with Wireshark?
-
@_mateo said:
How do you go about analyzing PCAP? Can you just open it with Wireshark?
Yes.
If you’re hardcore, you use Vi. Or, not even open it and use cat with grep and awk and sed
-
@_mateo said:
How do you go about analyzing PCAP? Can you just open it with Wireshark?
Yes, that’s pretty much all you need to do. Then there is a couple of years experience looking through those dump files but just give it a go and start learning.
-
@Wayne-Workman Haha! Oddly enough, I’ve only ever been taught to navigate and edit .conf files with Vi. I was following a FOG tutorial and was thinking, “What’s this ‘sudo nano’ crap all about?”
@Sebastian-Roth Gotcha! Thanks for your help. Still no word on if there’s a rogue AP/dhcp service running somewhere. I’ll keep you posted.
P.S. I have a community oriented question for you guys. Is it okay to keep posting in the same thread with each issue that comes up as I go along? I figure someone looking for a TFTP or PXE error will stumble across this, but we’ve covered a few different topics. I guess the search engine will be good enough to find keywords, I’m mostly just curious!
