"ifconfig -vlandev" syntax

[Yar Tikhiy]

On Wed, Sep 28, 2005 at 12:57:42PM +0200, Bernd Walter wrote:
> On Wed, Sep 28, 2005 at 02:32:41PM +0400, Yar Tikhiy wrote:
> > On Mon, Sep 26, 2005 at 12:54:33AM +0200, Bernd Walter wrote:
> > > On Sun, Sep 25, 2005 at 11:08:25PM +0100, Gavin Atkinson wrote:
> > > > 
> > > > Also, you can't set both the vlan and IP address information:
> > > > leeloo# ifconfig vlan14 vlan 14 vlandev fxp0 inet W.X.Y.Z netmask 255.255.255.0
> > > > ifconfig: inet: bad value
> > > > 
> > > > As a result of this, the only way to create vlans from rc.conf seems to
> > > > be in two stages, by renaming the interface:
> > > > 
> > > > cloned_interfaces="vlan14"
> > > > ifconfig_vlan14="vlan 14 vlandev fxp0 name somename"
> > > > ifconfig_somename="inet W.X.Y.Z netmask 255.255.255.0"
> > > 
> > > The follwing always worked for me, no need to rename:
> > > cloned_interfaces="vlan1"
> > > ifconfig_vlan1="inet 1.2.3.4/29 vlan 1 vlandev fxp0"
> > 
> > Indeed, the address assignment arguments should precede other
> > parameters to ifconfig(8).  I think this is evident from the syntax
> > shown on the manpage.
> > 
> > > What doesn't work is this:
> > > ifconfig_vlan1_alias0="1.2.3.4/32"
> > > I had to configure them by a selfdone script.
> > 
> > Adding aliases on vlanX this way has been working for me.  Could
> > you check if prepending the "inet" keyword before the address changes
> > anything?  I prefer to specify address family explicitly in my
> > rc.conf files.  E.g.:
> > 
> > 	ifconfig_vlan1_alias0="inet 1.2.3.4/32"
> 
> Sorry, but the configuration is used on a production machine that
> I can't do tests on.

Just tested without "inet", and it still worked for me.

-- 
Yar