On Dec 18, 2014, at 1:42 PM, Michael Richardson wrote:
> Guy Harris 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
>>
Xiufeng Xie wrote:
> is not caused by tcpdump, libpcap or Android. I found the phone actually
> has two LTE interfaces "lte_rmnet0" and "lte_rmnet1", which is
Maybe different frequencies?
4G VoIP vs 4G data?
___
tcpdump-workers mailing lis
Hi,
Thanks for your suggestions. I have figured out the solution. The problem
is not caused by tcpdump, libpcap or Android. I found the phone actually
has two LTE interfaces "lte_rmnet0" and "lte_rmnet1", which is
unanticipated. I was always looking at the first interface "lte_rmnet0"
because I
Guy Harris 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*-bugg
On Dec 17, 2014, at 2:11 PM, Xiufeng Xie wrote:
> Currently I need to capture ipv6 packets on Android phone. On my PC,
> tcpdump works well with ipv6 traffic, so I also want to try it on the
> phone.
>
> However, when I cross-compile tcpdump for ARM platform with ipv6 enabled,
> it is forced
Hi,
Currently I need to capture ipv6 packets on Android phone. On my PC,
tcpdump works well with ipv6 traffic, so I also want to try it on the
phone.
However, when I cross-compile tcpdump for ARM platform with ipv6 enabled,
it is forced to give the warning about buggy getaddrinfo() function a
