Date: Mon, 10 Jul 2006 10:44:05 +0300 (EEST) From: Dmitry Pryanishnikov <dmitry@atlantis.dp.ua> To: Sam Leffler <sam@errno.com> Cc: freebsd-arch@freebsd.org Subject: Re: vlans and cloning Message-ID: <20060710103404.I25526@atlantis.atlantis.dp.ua> In-Reply-To: <44B15511.206@errno.com> References: <44B15511.206@errno.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello! On Sun, 9 Jul 2006, Sam Leffler wrote: > clone operation? This would change the user api but otherwise I can see > no reason for continuing to support the old mechanism where you do: > > ifconfig vlan create > ifconfig vlan0 vlan 1 vlandev em0 > > Anyone _against_ nuking the above? Do you mean that you're going to nuke ifconfig vlan create but not ifconfig vlan0 create ? As I understand the flow of /etc/rc processing, support of the ifconfig vlan0 create ifconfig vlan0 vlan 1 vlandev em0 sequence is required for now. Also, I thing it's perfectly correct to have cloned_interfaces="vlan30" while NOT having 'ifconfig_vlan30' assignment - system administrator could just reserve a spare interface w/o assigning it's parameters. So I think that possibility of the specific device cloning w/o arguments, e.g., ifconfig vlan30 create should be preserved. Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: dmitry@atlantis.dp.ua nic-hdl: LYNX-RIPE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060710103404.I25526>