Date: Sun, 17 Jun 2007 11:05:38 +0300 From: "Miroslav Slavkov" <miroslav@svishtov.net> To: freebsd-net@freebsd.org Subject: Re: Quickly creating VLANs? Message-ID: <20070617080538.93f72c53@mail.svishtov.net> In-Reply-To: 46747735.5010603@monkeybrains.net
next in thread | raw e-mail | index | archive | help
# ifconfig vlan100 create inet 1.2.3.4/24 vlan 100 vlandev xl0
# ifconfig vlan100
vlan100: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 1.2.3.4 netmask 0xffffff00 broadcast 1.2.3.255
ether 00:10:5a:48:ce:a4
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
vlan: 100 parent interface: xl0
_____
From: Rudy Rucker [mailto:crapsh@monkeybrains.net]
To: freebsd-net@freebsd.org
Sent: Sun, 17 Jun 2007 02:50:13 +0300
Subject: Re: Quickly creating VLANs?
Works for me, but if you put in the 'inet' if breaks.
# ifconfig vlan600 create vlan 600 vlandev fxp1 inet 10.20.0.1/24
ifconfig: inet: bad value
man ifconfig:
Since an interface can receive transmissions in differing
protocols with different naming schemes, specifying the
address family is recommended.
either needs to be revised to:
except when creating a vlan, 'cause that causes sh*t to break
or, the ifconfig command needs to accept 'inet' when creating a vlan.
Is inet inherited from the 'vlandev' and therefore redundant?
Rudy
Pieter de Boer wrote:
> Ivan Voras wrote:
>
>> ifconfig vlan600 destroy
>> ifconfig vlan600 create
>> ifconfig vlan600 vlan 600 vlandev fxp1
>> ifconfig vlan600 inet 10.20.0.1 netmask 255.255.255.0
> Try ifconfig vlan600 create vlan 600 vlandev fxp1 10.20.0.1/24
>
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070617080538.93f72c53>