[Error] Getting invalid TCPdump header when running pcap about bitnodes HOT 8 CLOSED

@Kulgar Can you upload the .pcap file that causes the error above?

from bitnodes.

Sure thing :)

1530680517.eth0.pcap.txt

I had to rename it (added txt extension) because Github isn't supporting "pcap" extension for uploads.

While searching the web about this error I found this discussion: https://stackoverflow.com/questions/23523524/dpkt-invalid-tcpdump-header-error

I think that is what happens here, but I am not sure.

from bitnodes.

How was 1530680517.eth0.pcap.txt generated? It does not look like pcap file.

from bitnodes.

@ayeowch
Well I used the commands from the wiki:

sudo tcpdump -i eth0 -w %s.eth0.pcap -v -n -G 2 -B 65536 -Z [USERNAME] 'tcp and not src host [IP_ADDRESS] and not src host [IPV6_ADDRESS]' > eth0 2>&1 &
sudo tcpdump -i lo -w %s.lo.pcap -v -n -G 2 -B 65536 -Z [USERNAME] 'tcp and port 9050' > lo 2>&1 &

How can you tell that it is not a pcap file?
And why would these commands generate a none pcap file?

from bitnodes.

@Kulgar What OS are you running the command on?

from bitnodes.

Ubuntu 18.04 Bionic

from bitnodes.

@Kulgar Can you email me the pcap file again? Maybe the upload/download from github is messing with the content. Also, I assume you have the same tcpdump version?

$ tcpdump --version
tcpdump version 4.9.2
libpcap version 1.8.1
OpenSSL 1.1.0g  2 Nov 2017

from bitnodes.

Yeah I have the same version.

That's strange, I was trying to reproduce the bug by restarting all the processes... But it seems to work properly now.

Well... I hope I did not bother you too much.
If it happens again I'll send you the faulty pcap file by mail.

Thanks for your patience and kindness

from bitnodes.