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

2014-12-19 Thread Xiufeng Xie
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 never considered there can be another one. However, all the LTE
traffic goes through "lte_rmnet1". That is why I always get 0 packets. If I
set the interface to "lte-rmnet1", tcpdump works well with LTE ipv6 packets.

Best Regards,
Xiufeng

On Thu, Dec 18, 2014 at 3: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
> > 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  [
> ] m...@sandelman.ca  http://www.sandelman.ca/|   ruby on
> rails[
>
>
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers


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

2014-12-19 Thread Michael Richardson

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 list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers


[tcpdump-workers] #tcpdump-dev

2014-12-19 Thread Michael Richardson

Do people know that #tcpdump-dev on irc.freenode.net has the git.io bot in
it, and see stuff like:

(01:48:44 PM) GitHub15: tcpdump/master 94b4c01 Denis Ovsienko: OpenFlow: add
vendor name printing...
(01:48:44 PM) GitHub15: tcpdump/master 78a0b1c Denis Ovsienko: OpenFlow:
improve vendor message decoding...
(14/12/14 11:25:28 PM) GitHub148: [tcpdump] infrastation pushed 1 new commit
to master: http://git.io/nvwXYQ
(11:25:28 PM) GitHub148: tcpdump/master 3be91f6 Denis Ovsienko: OpenFlow:
handle 5 more BSN subtypes
(15/12/14 01:58:20 PM) GitHub117: [tcpdump] fxlb created coverity_scan from
master (+0 new commits): http://git.io/wynloA
(02:29:38 PM) GitHub41: [tcpdump] fxlb deleted coverity_scan at 3be91f6:
http://git.io/WFHVog
(17/12/14 08:56:14 AM) GitHub144: [tcpdump] fxlb opened pull request #416:
ForCES: update reference from draft to RFC5810 (master...forces)
http://git.io/iq-KRg
(09:36:30 AM) GitHub138: [tcpdump] fxlb closed pull request #416: ForCES:
update reference from draft to RFC5810 (master...forces) http://git.io/iq-KRg
(09:36:33 AM) GitHub174: [tcpdump] fxlb pushed 1 new commit to master:
http://git.io/QlFDVQ
(09:36:33 AM) GitHub174: tcpdump/master 6fe428b Francois-Xavier Le Bail:
ForCES: update reference from draft to RFC5810...
(09:51:07 AM) GitHub195: [tcpdump] fxlb pushed 1 new commit to master:
http://git.io/NxXAjA
(09:51:07 AM) GitHub195: tcpdump/master df75779 Francois-Xavier Le Bail: Fix
some typos
(04:08:40 PM) GitHub58: [tcpdump] fxlb pushed 1 new commit to master:
http://git.io/W5tHfQ
(04:08:40 PM) GitHub58: tcpdump/master a726686 Francois-Xavier Le Bail:
Travis: minor update...
(19/12/14 01:27:56 AM) GitHub110: [tcpdump] mcr pushed 6 new commits to
tcpdump-4.7: http://git.io/3pnlqg
(01:27:56 AM) GitHub110: tcpdump/tcpdump-4.7 45f8b5e Guy Harris: Check
whether the version field is available before looking at it
(01:27:56 AM) GitHub110: tcpdump/tcpdump-4.7 df8c15f Guy Harris: Do more
length checking.  From OpenBSD.
(01:27:56 AM) GitHub110: tcpdump/tcpdump-4.7 44128cf Guy Harris: Fix length
checking
(01:27:56 AM) GitHub5: [tcpdump] mcr pushed 6 new commits to master:
http://git.io/k7ankQ
(01:27:56 AM) GitHub5: tcpdump/master c67afe9 Guy Harris: Check whether the
version field is available before looking at it
(01:27:56 AM) GitHub5: tcpdump/master d751676 Guy Harris: Do more length
checking.  From OpenBSD.
(01:27:56 AM) GitHub5: tcpdump/master 743bcec Guy Harris: Fix length
checking
(04:34:08 AM) GitHub38: [tcpdump] fxlb created coverity_scan from master (+0
new commits): http://git.io/wynloA
(07:57:36 AM) GitHub9: [tcpdump] infrastation pushed 2 new commits to master:
http://git.io/iHUf1A
(07:57:36 AM) GitHub9: tcpdump/master fc70538 Guy Harris: Dissect the IPv4
header if the version is wrong, but fix the messages.
(07:57:36 AM) GitHub9: tcpdump/master 7685b21 Guy Harris: Only print the
incorporated IP packet if there is one
(01:07:46 PM) GitHub120: [tcpdump] infrastation pushed 1 new commit to
master: http://git.io/ydc-bQ
(01:07:46 PM) GitHub120: tcpdump/master 7cea408 Denis Ovsienko: update a
comment: TCP Fast Open is now an RFC
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers


Re: [tcpdump-workers] Fix FreeBSD capsicum build on FreeBSD 10.1

2014-12-19 Thread Guy Harris

On Dec 7, 2014, at 12:17 AM, Loganaden Velvindron  wrote:

> Here's the diff:
> 
> index d0e90dd..1620bbb 100644
> --- a/configure.in
> +++ b/configure.in
> @@ -207,8 +207,10 @@ AC_ARG_WITH(sandbox-capsicum,
> #
> # All of them must be available in order to enable capsicum sandboxing.
> #
> +# NOTE: cap_rights_init is a macro on FreeBSD, so remove it from the list.
> +
> if test ! -z "$with_sandbox-capsicum" && test "$with_sandbox-capsicum" != 
> "no" ; then
> -   AC_CHECK_FUNCS(cap_enter cap_rights_init cap_rights_limit 
> cap_ioctls_limit openat,
> +   AC_CHECK_FUNCS(cap_enter cap_rights_limit cap_ioctls_limit openat,
>ac_lbl_capsicum_function_seen=yes,
>ac_lbl_capsicum_function_not_seen=yes)
> fi

I've checked into the trunk a similar change, but with a more elaborate 
comment, and cherry-picked it to the 4.7 branch.
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers


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

2014-12-19 Thread Guy Harris

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
>> 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...

OK, I've checked in that change.
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers


Re: [tcpdump-workers] Fix FreeBSD capsicum build on FreeBSD 10.1

2014-12-19 Thread Loganaden Velvindron
On Fri, Dec 19, 2014 at 01:29:00PM -0800, Guy Harris wrote:
> 
> On Dec 7, 2014, at 12:17 AM, Loganaden Velvindron  wrote:
> 
> > Here's the diff:
> > 
> > index d0e90dd..1620bbb 100644
> > --- a/configure.in
> > +++ b/configure.in
> > @@ -207,8 +207,10 @@ AC_ARG_WITH(sandbox-capsicum,
> > #
> > # All of them must be available in order to enable capsicum sandboxing.
> > #
> > +# NOTE: cap_rights_init is a macro on FreeBSD, so remove it from the list.
> > +
> > if test ! -z "$with_sandbox-capsicum" && test "$with_sandbox-capsicum" != 
> > "no" ; then
> > -   AC_CHECK_FUNCS(cap_enter cap_rights_init cap_rights_limit 
> > cap_ioctls_limit openat,
> > +   AC_CHECK_FUNCS(cap_enter cap_rights_limit cap_ioctls_limit openat,
> >ac_lbl_capsicum_function_seen=yes,
> >ac_lbl_capsicum_function_not_seen=yes)
> > fi
> 
> I've checked into the trunk a similar change, but with a more elaborate 
> comment, and cherry-picked it to the 4.7 branch.

Awesome ! Thank you.

I was looking into the github repo, but couldn't find the change.

Do you have the git commit id for this ?
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers


Re: [tcpdump-workers] Fix FreeBSD capsicum build on FreeBSD 10.1

2014-12-19 Thread Guy Harris

On Dec 19, 2014, at 8:36 PM, Loganaden Velvindron  wrote:

> I was looking into the github repo, but couldn't find the change.

I didn't check it into the github repo, I checked it into the bpf.tcpdump.org 
repo.  It should eventually get propagated to the github repo.

> Do you have the git commit id for this ?

05d7191dc989090c94d1fefc35a50e1d99b0b532

___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers