[tcpdump-workers] Cross-compiling tcpdump with ipv6 enabled

Michael Richardson mcr at sandelman.ca
Thu Dec 18 16:42:34 EST 2014

Guy Harris <guy at alum.mit.edu> wrote:
    > I would vote for assuming that there aren't many buggy implementations
    > these days, especially when cross-compiling (which would probably be
    > for a Linux or *BSD target, current versions of which probably have
    > non-buggy getaddrinfo()), assuming a *non*-buggy getaddrinfo() when
    > cross compiling, and playing The World's Smallest Violin if somebody
    > ends up getting hosed by getaddrinfo() on a target platform for which
    > they're cross-compiling.

yes, I agree...

    >> I comment out this test to complete compiling (with ipv6
    >> enabled). The resulting binary works well when monitoring ipv4 packets on
    >> my phone, but still captures 0 packets on the Verizon ipv6 lTE network.

    > Try writing a small test program, using libpcap, that doesn't set any
    > capture filter and that just counts packets.

    > If that doesn't capture any packets on Verizon's LTE network, then the
    > problem is either with libpcap or with the Android networking stack.

I was trying to get tcpdump in the Android AOSP tree updated in the spring,
but I ran out of time...

]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr at sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

More information about the tcpdump-workers mailing list