Hi gurus,

I had a wireless bridge that is working fine. I wanted to add a 2nd station, so I changed to AP-Bridge
and copied the settings on the station to a new one (with the appropriate IPs changed).

R0 (AP-BRIDGE)
VPLS1: ip=172.16.0.1
ETHER1: ip=192.168.0.18
WLAN1: ssid="wrcbridge"
BRIDGE: ports=ETHER1, VPLS1

R1 (station)
VPLS1: ip=172.16.0.2
ETHER1: ip=192.168.0.17
WLAN1: ssid="wrcbridge"
BRIDGE: ports=ETHER1, VPLS1

R2 (station)
VPLS1: ip=172.16.0.3
ETHER1: ip=192.168.0.19
WLAN1: ssid="wrcbridge"
BRIDGE: ports=ETHER1, VPLS1

Current state:
- Original bridge works fine (R0<->R1)
- New bridge (R0<->R2) - I can ping the VPLS address from the AP-Bridge, but I cannot ping the static IP on the Ethernet interface.

In reading some other posts, I see mention to ensure that the bridge l2mtu is less than wlan/vpls l2mtus.

In looking at my working station (R1), I see:
In looking at the non-working station (R2), I see:
I see 2 issues:
- Bridge1 L2MTU is 1526. I believe I need that to be 1500.
- VPLS1 is not running

How do I reset the l2mtu on Bridge1 on R2 ? I assume that's why VPLS1 is not happy.

Thanks for any pointers !

Ward

The bridge interface inherits the lowest supported MTU so 1500 is right.
Also if you have the ethernet interface that mpls/VPLS is running on in a bridge I don't think this works.

Looks like you have 3 devices all trying to be a part of the same VPLS tunnel?
I've never tried having a VPLS tunnel with 3 end points ? Didn't think it was possible

The bridge interface inherits the lowest supported MTU so 1500 is right.
Also if you have the ethernet interface that mpls/VPLS is running on in a bridge I don't think this works.

Looks like you have 3 devices all trying to be a part of the same VPLS tunnel?
I've never tried having a VPLS tunnel with 3 end points ? Didn't think it was possible

Thanks Inssomniak for the pointer !

Solution: I added a 2nd VPLS for R0<->R2, added it to the bridge on R0 and everything is behaving appropriately.