Bug #122
tcpdump is broken
| Status: | New | Start: | 09/02/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | Debian packages | |||
| Target version: | 3.4 |
Description
root@deepfix:~# tcpdump -V
tcpdump version 4.1.1
libpcap version 1.1.1
Usage: tcpdump [-aAbdDefIKlLnNOpqRStuUvxX] [ -B size ] [ -c count ]
[ -C file_size ] [ -E algo:secret ] [ -F file ] [ -G seconds ]
[ -i interface ] [ -M secret ] [ -r file ]
[ -s snaplen ] [ -T type ] [ -w file ] [ -W filecount ]
[ -y datalinktype ] [ -z command ] [ -Z user ]
[ expression ]
root@deepfix:~# tcpdump tcpdump: SIOCGIFFLAGS: bonding_masters: No such device
Quick google search tells that probably an issue in libpcap. Should possibly be upgraded.
History
Updated by Mohit Chawla about 1 year ago
Seems like that was incorrect usage of tcpdump in the first place with deepOfix.
Apparently this bug didn't get updated as suggested by Abhas sir, so quoting him:
When you type 'tcpdump' without any arguments, it will try to use the first interface. In deepOfix, because of the way network drivers are compiled and inserted into the kernel, bond0 is the first interface. So tcpdump tries to listen in on bond0. Which it can't - because the interface is not up among other reasons. You should always provide 'tcpdump' with an interface using the '-i' flag. Such as: tcpdump -i eth0 -n