tcpdump mailing list archives
Re: Requesting LINKTYPE constant be defined/reserved for: IP over IB
From: Oren Kladnitsky <orenk () mellanox com>
Date: Thu, 20 Dec 2012 15:42:34 +0000
Hi Stuart, Please note that DLT_INFINIBAND (247) is reserved for native InfiniBand link type. Not to be mixed with IPoIB. Regards, Oren -----Original Message----- From: tcpdump-workers-bounces () lists tcpdump org [mailto:tcpdump-workers-bounces () lists tcpdump org] On Behalf Of Guy Harris Sent: Thursday, December 20, 2012 12:20 AM To: Stuart Werbner Cc: tcpdump-workers () lists tcpdump org Subject: Re: [tcpdump-workers] Requesting LINKTYPE constant be defined/reserved for: IP over IB On Dec 19, 2012, at 1:27 PM, Stuart Werbner <swerbner () us ibm com> wrote:
I am requesting a new LINKTYPE_ (LINKTYPE_IB) value for IP over Infiniband be reserved, in order to properly support this protocol within tcpdump and libpcap for upcoming AIX kernel releases.
So you're using LINKTYPE_ values, rather than SNMP interface type values, as the network type in pcap files now? Good. If you're writing nanosecond time stamps to files, are you now using a1 b2 3c 4d rather than a1 b2 c3 d4 as the magic number, so that programs or libraries reading the files can determine what the time stamp resolution is? (And speaking of AIX's libpcap/tcpdump, there's AIX support in the tcpdump.org libpcap, but it seems to be tripping across some bugs in AIX's BPF implementation, at least in the versions of AIX against which the people reporting the bugs tried it.)
If this value is already defined, please indicate that. I have discovered that within an AIX kernel header file, DLT_IB (Data-link Level Type) is defined, but I believe we are still in need of a Link-Layer Header Type. Here are the RFCs related to IP over Infiniband: * RFC 3827 * RFC 4391
In the existing link-layer header type list: http://www.tcpdump.org/linktypes.html there's a LINKTYPE_IPOIB value, in which the packet data is as described in section 6 of RFC 4391, starting with the 4-octet encapsulation header. RFC 3827 just speaks of a snoop link-layer header type value for IP-over-IB, referring to a "work in progress" document; as RFC 3827 came from Sun, and as LINKTYPE_IPOIB was provided in response to a request from somebody from Sun^WOracle, the snoop link-layer header type probably refers to the same thing. _______________________________________________ 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
Current thread:
- Requesting LINKTYPE constant be defined/reserved for: IP over IB Stuart Werbner (Dec 19)
- Re: Requesting LINKTYPE constant be defined/reserved for: IP over IB Guy Harris (Dec 19)
- Re: Requesting LINKTYPE constant be defined/reserved for: IP over IB Oren Kladnitsky (Dec 20)
- Re: Requesting LINKTYPE constant be defined/reserved for: IP over IB Guy Harris (Dec 19)