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
On Jul 8, 2011, at 12:46 AM, Folkert van Heusden wrote:
> Found the problem: I selected to not only not using yacc but not using
> bison as well. That gives weird results.
There's no "don't use yacc" configure option. Did you mean "flex" rather than
"yacc", or did you mean you specified not to
>> What can be the cause of this? And how do I solve this problem?
> It would appear that HAVE_PCAP_DATALINK_NAME_TO_VAL isn't defined.
Found the problem: I selected to not only not using yacc but not using
bison as well. That gives weird results.
-
This is the tcpdump-workers list.
Visit https://
Folkert van Heusden gmail.com> writes:
> What can be the cause of this? And how do I solve this problem?
It would appear that HAVE_PCAP_DATALINK_NAME_TO_VAL isn't defined.
-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscribe.
Hi,
(could not find a more general help mailinglist)
I'm trying to cross-compile libpcap and tcpdump to an ARM platform.
For that I use the following script to run configure for libpcap:
export CXX=arm-g++
export CC=arm-gcc
export CPP=arm-linux-cpp
export AR=arm-ar
export RANLIB=arm-ranlib
export
On Jun 22, 2010, at 8:48 AM, Alan Neville wrote:
> I have been trying to cross-compile libpcap-1.1.1 for use on the iPhone
> (armv6 architecture) to no avail.
Note that, in iOS, the BPF devices are probably owned by root and only openable
by root, so you will have to run your program as root, w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey list,
I have been trying to cross-compile libpcap-1.1.1 for use on the iPhone
(armv6 architecture) to no avail. I have the iPhone SDK 3.1.3 installed
on my Mac (10.6, Snow Leopard) and I have managed to successfully
compile and run applications on
12 matches
Mail list logo
