From owner-freebsd-net@FreeBSD.ORG Sat Oct 1 19:48:47 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B672E16A41F for ; Sat, 1 Oct 2005 19:48:47 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw0.york.ac.uk (mail-gw0.york.ac.uk [144.32.128.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B62F43D49 for ; Sat, 1 Oct 2005 19:48:46 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from buffy.york.ac.uk (buffy-128.york.ac.uk [144.32.128.160]) by mail-gw0.york.ac.uk (8.12.10/8.12.10) with ESMTP id j91Jmhrc011664 for ; Sat, 1 Oct 2005 20:48:43 +0100 (BST) Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.13.4/8.13.4) with ESMTP id j91JmhI3007824 for ; Sat, 1 Oct 2005 20:48:43 +0100 (BST) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: (from ga9@localhost) by buffy.york.ac.uk (8.13.4/8.13.4/Submit) id j91JmhDc007823 for freebsd-net@freebsd.org; Sat, 1 Oct 2005 20:48:43 +0100 (BST) (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin.atkinson@ury.york.ac.uk using -f From: Gavin Atkinson To: freebsd-net@freebsd.org Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Sat, 01 Oct 2005 20:48:42 +0100 Message-Id: <1128196122.7015.38.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk Subject: vlan(4), bge(4) and bringing parent interface up X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Oct 2005 19:48:47 -0000 Hi, It seems to me that assigning an IP address to a vlan device (parent device bge0) isn't enough to get the interface working - I need to manually bring the parent interface up. Freshly rebooted system with no network configuration in /etc/rc.conf wiggum# uname -a FreeBSD wiggum.york.ac.uk 6.0-BETA5 FreeBSD 6.0-BETA5 #2: Fri Sep 30 15:00:28 BST 2005 root@wiggum.york.ac.uk:/usr/obj/usr/src/sys/GENERIC amd64 wiggum# ifconfig -a bge0: flags=8802 mtu 1500 options=1a ether 00:09:3d:12:6c:06 media: Ethernet autoselect (10baseT/UTP ) status: active wiggum# ifconfig vlan66 inet 144.32.66.59 netmask 255.255.254.0 vlan 66 vlandev bge0 wiggum# ifconfig -a bge0: flags=8802 mtu 1500 options=1a ether 00:09:3d:12:6c:06 media: Ethernet autoselect (10baseT/UTP ) status: active vlan66: flags=8843 mtu 1500 inet 144.32.66.59 netmask 0xfffffe00 broadcast 144.32.67.255 inet6 fe80::209:3dff:fe12:6c06%vlan66 prefixlen 64 scopeid 0x4 ether 00:09:3d:12:6c:06 media: Ethernet autoselect (10baseT/UTP ) status: active vlan: 66 parent interface: bge0 wiggum# ping 144.32.66.200 PING 144.32.66.200 (144.32.66.200): 56 data bytes ^C --- 144.32.66.200 ping statistics --- 3 packets transmitted, 0 packets received, 100% packet loss wiggum# ifconfig bge0 up wiggum# ifconfig -a bge0: flags=8843 mtu 1500 options=1a inet6 fe80::209:3dff:fe12:6c06%bge0 prefixlen 64 scopeid 0x1 ether 00:09:3d:12:6c:06 media: Ethernet autoselect (10baseT/UTP ) status: active vlan66: flags=8843 mtu 1500 inet 144.32.66.59 netmask 0xfffffe00 broadcast 144.32.67.255 inet6 fe80::209:3dff:fe12:6c06%vlan66 prefixlen 64 scopeid 0x4 ether 00:09:3d:12:6c:06 media: Ethernet autoselect (10baseT/UTP ) status: active vlan: 66 parent interface: bge0 wiggum# ping 144.32.66.200 PING 144.32.66.200 (144.32.66.200): 56 data bytes 64 bytes from 144.32.66.200: icmp_seq=0 ttl=128 time=0.880 ms 64 bytes from 144.32.66.200: icmp_seq=1 ttl=128 time=0.960 ms ^C --- 144.32.66.200 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.880/0.920/0.960/0.040 ms Is this expected? I suspect it's a bug in either the vlan layer, or the bge interface code, but if it is expected it would be good to see this documented. I don't ever remember having to do anything special to get fxp cards working with vlans. Thanks, Gavin