-Original Message-
From: osprey67 [mailto:[EMAIL PROTECTED]
Sent: Monday, November 12, 2007 7:55 AM
To: netdev@vger.kernel.org
Subject: [PATCH 04/05] ipv6: RFC4214 Support (4)
From: Fred L. Templin <[EMAIL PROTECTED]>
This is experimental support for the Intra-Site Automatic
From: Fred L. Templin <[EMAIL PROTECTED]>
This is experimental support for the Intra-Site Automatic
Tunnel Addressing Protocol (ISATAP) per RFC4214. It uses
the SIT module, and is configured using the unmodified
"ip" utility with device names beginning with: "isatap".
The following diffs are spe
"Templin, Fred L" <[EMAIL PROTECTED]> writes:
>
> +#if defined(CONFIG_IPV6_ISATAP)
> + /* ISATAP (RFC4214) - router address in daddr */
> + if (!strncmp(parms->name, "isatap", 6)) {
Modern distributions tend to have daemons to automatically rename
network interfaces using SIOCSIFNAME. No
From: Fred L. Templin <[EMAIL PROTECTED]>
This is experimental support for the Intra-Site Automatic
Tunnel Addressing Protocol (ISATAP) per RFC4214. It uses
the SIT module, and is configured using the unmodified
"ip" utility with device names beginning with: "isatap".
The following diffs are spe
From: "Templin, Fred L" <[EMAIL PROTECTED]>
Date: Thu, 8 Nov 2007 13:01:34 -0800
> > Hmm, what is missing from API POV?
>
> This would have to be determined under a follow-on project (hopefully
> with input from others) after we have gained operational experience.
I personally don't buy any of t
> Hmm, what is missing from API POV?
This would have to be determined under a follow-on project (hopefully
with input from others) after we have gained operational experience.
> Since even if you do not change iproute2 now, users may need
> to change their configuration script twice anyway, we sh
From: Fred L. Templin <[EMAIL PROTECTED]>
This is experimental support for the Intra-Site Automatic
Tunnel Addressing Protocol (ISATAP) per RFC4214. It uses
the SIT module, and is configured using the unmodified
"ip" utility with device names beginning with: "isatap".
The following diffs are spe
In article <[EMAIL PROTECTED]> (at Wed, 7 Nov 2007 11:12:47 -0800), "Templin,
Fred L" <[EMAIL PROTECTED]> says:
> > > The goal was to avoid requiring changes to applications such as
> > > 'iproute2', i.e., the intention was for a standalone code
> > insertion point
> > > within the kernel itself
> -Original Message-
> From: Stephen Hemminger [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 07, 2007 10:45 AM
> To: Templin, Fred L
> Cc: YOSHIFUJI Hideaki / 吉藤英明; netdev@vger.kernel.org
> Subject: Re: [PATCH 04/05] ipv6: RFC4214 Support
>
> On Wed, 7
Templin, Fred L
> > Cc: netdev@vger.kernel.org; [EMAIL PROTECTED]
> > Subject: Re: [PATCH 04/05] ipv6: RFC4214 Support
> >
> > Hello.
> >
> > In article
> > <[EMAIL PROTECTED]
> > eing.com> (at Tue, 6 Nov 2007 17:16:11 -0800), "Templin, Fred
Yoshifuji,
> -Original Message-
> From: YOSHIFUJI Hideaki / 吉藤英明 [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 07, 2007 10:37 AM
> To: Templin, Fred L
> Cc: netdev@vger.kernel.org; [EMAIL PROTECTED]
> Subject: Re: [PATCH 04/05] ipv6: RFC4214 Support
>
>
Hello.
In article <[EMAIL PROTECTED]> (at Tue, 6 Nov 2007 17:16:11 -0800), "Templin,
Fred L" <[EMAIL PROTECTED]> says:
> @@ -154,6 +155,14 @@ static struct ip_tunnel * ipip6_tunnel_l
> struct net_device *dev;
> char name[IFNAMSIZ];
>
> +#if defined(CONFIG_IPV6_ISATAP)
> + /* IS
orrectly deleted.
This has been fixed and tested.
Fred
[EMAIL PROTECTED]
> -Original Message-
> From: Templin, Fred L
> Sent: Tuesday, November 06, 2007 5:16 PM
> To: netdev@vger.kernel.org
> Subject: [PATCH 04/05] ipv6: RFC4214 Support
>
> From: Fred L. Templin <[
From: Fred L. Templin <[EMAIL PROTECTED]>
This is experimental support for the Intra-Site Automatic
Tunnel Addressing Protocol (ISATAP) per RFC4214. It uses
the SIT module, and is configured using the unmodified
"ip" utility with device names beginning with: "isatap".
The following diffs are spec
14 matches
Mail list logo
