NetBSD Problem Report #9818

Received: (qmail 27845 invoked from network); 7 Apr 2000 15:04:02 -0000
Message-Id: <200004071502.IAA20149@nbwww.isc.org>
Date: Fri, 7 Apr 2000 08:02:59 -0700 (PDT)
From: mullins@dcs.uky.edu
Reply-To: mullins@dcs.uky.edu
To: gnats-bugs@gnats.netbsd.org
Subject: Router Alert RFC2113 has not been implemented.
X-Send-Pr-Version: www-1.0

>Number:         9818
>Category:       kern
>Synopsis:       Router Alert RFC2113 has not been implemented.
>Confidential:   no
>Severity:       non-critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Fri Apr 07 15:05:00 +0000 2000
>Closed-Date:    
>Last-Modified:  Mon Feb 05 03:27:00 +0000 2001
>Originator:     Billy Mullins
>Release:        1.4.1
>Organization:
University of Kentucky
>Environment:
NetBSD fred 1.4.1 NetBSD 1.4.1 (APIC_1_4_1) #0: Tue Mar 28 11:45:03 PST 2000 

>Description:
The IP Router Alert Option RFC2113, has not been implemented.  I don't
know if this has been submitted in a previous change, although I did
look without success.  I would like to implement the change and
submit patch.  

>How-To-Repeat:


>Fix:

Just a matter of programming.
>Release-Note:
>Audit-Trail:

From: Jun-ichiro itojun Hagino <itojun@iijlab.net>
To: mullins@dcs.uky.edu
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/9818
Date: Mon, 05 Feb 2001 12:26:16 +0900

 	http://www.NetBSD.org/cgi-bin/query-pr-single.pl?number=9818
 	(IPv4 router alert option)

 	the problem is that (1) there's no commonly-agreed API for intermediate
 	routers for inspecting packets, (2) there's no commonly-agreed API for
 	sending packets with router alert option set.

 	for IPv6, we have some code to handle these cases: for (1),
 	we capture these packet in sys/netinet6/ip6_input.c:ip6_input()
 	(check variable "rtalert") and grab them in sys/netinet6/mld6.c:
 	mld6_input().  for non-MLD protocol types, we have no idea how to
 	deal with them.  for example, if a packet with TCP header carries
 	router alert option, they will go up to tcp6_input() and then
 	dropped due to the lack of tcp control block for the connection.
 	for (2), luckily we have "2292bis" advanced API for IPv6, and we can
 	attach them as we wish (see draft-ietf-ipngwg-rfc2292bis-02.txt).

 itojun
>Unformatted:

Home	PR Database Search