the filename must incorporate a valid device name, vlan0123 is not permitted (vlan0 is ok, otherwise the number must start with digit 1-9).
On 2010-03-15, silvershadow...@gmx.de <silvershadow...@gmx.de> wrote: > -------- Original-Nachricht -------- >> Datum: Mon, 15 Mar 2010 07:58:42 +0100 >> Von: Timo Schoeler <timo.schoe...@riscworks.net> >> An: misc@openbsd.org >> CC: silvershadow...@gmx.de >> Betreff: Re: VLAN across two (or more) different vlandevs? > >> > On 2010-03-12, silvershadow...@gmx.de <silvershadow...@gmx.de> wrote: >> >> Simply put, I need vlan 123 on both vr0 and vr2 (the Alix I use has >> >> three NICs, vr0 to vr2). >> > >> > the vlan device names (vlan123) do NOT need to be the same as the vlan >> ID. >> > >> > e.g.: >> > >> > hostname.vlan123 >> >> inet 10.11.0.3 255.255.255.0 NONE vlan 123 vlandev vr0 >> > >> > hostname.vlan1230 >> >> inet 222.111.222.111 255.255.255.0 NONE vlan 123 vlandev vr2 >> > >> > if this isn't what you want, describe in more detail what you're >> > trying to do. >> >> Hi, >> >> maybe you already tried this, but named the files like this: >> >> /etc/hostname.vlan0123 (vlan 123, vr0) >> >> and >> >> /etc/hostname.vlan2123 (vlan 123, vr2) >> >> ? >> >> I ran into a similar phenomenon quite a while ago. After renaming the >> files so that '0' was not the first digit (e.g. .vlan1230 and .vlan1232, >> respectively), it worked as supposed. >> >> HTH, >> >> Timo > > Hi! > > Wow, thanks, that was exactly the problem I had! > > After renaming it so that there's no 'zero' as the first number of the VLAN > naming scheme, it works flawlessly. > > However, AFAICS, the name of the file should be meaningless, shouldn't it? > So, is that a 'bug', or intended behaviour? > > Thanks again! > > Donald
