Re: [Nsis-imp] Assigned numbers for version GIMPS -06
Thomas Herzog <thomas.herzog@gmx.li> Mon, 11 July 2005 17:03 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32)
id 1Ds1gw-0004RU-S0; Mon, 11 Jul 2005 13:03:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32) id 1Ds1gr-0004Qs-3o
for nsis-imp@megatron.ietf.org; Mon, 11 Jul 2005 13:03:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00650
for <nsis-imp@ietf.org>; Mon, 11 Jul 2005 13:03:29 -0400 (EDT)
Received: from pop.gmx.de ([213.165.64.20] helo=mail.gmx.net)
by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Ds28p-0008S0-3M
for nsis-imp@ietf.org; Mon, 11 Jul 2005 13:32:31 -0400
Received: (qmail invoked by alias); 11 Jul 2005 17:03:17 -0000
Received: from J383f.j.pppool.de (EHLO [192.168.0.3]) [85.74.56.63]
by mail.gmx.net (mp019) with SMTP; 11 Jul 2005 19:03:17 +0200
X-Authenticated: #4469397
Message-ID: <42D2A656.3000809@gmx.li>
Date: Mon, 11 Jul 2005 19:03:18 +0200
From: Thomas Herzog <thomas.herzog@gmx.li>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041207)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Lang, Christopher" <christopher.lang@roke.co.uk>
Subject: Re: [Nsis-imp] Assigned numbers for version GIMPS -06
References: <3F2E01E1D7B04F4EBEC92D3FA324D8803F683E@rsys004a>
In-Reply-To: <3F2E01E1D7B04F4EBEC92D3FA324D8803F683E@rsys004a>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Content-Transfer-Encoding: 7bit
Cc: nsis-imp@ietf.org
X-BeenThere: nsis-imp@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: thomas@herzogonline.net
List-Id: List for implementation questions for NSIS protocols
<nsis-imp.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis-imp>,
<mailto:nsis-imp-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/nsis-imp>
List-Post: <mailto:nsis-imp@lists.ietf.org>
List-Help: <mailto:nsis-imp-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis-imp>,
<mailto:nsis-imp-request@lists.ietf.org?subject=subscribe>
Sender: nsis-imp-bounces@lists.ietf.org
Errors-To: nsis-imp-bounces@lists.ietf.org
To be a little bit more specific: For IPv6, you theoretically do not even need to use a RAW socket, to read RAO options, of course, you need them to intercept the packets which are not addressed to us but to the flow sink/source... "man ipv6" tells us: > IPV6_RTHDR, IPV6_AUTHHDR, IPV6_DSTOPS, IPV6_HOPOPTS, IPV6_FLOWINFO, IPV6_HOPLIMIT > Set delivery of control messages for incoming datagrams containing extension headers from the received packet. IPV6_RTHDR delivers the > routing header, IPV6_AUTHHDR delivers the authentication header, IPV6_DSTOPTS delivers the destination options, IPV6_HOPOPTS delivers the > hop options, IPV6_FLOWINFO delivers an integer containing the flow id, IPV6_HOPLIMIT delivers an integer containing the hop count of the > packet. The control messages have the same type as the socket option. All these header options can also be set for outgoing packets by > putting the appropriate control message into the control buffer of sendmsg(2). Only allowed for SOCK_DGRAM or SOCK_RAW sockets. Argument > is a pointer to a boolean value. > A recvmsg on the socket should deliver the packet in a msghdr structure along with all the Hop-by-Hop options in the ancillary data. On a different approach, via iptables/libipq, also all RAO values can be read easily in both IPv4 and IPv6. Cheers, Thomas Lang, Christopher wrote: > To be more specific: > > We have been using standard raw IP sockets with the IP_ROUTER_ALERT option to intercept packets. This method only works on Linux when the RAO value is 0 (see http://lxr.linux.no/source/net/ipv4/ip_options.c#L428). Also we only looked at IPv4 before we stuck to an RAO of 0. I don't know if raw IPv6 sockets work better or not. > > It appears, from comments from Thomas, that it is possible to use any RAO value if the packets are intercepted using iptables and libipq (using a standard unpatched kernel) :-) > > Chris Lang > >>-----Original Message----- >>From: Lang, Christopher >>Sent: 11 July 2005 10:46 >>To: 'Xiaoming Fu'; Hancock, Robert >>Cc: nsis-imp@ietf.org >>Subject: RE: [Nsis-imp] Assigned numbers for version GIMPS -06 >> >> >>Hi, >> >>We have been using Linux as a platform (with a 2.6.7 kernel). >>Using non-zero RAO values we intially found that GIMPS >>messages were not being picked up by intermediate nodes. >>Inspection of the Kernel source revealed that the Linux >>kernel ignores all RAO values except 0. >> >>There also does not appear to be support for picking out any >>RAO packets in Windows. >> >>Which platform have you been using? >> >>Chris Lang >> _______________________________________________ NSIS-imp mailing list NSIS-imp@lists.ietf.org https://www1.ietf.org/mailman/listinfo/nsis-imp
- [Nsis-imp] Assigned numbers for version GIMPS -06 Hancock, Robert
- Re: [Nsis-imp] Assigned numbers for version GIMPS… Xiaoming Fu
- RE: [Nsis-imp] Assigned numbers for version GIMPS… Hancock, Robert
- Re: [Nsis-imp] Assigned numbers for version GIMPS… Xiaoming Fu
- RE: [Nsis-imp] Assigned numbers for version GIMPS… Hancock, Robert
- Re: [Nsis-imp] Assigned numbers for version GIMPS… Xiaoming Fu
- RE: [Nsis-imp] Assigned numbers for version GIMPS… Lang, Christopher
- RE: [Nsis-imp] Assigned numbers for version GIMPS… Lang, Christopher
- Re: [Nsis-imp] Assigned numbers for version GIMPS… Thomas Herzog
- Re: [Nsis-imp] Assigned numbers for version GIMPS… Xiaoming Fu