Date: Sat, 01 Oct 2005 20:48:42 +0100 From: Gavin Atkinson <gavin.atkinson@ury.york.ac.uk> To: freebsd-net@freebsd.org Subject: vlan(4), bge(4) and bringing parent interface up Message-ID: <1128196122.7015.38.camel@buffy.york.ac.uk>
next in thread | raw e-mail | index | archive | help
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<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
options=1a<TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
ether 00:09:3d:12:6c:06
media: Ethernet autoselect (10baseT/UTP <half-duplex>)
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<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
options=1a<TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
ether 00:09:3d:12:6c:06
media: Ethernet autoselect (10baseT/UTP <half-duplex>)
status: active
vlan66: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> 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 <half-duplex>)
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<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=1a<TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
inet6 fe80::209:3dff:fe12:6c06%bge0 prefixlen 64 scopeid 0x1
ether 00:09:3d:12:6c:06
media: Ethernet autoselect (10baseT/UTP <half-duplex>)
status: active
vlan66: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> 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 <half-duplex>)
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1128196122.7015.38.camel>