Re: [tcpdump-workers] Build and check on a big-endian system
- Original Message - > From: Guy Harris > To: François-Xavier Le Bail > Cc: tcpdump-workers > Sent: Monday, February 17, 2014 12:55 AM > Subject: Re: [tcpdump-workers] Build and check on a big-endian system > > > On Feb 16, 2014, at 10:58 AM, François-Xavier Le Bail > wrote: > >>> From: Guy Harris >> >>> On Feb 15, 2014, at 1:21 PM, Michael Richardson > wrote: >>> The ESP tests are failing because you haven't got libssl-dev. >>> >>> Yes - some tests fail if the full set of support libraries weren't > available when tcpdump was built. >>> >>> Perhaps we want to suppress some tests if we don't have the > appropriate libraries - or have the tests compare against the results of a > tcpdump built without the library or libraries in question rather than the > results of one built with them. >> >> >> We could maybe add a text in INSTALL file, like: >> +To build with crypto support, you need SSL library (libssl-dev). >> +If you don't have this library, you will have some "make > check" errors. > > Denis appears to have fixed that with > > commit 9e2042ebe86c41d373930dbd89b56a6a2f06fcf0 > Author: Denis Ovsienko > Date: Mon Feb 17 00:22:37 2014 +0400 > > make OpenSSL-specific tests conditional We could maybe add a text in INSTALL file, like: To build with crypto support, you need SSL library (libssl-dev). ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Re: [tcpdump-workers] how can i access tsval from tcp options?
Thanks, Denis, I'll check that out. 2014-02-15 14:28 GMT-05:00, Denis Ovsienko : > 15.02.2014, 18:44, "Daniel H. Bahr" : >> Hello everyone, >> >> I'm in need of accessing the tsval value of the options field in the >> tcp header... i've been checking the tcp.h and did not find anything >> that helped me. >> >> Does any body know how to do it? > > Greetings. > > TCP options are a particular case of TLV class of encodings. This most > likely implies that TCP options are opaque to libpcap. To access one or more > TCP options it is necessary to have some code like that in tcpdump, > print-tcp.c around line 500. > > -- > Denis Ovsienko > ___ > tcpdump-workers mailing list > tcpdump-workers@lists.tcpdump.org > https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers > ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] Updating libpcap and tcpdump in Android Open Source Platform (AOSP)
Hi, I'm aka m...@tcpdump.org, and getting tcpdump in AOSP updated to the latest has been on my list for awhile. It's been two years since I last did much Android build work, so it took me a few days to get a build VM going again. I checked out a copy of kitkat, built it, and proceeded to extract the Android patches from external/libpcap and external/tcpdump. Those trees were originally imported in 2007 from the CVS trees at the time... the Tcpdump project has since moved to git, and has imported our old releases in as well. I checked out our 0.9.8 (libpcap) and 3.9.8 branches, and then did a bit of diff and patching. I removed the spurious CVS $Id stuff, and then adapted the Android.mk slightly. I have not yet decided what to do about disuse of bison/flex for libpcap, I propose to leave the generated files there now, and fix this once Android is on libpcap 1.5 (1.6 will come out in two weeks, during IETF89 week). Gerritt won't let me repo upload my merged tree, as it includes much code from others, and naturally those email addresses are not valid for me. I am seeking advice here --- I originally merged in the Android branch into my tree to keep common ancestry, but really that tree has little value, and I'd rather do a git push -f if the community accepts that. You can see the merged trees at: https://github.com/the-tcpdump-group/libpcap/tree/android-libpcap-0.9.8 https://github.com/the-tcpdump-group/tcpdump/tree/android-tcpdump-3.9.8 there are some warnings about variables which are likely fixed in tcpdump 4.5/libpcap-1.5, but it compiles and links properly. Some commits which likely are most interesting: https://github.com/the-tcpdump-group/tcpdump/commit/02d222b008e130867d44fc1501ccee1aa27a8d8e https://github.com/the-tcpdump-group/tcpdump/commit/11bcf04c31e63867632732d4732e76e203d34073 https://github.com/the-tcpdump-group/libpcap/commit/56deb7c250d306650df7bf1788754e2e5d805cfc https://github.com/the-tcpdump-group/libpcap/commit/91f35ab90101db7c204fb8dc8dfb54729a4c34ee Replacing the 0.9.8/3.9.8 imports is what I call step one. I will be cherry-picking the changes to make that tree work on Android into the libpcap/tcpdump master branch, and then verifying that it compiles and works. I don't know how that will interact with repo, given that I can't use repo upload on what I have so far. Please advise. remote: ERROR: In commit b11ddf8a9b0d30bf759abf01afcf2894e79857b1 remote: ERROR: committer email address mcr remote: ERROR: does not match your user account. remote: ERROR: ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
[tcpdump-workers] Updating libpcap and tcpdump in Android Open Source Platform (AOSP)
{this is a resend. I don't see my email in the android-platform online
archives}
Hi, I'm aka mcr at tcpdump.org, and getting tcpdump in AOSP updated to the
latest has been on my list for awhile.
It's been two years since I last did much Android build work, so it took me
a few days to get a build VM going again.
I checked out a copy of kitkat, built it, and proceeded to extract the
Android patches from external/libpcap and external/tcpdump.
Those trees were originally imported in 2007 from the CVS trees at the
time... the Tcpdump project has since moved to git, and
has imported our old releases in as well. I checked out our 0.9.8
(libpcap) and 3.9.8 branches, and then did a bit of diff and patching.
I removed the spurious CVS $Id stuff, and then adapted the Android.mk
slightly. I have not yet decided what to do about disuse
of bison/flex for libpcap, I propose to leave the generated files there
now, and fix this once Android is on libpcap 1.5 (1.6 will come out in two
weeks, during IETF89 week).
Gerritt won't let me repo upload my merged tree, as it includes much code
from others, and naturally those email addresses are not
valid for me. I am seeking advice here --- I originally merged in the
Android branch into my tree to keep common ancestry, but really that
tree has little value, and I'd rather do a git push -f if the community
accepts that. You can see the merged trees at:
https://github.com/the-tcpdump-group/libpcap/tree/android-libpcap-0.9.8
https://github.com/the-tcpdump-group/tcpdump/tree/android-tcpdump-3.9.8
there are some warnings about variables which are likely fixed in tcpdump
4.5/libpcap-1.5, but it compiles and links properly.
Some commits which likely are most interesting:
https://github.com/the-tcpdump-group/tcpdump/commit/02d222b008e130867d44fc1501ccee1aa27a8d8e
https://github.com/the-tcpdump-group/tcpdump/commit/11bcf04c31e63867632732d4732e76e203d34073
https://github.com/the-tcpdump-group/libpcap/commit/56deb7c250d306650df7bf1788754e2e5d805cfc
https://github.com/the-tcpdump-group/libpcap/commit/91f35ab90101db7c204fb8dc8dfb54729a4c34ee
Replacing the 0.9.8/3.9.8 imports is what I call step one.
I will be cherry-picking the changes to make that tree work on Android into
the libpcap/tcpdump master
branch, and then verifying that it compiles and works. I don't know how
that will interact with repo, given
that I can't use repo upload on what I have so far.
Please advise.
this is what repo upload says to me:
remote: ERROR: In commit b11ddf8a9b0d30bf759abf01afcf2894e79857b1
remote: ERROR: committer email address mcr
remote: ERROR: does not match your user account.
remote: ERROR:
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
