[Xorp-users] VLAN support in XORP
Dan Lukes
dan at obluda.cz
Wed Sep 26 03:35:25 PDT 2007
Pavlin Radoslavov napsal/wrote, On 09/26/07 11:01:
> The first-cut VLAN support is now committed in the CVS tree.
...
> In term of VLAN naming, the situation is the following.
> In FreeBSD (and I believe in other BSDs as well, but I haven't
> double-checked it yet), the vlan name has to be "vlan%d". However,
> the integer after "vlan" doesn't need to match the VLAN ID. E.g.,
> vlan10 could have VLAN ID of, say, 20.
Unfortunately, no. It is "default" name, but the real interface name
can be set to anything the administrator wish.
On out network, the number after 'vlan' often match the VLAN ID. But I
have interface named DEVILLAN also.
You shall not derive any information about interface type nor
underlying configuration from it's name.
If you need specific information about a interface (as a type, VLAN ID
or parent interface), you need to use os-specific routines to obtain it.
By the way, configuration file shall contain configuration, not
description of the OS that can be obtained from OS itself.
Dis-synchronisation between real system configurations and it's
description in xorp.conf is common source of problems.
I mean - why I need to encode that interface vlan10 is virtual
interface derived from parent fxp0 into xorp.conf ? It's information
that can be extracted from OS (if you really need it), so it shall be
extracted from OS, not from configuration file. The BSD make those
informations available for application. I'm sure the Linux does it also
as well.
Dan
--
Dan Lukes SISAL MFF UK
AKA: dan at obluda.cz, dan at freebsd.cz, dan at (kolej.)mff.cuni.cz
More information about the Xorp-users
mailing list