https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7808
--- Comment #3 from Guy Harris <guy@xxxxxxxxxxxx> 2012-10-07 17:06:26 PDT ---
(In reply to comment #2)
> % ldd /usr/lib64/libpcap.so.1
...
> libnl.so.1 => /usr/lib64/libnl.so.1 (0x00007f8d31eec000)
...
Exactly.
There's not much Wireshark can do about this; it *does* support libnl1, so I
guess whatever Wireshark package you're using could be configured to use libnl1
rather than libnl3 and not get collisions of that sort, or the distribution
could stop configuring libpcap to use libnl (with the loss of some convenience
in capturing in monitor mode).
The best way to deal with this is probably to change libpcap to avoid using
libnl to do things such as adding monitor-mode VIFs - perhaps just doing Full
Frontal Netlink (it can't incorporate any GPLed code into the library, so
merging in a GPLed or LGPLed netlink library isn't possible here) - which would
also mean that more distributions will support libpcap's monitor-mode APIs
(some avoid linking libpcap with libnl so as not having to deal with "which
version of libnl should it use?" issues).
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
