netdev
[Top] [All Lists]

Re: routable interfaces

To: hadi@xxxxxxxxxx (jamal)
Subject: Re: routable interfaces
From: kuznet@xxxxxxxxxxxxx
Date: Mon, 15 Jan 2001 22:28:48 +0300 (MSK)
Cc: netdev@xxxxxxxxxxx
In-reply-to: <Pine.GSO.4.30.0101080642000.18916-100000@xxxxxxxxxxxxxxxx> from "jamal" at Jan 8, 1 04:15:02 pm
Sender: owner-netdev@xxxxxxxxxxx
Hello!

> A vlan device could be a simple IP-alias.

Sorry, Jamal you messed all the things completely.

ifaddr is not a virtual device. "Alias" was virtual device, but
this was bogus ill-defined device which created nothing but problems for 
routing,
that's why we have no "aliases", but use plain ifaddrs.

VLAN is true "virtual" device, using nice well-defined encapsulation,
and from viewpoint of routing/addressing such device is not distinguishable
of "physical" one. The question: "physical" or "virtual" is just meaningless
from the viewpoint of routing and from any other viewpoint but packet
scheduling and policing.

What's about VLANs, they can be handled as separate virtual devices
provided you have _couple_ of them. It the number is higher, they must
be clustered as single nbma interface via framing (i.e neighbour) level
or via tags in routing tables. The same thing is with MPLs.
That's why I strongly dislike the idea to create zillions of net_devices
and consider that approach to VLANs as stupid one. And this is reason
why hashing device list (being great in principle) is not considered
to be some really required feature.

Alexey

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