ros 5.4 new property in wireless interface

pljubas · Thu Jun 09, 2011 11:03 pm

Hi to all,

what does item Bridge Mode: in wireless interface means?
I'm using AP bridge and I'm wondering does this have to be enabled or disabled?

Thx, Petar

dallas · Thu Jun 09, 2011 11:23 pm

I am interested in this answer also.

lazerusrm · Fri Jun 10, 2011 12:35 am

From what i understand the "Bridge" Feature is a Mikrotik feature that will perform layer 2 bridging between two mikrotik devices without using any other type of tunneling (EOIP, VPLS, etc)

dallas · Fri Jun 10, 2011 12:52 am

That's what the interface/bridge is for right?

JorgeAmaral · Fri Jun 10, 2011 1:53 am

Please read here: http://wiki.mikrotik.com/wiki/Manual:Wi ... tion_Modes

Very quickly:
Same as wds, but without creating a new interface for each wds. Has the same speed limitations because the 802.11 frame is still built with the 4 mac.

Need to have a very careful design to avoid loops.

On AP you need to have bridge-mode=enabled and on cpe you can enable mode=station-bridge

Mikrotik proprietary.

I hope this helps a little bit.

Best regards,

dallas · Fri Jun 10, 2011 2:03 am

So I guess its a good way to pass the correct mac addresses of clients.

pljubas · Fri Jun 10, 2011 11:13 am

I guess it can't be used in situation that I have where all my wlan's are AP Bridge, no stations at all?

Petar

wpeople · Fri Jun 10, 2011 4:00 pm

Has the same speed limitations because the 802.11 frame is still built with the 4 mac.

is there a speed limitation using WDS?

JorgeAmaral · Fri Jun 10, 2011 5:14 pm

Has the same speed limitations because the 802.11 frame is still built with the 4 mac.
is there a speed limitation using WDS?

802.11a/b/g/n standard frame is composed by 3 MAC.

You can see it like this: PC -> Access-Point - > Gateway

If you want a transparent L2 bridge, it will have to behave diferent:

"PC1" -> 802.3 frame -> "station-wds" -> 802.11 wds frame -> "AP-bridge" -> 802.3 frame -> "PC2"

In this case, when the frame leaves PC1, it will be an 802.3 frame, with src mac and dst mac.

When it arrives to the sation-wds device, this frame will need to be converted to 802.11 wds frame, that will be composed by 4 mac.

In this case you will have src-mac, dst-mac, station-mac, AP-mac.

Finaly, when it reaches the AP, it will need again to be converted to 802.3 frame.

Now please read about what is AMSDU, AMPDU and how it helps on 802.11n networks.

This is the reason why Mikrotik recomends using AP + station + vpls tunnel on 802.11n L2 transparent P2P links.

Best regards,

pljubas · Fri Jun 10, 2011 6:19 pm

ok,

can this vpls tunnel be set up between two AP bridge wireless interfaces running 802.11b/g?

I actually need two tunnels to transport two different hotspot networks.

Any advice on that?

Petar

JorgeAmaral · Fri Jun 10, 2011 8:28 pm

ok,

can this vpls tunnel be set up between two AP bridge wireless interfaces running 802.11b/g?

I actually need two tunnels to transport two different hotspot networks.

Any advice on that?

Petar

My recomendation would be the two devices on AP-Bridge mode with wds between them, but do not add the wds interface to any bridge.

Set ip address directly on the wds interface, and create vpls tunnel between these to hosts. You can create multiple vpls tunnels between the same hosts, just set the vpls-id diferent for each tunnel.

Best regards,

pljubas · Fri Jun 10, 2011 9:04 pm

Hi Jorge,

that is interesting.

So setup will be:
RB 1
wlan
wds ip 10.10.10.1
vpls1
vpls2
vap

bridge1: wlan, vpls1
bridge2: vap, vpls2

the same on another router, except wds ip: 10.10.10.2

VPLS then uses wds for transport (ldp interface) or wlan?

Thx, I'll try this this evening.

Petar

lazerusrm · Sat Jun 11, 2011 12:12 am

as a side note, from my understanding, the new "bridge" feature is faster than WDS. Not sure how it compares to mpls/vpls

Here is an example configuration on one of my routers using MPLS/VPLS Tunneling to two sites. you can add as many more as you want and using a different vpls-id as stated above:

 [admin@MTK4] /mpls ldp> print
enabled: yes
lsr-id: 10.0.0.4
transport-address: 10.0.0.4
path-vector-limit: 255
hop-limit: 255
loop-detect: no
use-explicit-null: no
distribute-for-default-route: no

 [admin@MTK4] /interface vpls> print
Flags: X - disabled, R - running, D - d
B - bgp-signaled, C - cisco-bgp-signale
0 R   name="VPLS -> MTK5" mtu=1500 l2m
arp=enabled disable-running-chec
cisco-style=no cisco-style-id=0 
pw-type=raw-ethernet 

1 R   name="VPLS -> MTK3" mtu=1500 l2m
arp=enabled disable-running-chec
cisco-style=no cisco-style-id=0 
pw-type=raw-ethernet

[admin@MTK4] /interface bridge port> print
Flags: X - disabled, I - inactive, D - dynamic 
 #    INTERFACE                     BRIDGE                     PRIORITY  PATH-COST    HORIZON
 0    ether1                       MTK4 -> BDHM            0x80         10       none
 2    VPLS -> MTK5                  MTK4 -> BDHM            0x80         10       none
 3    VPLS -> MTK3                  MTK4 -> BDHM            0x80         10       none

ros 5.4 new property in wireless interface

ros 5.4 new property in wireless interface

Re: ros 5.4 new property in wireless interface

Re: ros 5.4 new property in wireless interface

Re: ros 5.4 new property in wireless interface

Re: ros 5.4 new property in wireless interface

Re: ros 5.4 new property in wireless interface

Re: ros 5.4 new property in wireless interface

Re: ros 5.4 new property in wireless interface

Re: ros 5.4 new property in wireless interface

Re: ros 5.4 new property in wireless interface

Re: ros 5.4 new property in wireless interface

Re: ros 5.4 new property in wireless interface

Re: ros 5.4 new property in wireless interface

Who is online