tcpdump mailing list archives
Re: Building IPv6 code in tcpdump on systems without
From: Darren Reed <darrenr () reed wattle id au>
Date: Wed, 21 Jul 2004 21:19:40 +1000 (EST)
In some email I received from Guy Harris, sie wrote:
I have some changes to support that.
The main change is to add a "union h6addr" to "tcpdump-stdinc.h", along
with defintions of IN6_IS_ADDR_UNSPECIFIED, AF_INET6, and NI_MAXHOST if
they're not defined.
Some side-effects of this:
1) it defines DEFAULT_SNAPLEN as 96 unconditionally, rather
than, as is done now, as 68 if INET6 isn't defined and as 96
if it is defined;
The first seems OK to me, although some might find it a surprise. You
can always use "-s 68" if you want 68 bytes.
I agree with this. 96..plus pcap header size of 16 is 112. Do you want to push it out to 112, so with the pcap header size, brings it up to 128 bytes (normal length), fitting in evenly to most buffer sizes? Oh wait, that's the "max" pcapture size so ignore that :) Darren - This is the tcpdump-workers list. Visit https://lists.sandelman.ca/ to unsubscribe.
Current thread:
- Building IPv6 code in tcpdump on systems without native IPv6 support Guy Harris (Jul 20)
- Re: Building IPv6 code in tcpdump on systems without Darren Reed (Jul 21)
- Re: Building IPv6 code in tcpdump on systems without native IPv6 support John Hawkinson (Jul 21)
- Re: Building IPv6 code in tcpdump on systems without Darren Reed (Jul 21)
- Re: Building IPv6 code in tcpdump on systems without native IPv6 support Guy Harris (Jul 21)
