DragonFly bugs List (threaded) for 2007-05
DragonFly BSD
DragonFly bugs List (threaded) for 2007-05
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: [issue589] VLAN issues


From: Gergo Szakal <bastyaelvtars@xxxxxxxxx>
Date: Sat, 19 May 2007 22:30:27 +0200

The patch (the xl mtu and the vlan promisc) applies and compiles fine, and the warning is indeed gone. Now I found out that I should rather create separate bridge interfaces for the vlan's by ID. Let's see:

cloned_interfaces="bridge0 bridge1 vlan0 vlan1 vlan2 vlan3"
ifconfig_xl0="up"
ifconfig_xl1="up"
ifconfig_vlan2="vlan 11 vlandev xl1 up"
ifconfig_vlan3="vlan 12 vlandev xl1 up"
ifconfig_vlan0="vlan 11 vlandev xl0 up"
ifconfig_vlan1="vlan 12 vlandev xl0 up"
ifconfig_bridge0="addm vlan0 addm vlan2 up"
ifconfig_bridge1="addm vlan1 addm vlan3 up"

I get in dmesg:

bridge0: MAC address: fe:84:dc:d5:af:e8
bridge1: MAC address: 4e:26:12:cc:2c:51
vlan0: MAC address: 00:00:00:00:00:00
vlan1: MAC address: 00:00:00:00:00:00
vlan2: MAC address: 00:00:00:00:00:00
vlan3: MAC address: 00:00:00:00:00:00


ifconfig:

xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=8<VLAN_MTU>
        inet6 fe80::210:5aff:fed6:e44%xl0 prefixlen 64 scopeid 0x1 
        ether 00:10:5a:d6:0e:44
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
xl1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=8<VLAN_MTU>
        inet6 fe80::204:76ff:fedf:d8ac%xl1 prefixlen 64 scopeid 0x2 
        ether 00:04:76:df:d8:ac
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet6 fe80::230:4fff:fe08:b5d0%rl0 prefixlen 64 scopeid 0x3 
        inet 10.0.0.22 netmask 0xffffff00 broadcast 10.0.0.255
        ether 00:30:4f:08:b5:d0
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
bridge0: flags=8002<BROADCAST,MULTICAST> mtu 1500
        ether fe:84:dc:d5:af:e8
        priority 32768 hellotime 2 fwddelay 15 maxage 20
bridge1: flags=8002<BROADCAST,MULTICAST> mtu 1500
        ether 4e:26:12:cc:2c:51
        priority 32768 hellotime 2 fwddelay 15 maxage 20
vlan0: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        ether 00:10:5a:d6:0e:44
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
        vlan: 11 parent interface: xl0
vlan1: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        ether 00:10:5a:d6:0e:44
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
        vlan: 12 parent interface: xl0
vlan2: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        ether 00:04:76:df:d8:ac
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
        vlan: 11 parent interface: xl1
vlan3: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        ether 00:04:76:df:d8:ac
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
        vlan: 12 parent interface: xl1

--------------------------------------------------------------------------

When I add the physical interface on one side:

ifconfig_bridge0="addm xl0 addm vlan2 up"
ifconfig_bridge1="addm xl0 addm vlan3 up"

then it gets added to the bridge as a member, but vlan interfaces still do not get added. Let's add:

%ifconfig bridge0 addm vlan2 up
ifconfig: BRDGADD vlan2: Network is down

So vlan interfaces start as "down" and don't get added to the bridge.



[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]