Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 11058] annoying popup when trying to capture on bonds

[bugzilla-daemon@xxxxxxxxxxxxx]

Comment # 9 on bug 11058 from Yann Bonnamy

in the end it looks as if there is a big difference in the way dumpcap and
tcpdump retrieves the devices capabilities, dumpcap can't succeed where tcpdump
succeeds :

# tcpdump -L -i em1
Data link types for em1 (use option -y to set):
  DOCSIS (DOCSIS) (printing not supported)
  EN10MB (Ethernet)

# dumpcap -L -i em1
Capturing on 'em1'
Data link types of interface em1 (use option -y to set):
  EN10MB (Ethernet)
  DOCSIS (DOCSIS)

# tcpdump -L -i MONI
Data link types for MONI (use option -y to set):
  DOCSIS (DOCSIS) (printing not supported)
  EN10MB (Ethernet)

# dumpcap -L -i MONI
Capturing on 'MONI'
dumpcap: The capabilities of the capture device "MONI" could not be obtained
(No such device exists).
Please check to make sure you have sufficient permissions, and that
you have the proper interface or pipe specified.

Comment # 8 on bug 11058 from Yann Bonnamy

actually i have to apologize for misleading the investigation, i just realized
that my "from source" version was installed a long time ago , and i forgot that
i patched it so that the issue does not occurs, i could say that i just ported
what is done in qt to what is done is gtk , the dialog is commented out on the
OK machine:

# grep -r "The link type of interface" .
./qt/capture_filter_edit.cpp://                   
simple_dialog(ESD_TYPE_ERROR, ESD_BTN_OK, "The link type of interface %s was
not specified.", device.name);
./gtk/capture_dlg.c:        //simple_dialog(ESD_TYPE_ERROR, ESD_BTN_OK, "The
link type of interface %s was not specified.", device.name);


so please forget my statement "the issue disappears when using wireshark
compiled from sources", actually it was "the issue disappear when patching the
sources" , sorry again for this.

Comment # 7 on bug 11058 from Yann Bonnamy

the problem occurs only if at least one bond interface is "checked" in the
"capture option" windows, if only non-bond interfaces are selected then there
is no issue.

both machines reports the same concerning tcpdump (normal as it is aligned on
the fedora repository):

# tcpdump -i MONI -L
Data link types for MONI (use option -y to set):
  DOCSIS (DOCSIS) (printing not supported)
  EN10MB (Ethernet)

# tcpdump -h
tcpdump version 4.5.1
libpcap version 1.5.3

there is no eth0 but rather em1, and yet again both machines reports the same:

# tcpdump -i em1 -L
Data link types for em1 (use option -y to set):
  DOCSIS (DOCSIS) (printing not supported)
  EN10MB (Ethernet)


concerning the output of dumpcap -D ,it is roughly the same on the 2 machines ,
except concerning the usb interfaces but is probably because i have set the
sticky bit on the "from source" version


NOK machine :

[user1@orvtr19moni ~]$ dumpcap -i MONI -L -M
Capturing on 'MONI'
dumpcap: The capabilities of the capture device "MONI" could not be obtained
(No such device exists).
Please check to make sure you have sufficient permissions, and that
you have the proper interface or pipe specified.
[user1@orvtr19moni ~]$ dumpcap -D -M
1. MONI                 0       fe80::21e:67ff:fe00:ea4e        network
2. bondOAM                      0       10.33.158.19,fe80::21e:67ff:fe00:ea4a  
network
3. nflog                        0               network
4. nfqueue                      0               network
5. em1                  0               network
6. em2                  0               network
7. p6p2                 0               network
8. p6p5                 0               network
9. p6p1                 0               network
10. p6p6                        0               network
11. any                 0               network
12. lo          Loopback        0       127.0.0.1,::1   loopback
[user1@orvtr19moni ~]$ type dumpcap
dumpcap is hashed (/usr/sbin/dumpcap)
[user1@orvtr19moni ~]$ ll /usr/sbin/dumpcap
-rwxr-x--- 1 root wireshark 82504 Jan  8 10:05 /usr/sbin/dumpcap





OK machine :

[user1@orvtr17moni ~]$ dumpcap -i MONI -L -M
Capturing on 'MONI'
dumpcap: The capabilities of the capture device "MONI" could not be obtained
(No such device exists).
Please check to make sure you have sufficient permissions, and that
you have the proper interface or pipe specified.
[user1@orvtr17moni ~]$ dumpcap -D -M
1. MONI                 0       fe80::21e:67ff:fe00:bd76        network
2. bondOAM                      0       10.32.246.19,fe80::21e:67ff:fe00:bd72  
network
3. nflog                        0               network
4. nfqueue                      0               network
5. em1                  0               network
6. usbmon1                      7               network
7. em2                  0               network
8. usbmon2                      7               network
9. usbmon3                      7               network
10. usbmon4                     7               network
11. usbmon5                     7               network
12. p6p3                        0               network
13. p6p4                        0               network
14. p6p5                        0               network
15. p6p1                        0               network
16. p6p6                        0               network
17. p6p2                        0               network
18. any                 0               network
19. lo          Loopback        0       127.0.0.1,::1   loopback
[user1@orvtr17moni ~]$ ll /usr/local/bin/dumpcap
-rwsr-s--x 1 root root 227606 Dec  8 08:30 /usr/local/bin/dumpcap

---

      You are receiving this mail because:

• You are watching all bug changes.