Mailinglist Archive: opensuse-virtual (32 mails)

[PGNet <pgnet.trash+osvm@xxxxxxxxx>]

On Mon, Jan 5, 2009 at 6:35 AM, James Oakley <jfunk@xxxxxxxxxxxx> wrote:
> To create a vlan, you need to create an ifcfg-vlan<num> file under
...

Seems straightforward, but, per your config, after reboot, ifconfig
shows no trace of a vlan (it's supposed to, right?).

missing kernel mod maybe? one of these?

lsmod | grep -i vlan
locate -i vlan |grep -i ko
 /lib/modules/2.6.25.18-0.2-default/kernel/drivers/net/macvlan.ko
 /lib/modules/2.6.25.18-0.2-default/kernel/net/bridge/netfilter/ebt_vlan.ko
 /lib/modules/2.6.25.18-0.2-xen/kernel/drivers/net/macvlan.ko
 /lib/modules/2.6.25.18-0.2-xen/kernel/net/bridge/netfilter/ebt_vlan.ko

or yet something else?


> Also, you can name your bridge interfaces to anything you want, but vlan
> devices always have to be named vlan<num>. On Xen systems, I usually give the
> bridges descriptive names, which helps when selecting which bridge to use when
> deploying a domU.

That's what I do with as well with bridges.  I was not aware of the
naming restriction for vlans -- just had used the numbering convention
by happenstance.

Thanks.
-- 
To unsubscribe, e-mail: opensuse-virtual+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-virtual+help@xxxxxxxxxxxx