Subject: Re: does gif(4) do RFC 2003 IPv4-in-IPv4 encapsulation?
To: None <firstname.lastname@example.org,>
From: Greg A. Woods <email@example.com>
Date: 03/04/2002 14:32:09
[ On Monday, March 4, 2002 at 15:24:13 (+0200), Bill Sommerfeld wrote: ]
> Subject: CVS commit: syssrc/sys/netinet
> Module Name: syssrc
> Committed By: sommerfeld
> Date: Mon Mar 4 13:24:12 UTC 2002
> Removed Files:
> sharesrc/share/man/man4: ipip.4
> syssrc/sys/netinet: ip_ipip.c ip_ipip.h
> Log Message:
> The "gif*" tunnelling interface does everything ipip does.
Does 'gif' really do encapsulation is according to RFC 2003?
As far as I know it is still the most widely adopted "standard" for
IP-in-IP tunnels. From the 2002/02/26 rfc-index.txt:
2003 IP Encapsulation within IP. C. Perkins. October 1996. (Format:
TXT=30291 bytes) (Status: PROPOSED STANDARD)
I do see mention of RFC 2003 support in sys/netinet/ip_encap.c, and
there seems to be some link to gif(4) (sys/netinet/in_gif.c includes
<netinet/ip_encap.h>). However I don't immediately see how one
configures an RFC 2003 tunnel with gif(4). Maybe it happens
automatically through some form of negotiation? Is there just an
omission in the docs?
Greg A. Woods
+1 416 218-0098; <firstname.lastname@example.org>; <email@example.com>; <firstname.lastname@example.org>
Planix, Inc. <email@example.com>; VE3TCP; Secrets of the Weird <firstname.lastname@example.org>