Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 03 Sep 2014 00:34:14 +0200
From:      Marek Salwerowicz <marek_sal@wp.pl>
To:        "Dustin J. Mitchell" <dustin@v.igoro.us>,  Marek Salwerowicz <marek_sal@wp.pl>
Cc:        freebsd-net@freebsd.org, Peter Jeremy <peter@rulingia.com>
Subject:   Re: bridging VLAN interfaces and STP
Message-ID:  <540645E6.2050809@wp.pl>
In-Reply-To: <CAJtE5vQxeaufx2LPYxOHcixhm5QiV49Y7Ab2DkpKhSdbE0_YUA@mail.gmail.com>
References:  <CAJtE5vRq8oJz1f8ujsTSjGJjoEMp_J-n6Nqj0YCUd_nrScnPqA@mail.gmail.com>	<CAJtE5vQLdtXtyejKUHkX1DKfVS-SaVF4n3=nfA%2BecH4Jhn3VXQ@mail.gmail.com>	<20120827094956.GA93853@server.rulingia.com>	<CAJtE5vSQ2W_H_jsr=BA7e0pcU1wJ_qiKHTSc3W2AuWbWgAjvpA@mail.gmail.com>	<20120901215514.GA84970@server.rulingia.com>	<CAJtE5vQn-ToGhMqPw3By8M4Mi_ycpkR33qxQRwT=ezKv5PTmhg@mail.gmail.com>	<540625B4.6040907@wp.pl> <CAJtE5vQxeaufx2LPYxOHcixhm5QiV49Y7Ab2DkpKhSdbE0_YUA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
W dniu 2014-09-02 o 22:27, Dustin J. Mitchell pisze:
> No, I never figured it out.  I never really even got Peter to
> understand the problem - he was still asking about whether STP packets
> were on the wire when I left the issue, yet the problem is interface
> configuration, not traffic.
>
> FreeBSD doesn't support configuring STP on VLAN interfaces - whether
> that's a bug or a feature is for someone else to decide.  I can
> confirm it is still the case:

Does the bridge without STP work for you ?

What do you actually bridge? As I see, there are 2 physical interfaces 
and 1 vlan

I am wondering if the STP is really necessary for bridging vlan with 
wlan0 interface, but so far I can't figure out the answer


Marek


>
> hilbert ~ # sysctl -n kern.osrelease kern.ostype
> 9.2-RELEASE-p10
> FreeBSD
> hilbert ~ # ifconfig bridge10
> bridge10: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
>          ether 02:f4:a1:63:5a:0a
>          inet6 fe80::f4:a1ff:fe63:5a0a%bridge10 prefixlen 64 scopeid 0xd
>          inet 172.16.1.21 netmask 0xffffff00 broadcast 172.16.1.255
>          inet 172.16.1.1 netmask 0xffffffff broadcast 172.16.1.1
>          inet6 2001:470:1f11:826::1:15 prefixlen 64
>          inet6 2001:470:1f11:826::1:1 prefixlen 128
>          nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
>          id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
>          maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
>          root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
>          member: vr3 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
>                  ifmaxaddr 0 port 4 priority 128 path cost 55
>          member: vr2 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
>                  ifmaxaddr 0 port 3 priority 128 path cost 200000
>          member: vr1.10 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
>                  ifmaxaddr 0 port 9 priority 128 path cost 200000
> hilbert ~ # ifconfig vr1.10
> vr1.10: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST>
> metric 0 mtu 1500
>          ether 00:00:24:ce:ec:95
>          inet6 fe80::200:24ff:fece:ec95%vr1.10 prefixlen 64 scopeid 0x9
>          nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
>          media: Ethernet autoselect (100baseTX <full-duplex>)
>          status: active
>          vlan: 10 parent interface: vr1
> hilbert ~ # ifconfig bridge10 stp vr1.10
> ifconfig: unable to set bridge flags: Invalid argument
>
> Dustin
>
> On Tue, Sep 2, 2014 at 4:16 PM, Marek Salwerowicz <marek_sal@wp.pl> wrote:
>> Hello Dustin,
>>
>> W dniu 2012-09-02 o 01:13, Dustin J. Mitchell pisze:
>>> On Sat, Sep 1, 2012 at 5:55 PM, Peter Jeremy<peter@rulingia.com>  wrote:
>>>>> That looks like RSTP is enabled on both bridge10 and bridge20 but is
>>>>> not seeing incoming [R]STP packets.  Are you sure the switch connected
>>>>> to vr1 is configured with per-VLAN STP (this is probably not the
>>>>> switch default).
>>>>>
>>>>> Have you tried running tcpdump on vr1 and checked that you are seeing
>>>>> STP packets within the VLANs.
>>> Actually, if you compare with my original ifconfig, you'll see that
>>> this particular arrangement shows STP as enabled on the bridge, but
>>> not on any of the members (no STP in their options.  In the OP, you
>>> can see that the vr{2,3} get STP in their flags
>>> (<LEARNING,DISCOVER,STP,AUTOEDGE,AUTOPTP>) while vr1.10 does not.
>>> That, and the error message from the 'ifconfig bridge10 stp vr1.10'
>>> command..
>>
>>
>> I'd like to ask if have you managed to figure out this issue? I am facing
>> more or less the same problem
>>
>> I have set up multiple VLANs on my FreeBSD box and now would like to bridge
>> WiFi adapter (wlan0) with only one vlan:
>>
>> When I try to configure bridge:
>>
>> % sudo ifconfig bridge create
>> % sudo ifconfig bridge addm wlan0
>> % sudo ifconfig bridge addm vlan1200
>> bridge0: error setting interface capabilities on vlan1200
>> % sudo ifconfig bridge stp wlan0
>> % sudo ifconfig bridge0 stp vlan1200
>> ifconfig: unable to set bridge flags: Invalid argument
>>
>> % ifconfig bridge0
>> bridge0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
>>          ether 02:8e:2e:18:3e:00
>>          nd6 options=9<PERFORMNUD,IFDISABLED>
>>          id 04:f0:21:0f:77:d7 priority 32768 hellotime 2 fwddelay 15
>>          maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
>>          root id 04:f0:21:0f:77:d7 priority 32768 ifcost 0 port 0
>>          member: vlan1200 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
>>                  ifmaxaddr 0 port 6 priority 128 path cost 20000
>>          member: wlan0 flags=147<LEARNING,DISCOVER,STP,AUTOEDGE,AUTOPTP>
>>                  ifmaxaddr 0 port 11 priority 128 path cost 33333 proto rstp
>>                  role designated state discarding
>>
>>
>> If I change vlan1200 to physical interface, everything works without any
>> problems..
>>
>> Do you have any idea?
>>
>> Cheers,
>>
>> Marek
>>
>>
>>




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?540645E6.2050809>