On Wednesday 29 November 2006 02:53, Ard van Breemen wrote:
> For an alias the actual interface must already exist.
> The vlan-raw-device should therefore not appear on the alias
> definition, as this tries to create the interface. (This is
> probably true for all such constructions like tunnels and
> bridges).
> So if you remove the vlan-raw-device from the alias definition,
> it should work as you want it.
You are right even the construction like eth0.2:0 works. However, I was being
tripped up by the error messages. For instance, check this out:
pyrus:/home/wt# ifup eth0.2
Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config
Added VLAN with VID == 2 to IF -:eth0:-
pyrus:/home/wt# ifup eth0.2:0
Interface eth0.2:0 does not exist
pyrus:/home/wt# ip addr show dev eth0.2
19: [EMAIL PROTECTED]: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:08:74:b6:ed:ee brd ff:ff:ff:ff:ff:ff
inet 192.168.3.88/24 brd 192.168.3.255 scope global eth0.2
inet 192.168.3.89/24 brd 192.168.3.255 scope global secondary eth0.2:0
inet6 fe80::208:74ff:feb6:edee/64 scope link
valid_lft forever preferred_lft forever
Why does it say that "eth0.2:0 does not exist" yet still bring up the device.
That looks suspiciously like an error message, and it's at least confusing.
The same goes for the "Set name-type..." and maybe also for the "Added
VLAN..." message.
I guess this bug can be retitled to "Please improve UI for ifupdown vlan
enhancement scripts" and severity changed to wishlist.
It would also be nice if an example for the aliasing were added to the manpage
and the manpage didn't say "# Aliases are ignored" since that is apparently
not true.
wt
--
Warren Turkal, Research Associate III/Systems Administrator
Colorado State University, Dept. of Atmospheric Science
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
