Interface descriptions via pcap broken

[Brandon Gooch]

On Tue, Mar 1, 2011 at 12:37 AM, Bruce Cran <bruce at cran.org.uk> wrote:
> I installed wireshark on my 9-CURRENT machine yesterday and found that
> the interface description fields are all set to 0xa5. From reading the
> code it looks like the data is being fetched via pcap.
>
> Device: usbus1
> Description: \xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5
> \xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5
> \xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5
> \xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5\xa5
> IP: unknown
>
> Has a recent change broken this?
>
> --
> Bruce Cran

I'm seeing the same thing. libpcap-1.1.1 was merged into HEAD about 4
months ago, so it's possible...

I suspect changes to libpcap's inet.c:

http://svn.freebsd.org/viewvc/base/head/contrib/libpcap/inet.c?r1=203052&r2=214518

...although I haven't had the time to look through it thoroughly --
it's more of a "gut feeling" (if there could be such a thing regarding
C code LOL). BTW, if you give your devices descriptions, libpcap
starts to behave again; this could be a clue to the source of the bug
:/

What do you think Rui? Any hints?

-Brandon