netdev
[Top] [All Lists]

Re: routable interfaces WAS( Re: [PATCH] hashed device lookup(DoesNOT

To: jamal <hadi@xxxxxxxxxx>
Subject: Re: routable interfaces WAS( Re: [PATCH] hashed device lookup(DoesNOT meet Linus' sumission policy!)
From: Sandy Harris <sandy@xxxxxxxx>
Date: Sun, 07 Jan 2001 14:19:19 -0500
Cc: linux-kernel <linux-kernel@xxxxxxxxxxxxxxx>, "netdev@xxxxxxxxxxx" <netdev@xxxxxxxxxxx>
References: <Pine.GSO.4.30.0101071321330.18916-100000@shell.cyberus.ca>
Sender: owner-netdev@xxxxxxxxxxx
jamal wrote:

> > What problem does this fix?
> >
> > If you are mucking with the ifindex, you may be affecting many places
> > in the rest of the kernel, as well as user-space programs which use
> > ifindex to bind to raw devices.
>
> I am talking about 2.5 possibilities now that 2.4 is out. I think
> "parasitic/virtual" interfaces is not a issue specific to VLANs.
> VLANs happen to use devices today to solve the problem.
> As pointed by that example no routing daemons are doing aliased
> interfaces (which are also virtual interfaces).
> We need some more general solution.
> 
Something like this also becomes an issue when you want routing
daemons to interact sensibly with IPSEC tunnels. A paper on these
issues is at:

http://www.quintillion.com/fdis/moat/ipsec+routing/

It is not (AFAIK) clear that the FreeS/WAN team will adopt the solutions
suggested there, but it is very clear we need to deal with those issues.

<Prev in Thread] Current Thread [Next in Thread>