proxyDHCP Issue

[Wayne Workman]

@Exig3nci Did you get the file transferred? When you have ProxyDHCP issues, you’re number one tool is TCPDump and Wireshark.

[Exig3nci]

@Wayne-Workman Thanks again Wayne, wish I could focus on this project, but I’m also busy with HelpDesk tickets. Sorry for the late reply, but I managed to get the file to my windows 7 PC, but I keep getting this error when I open the file.

[Wayne Workman]

@Exig3nci said:

I keep getting this error when I open the file.

I’ve gotten that error the last time I tried to do a TCPDump at home with a dnsmasq issue… That was maybe two weeks ago.

Because you too have gotten this error, it leads me to think that either something about dnsmasq changed or something about Wireshark changed, or something about TCPDump changed - and I doubt that TCPDump changed - and I doubt that dnsmasq changed…

I see you’re using the latest version of Wireshark. Could you try an older version? Maybe 6 months older?

[Exig3nci]

@Wayne-Workman unfortunately the issue is still the same.
Is there a way to cap the file when using TCPdump? I’ve tried -s 65535 but I still get the same result.

[Wayne Workman]

@Exig3nci Not ignoring you, just thinking about the issue and problems.

[cml]

https://ask.wireshark.org/questions/8931/capture-file-appears-to-be-damaged-or-corrupt

Maybe the issue is tftp defaulting to ASCII? Can you try transfering it with WinSCP?

Or try using binary mode?

tftp -i x.x.x.x get issue.pcap

From: https://technet.microsoft.com/en-us/library/Ff698993.aspx?f=255&MSPPError=-2147217396

[Wayne Workman]

@cml I tested that this works in Win 7 and have updated the “Troubleshoot TFTP” article to reflect binary only.

[Exig3nci]

@Wayne-Workman thanks for the updated
@cml I’ve followed that step, but I still get the same issue.

[Wayne Workman]

@Exig3nci Try setting the maximum packet size via TCPDump to exactly what the error says…

262144

Then after you do a capture with that setting and put the file in the /tftpboot directory, make sure you use binary mode to transfer via TFTP.

You might also try some older versions of WireShark https://www.wireshark.org/download/win32/all-versions/

[Exig3nci]

@Wayne-Workman So I have an older version of WireShark (1.10.4) I’ve set tftp in binary mode:
tftp
tftp> binary
Ran this command:
sudo tcpdump -w issue.pcap -i eth0 -c 65535
But I still get the same issue, The packet limit error on WireShark is capped at 65535, but the command in Ubuntu still runs.
Am I doing this correct? I have to break the command with Ctrl+C to get it to stop and it still goes over by many bytes.

[Exig3nci]

@Wayne-Workman I’m also just trying to run WireShark on my VM nic cards from my Windows 7 machine, think that will work?

[Wayne Workman]

@Exig3nci said:

@Wayne-Workman I’m also just trying to run WireShark on my VM nic cards from my Windows 7 machine, think that will work?

At this point, it’s worth a shot for sure.

[Wayne Workman]

@Exig3nci I’ve been thinking, and I think it would be worth the time to try to transfer the pcap file via FTP instead of TFTP just to see if it makes a difference or not.

Can you please place the pcap file inside of your /images directory and then try to get the file following the instructions found here: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP

[Exig3nci]

@Wayne-Workman Yeah, still no luck.
Although I got another error message PXE-E32.
What does your tftp-hpa file look like?

[Wayne Workman]

@Exig3nci There is an example here: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_TFTP#Ubuntu:

[Exig3nci]

@Wayne-Workman I’ve been following the website you forwarded to me, but I keep getting the 425 error with ftp.
I can exchange files via tftp just fine. I’m able to connect to ftp://ipaddress as well.
I’ve changed both the tftp conf file, the ftp conf file, changed permissions, and firewall is turned off, but I still get the same error.
Any advice?

[Wayne Workman]

None of this is making any sense anymore.

Please check to see if options 066 and 067 are already set on your switches that handle DHCP.

Please check for IP conflicts with your FOG server.

[Wayne Workman]

@Exig3nci Also,

Please load a Linux Live CD and try DHCPDump. I just found it through some searching and I think that this is exactly what you need to troubleshoot your issue.

http://www.cyberciti.biz/faq/linux-unix-dhcpdump-monitor-dhcp-traffic/

I found this in the WiKi, might be worth looking over… https://wiki.fogproject.org/wiki/index.php/Not_passing_PXE,_or_ProxyDHCP...NO_PROBLEM_Cisco#Original_Issue

[Exig3nci]

@Wayne-Workman So I got the issue.pcap file to work. It was a matter of putting
tftp -i 10.10.8.155 get issue.pcap instead of
tftp 10.10.8.155 get issue.pcap (Aiii yaaaa )
I’m not seeing any tftp protocols in the wireshark GUI, I’m assuming that it means my tftp config file isn’t setup properly.

[Exig3nci]

@Wayne-Workman Also, I was able to get the undionly.0 file through tftp on my windows 7 machine.