From owner-freebsd-net@FreeBSD.ORG  Sat Feb  2 16:59:16 2008
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 0C9DA16A417
	for <freebsd-net@freebsd.org>; Sat,  2 Feb 2008 16:59:16 +0000 (UTC)
	(envelope-from freebsd-net@dino.sk)
Received: from loki.netlab.sk (loki.netlab.sk [84.245.65.11])
	by mx1.freebsd.org (Postfix) with ESMTP id 7A2AB13C44B
	for <freebsd-net@freebsd.org>; Sat,  2 Feb 2008 16:59:15 +0000 (UTC)
	(envelope-from freebsd-net@dino.sk)
Received: from fox.dino.sk (home.dino.sk [84.245.95.252])
	(AUTH: PLAIN milan, TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by loki.netlab.sk with esmtp; Sat, 02 Feb 2008 17:57:22 +0100
	id 0002E02F.47A4A0F2.0000ABBE
From: Milan Obuch <freebsd-net@dino.sk>
To: freebsd-net@freebsd.org
Date: Sat, 2 Feb 2008 17:58:46 +0100
User-Agent: KMail/1.9.7
References: <200802021307.44140.freebsd-net@dino.sk>
In-Reply-To: <200802021307.44140.freebsd-net@dino.sk>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200802021758.47316.freebsd-net@dino.sk>
Subject: Re: Weird rc.conf problem
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Feb 2008 16:59:16 -0000

On Saturday 02 February 2008, Milan Obuch wrote:
> Hi,
> I am getting weird problem with network configuration.
>
> In rc.conf I have (just for demonstation, only part)
>
> ifconfig_em0="polling"
>
> cloned_interfaces="vlan2"
> ifconfig_vlan2="vlan 2 vlandev em0"
> ifconfig_vlan2_name="em0.2"
>
> Result is incorrect:
>
> em0.2: flags=8003<UP,BROADCAST,MULTICAST> mtu 1500
>         ether 00:00:00:00:00:00
>         vlan: 0 parent interface: <none>
>
> If I use
>
> ifconfig_em0="polling up"
>
> cloned_interfaces="vlan2"
> ifconfig_vlan2="vlan 2 vlandev em0 name em0.2"
>
> Result is correct:
>
> em0.2: flags=8003<UP,BROADCAST,MULTICAST> mtu 1500
>         ether 00:11:22:33:44:55
>         vlan: 2 parent interface: em0
>
> In the latter case I am getting some
>
> ifconfig: interface vlan2 does not exist
>
> messages in dmesg, which I was trying to avoid.
>

It seems today is not my best, I found the simplest solution at last...

All I need is just one line in rc.conf:

cloned_interfaces="em0.2 em1.16 em1.28"

And one line in loader.conf:

if_vlan_load=YES

That's it. I have no if_vlan in kernel config, this was the reason I can't 
find this solution, which really works like I expected.

One should not mix too much old and new features I think.

Milan

-- 
This address is used only for mailing list response.
Do not send any personal messages to it, use milan in
address instead.