Comment # 11
on bug 10366
from Guy Harris
(In reply to rosc from comment #10)
> (In reply to Evan Huus from comment #9)
> > If dumpcap works then the GUI probably has everything to do with it - the
> > packets are likely being captured, they're just not showing up in the UI for
> > some reason.
> >
> > If you do a GUI capture on eth0 (the one that doesn't work) then check the
> > tmp capture files, are the packets actually being captured? Can you open
> > that capture file after-the-fact in wireshark?
>
> It creates a file in /tmp, with this:
>
> Linux 3.12.17a
> Dumpcap 1.12.0 (Git Rev Unknown from unknown)
> eth0
> port 80
> Linux 3.12.17a
That could be an Interface Description Block in a pcap-ng file, in which case
it's not a text file and has other binary data in it.
What does the "file" command report when you run it on the file?
What happens if you try to open it with Wireshark?
> No filters are set.
I.e., you didn't specify a capture filter of "port 80"?
You are receiving this mail because:
- You are watching all bug changes.