transparent traffic shaper

djhurt1 · April 2, 2006, 5:03am

I’ve gone through the “how-to” on the MT home page for the transparent traffic shaper and it worked on 2.9.9. I’ve upgraded to 2.9.18 and now the
“/interface bridge port set ext,int bridge=bridge” command says invalid item number. I’ve tried using the item numbers in place and nothing seems to work. Any ideas?
Aaron

yancho · April 2, 2006, 8:14am

Create bridge

 /interface bridge add name=bridge

Add interfaces to bridge, ether1 and ether2 are interfaces names

/interface bridge port add ether1 bridge=bridge
/interface bridge port add ether2 bridge=bridge

Manual and how-to is outdated

djhurt1 · April 3, 2006, 5:43pm

No, this still doesn’t work. I renamed the interfaces to public, private respectively. I changed the names back to default and still no go.

gottin · April 3, 2006, 5:56pm

I have the same problem on 2.9.6 version.

I have done a lot of shapes on non bridge interfaces and they work fine. However when marking traffic in/out of interface (that is specified to be a bridge port) that traffic is not going into any queue. I tried to use “/queue simple” as explained in howto as well as “/queue tree” queues - No results.

Is there something specific that should be done when shaping traffic on bridge interfaces?

djhurt1 · April 3, 2006, 7:48pm

I think I found a solution at least to my problem. When adding interfaces to the bridge, I had to type the “set” command by itself and follow the prompts it provided. I couldn’t do it as one whole command line format.
Aaron

gottin · April 3, 2006, 9:42pm

Well I have my bridge set up and running, however I can not shape traffic on it.

BurstNET · April 4, 2006, 1:59am

See out earlier thread over past couple months…you cannot shape properly on a transparent bridge and it must be routed.

SMA

gottin · April 4, 2006, 6:06am

It really looks that I can not shape traffic on a transparent bridge. However it is strange that the guys from MikroTik have posted an article HowTo shape on it! (http://www.mikrotik.com/Documentation/HowTo.html#How_shaper)

postmanerk · April 6, 2006, 2:36pm

I can tell you that I am using a transparent bridge for the main QoS router, but I am running 2.2.28 on it. So to answer your question, it should work. However, I am not seeing the same result on 2.9.18-19. I don’t know if the problems are related, but to me they might because of the interaction with a bridge interface.

One thing I am seeing is that I have a router, that is on a tower, and the eth1 interface is the backhaul… I am routing between the eth1 and 3 other (eth2-4) interfaces in a bridge (so I am not the same as a transparent bridge). When I try and create a /queue tree who’s parent is the bridge interface, I am getting nothing in the counters, and it doesn’t look like it is processing. On the eth1 side of the queues, it does increment properly and they are using the same packet tags as the bridge. I validated my configs with another router (identical setup) running 2.8.28 and it works properly…

I have tried in the /ip firewall mangle rules both prerouting and forward but both rules do not tag the packets properly or the bridge interface queue is missing the packet tags.

Am I beating my head against the wall or am I missing something? I am trying to do VoIP QoS tagging based on my own server IP. The mangle rules are as follows:

add chain=forward src-address=[IPADDRESS] action=mark-packet new-packet-mark=“Local VoIP Flow” passthrough=no comment=“VoIP” disabled=no
add chain=forward dst-address=[IPADDRESS] action=mark-packet new-packet-mark=“Local VoIP Flow” passthrough=no comment=“” disabled=no

Eric

gottin · April 10, 2006, 7:58am

Would someone from MT support explain us why MT 2.9.x can not mark packets that are flowing through bridge interfaces? Should we wait for a fix?

postmanerk · April 12, 2006, 12:05am

Can anyone else verify that a bridged interface cannot increment counters?

Anyone from MikroTik on here?

Eric

Eugene · April 12, 2006, 5:22pm

Works fine for me. I.e.:

/ip firewall mangle add chain=forward out-bridge-port=ether2 action=mark-packet new-packet-mark=MyMark

marks packets and increments counters as it should …

postmanerk · April 27, 2006, 6:25pm

My /ip firewall mangle counters do increment, but in the /queue trees do not increment. The queue tree rules I have my parent as the bridge interface and the packet mark as the one in the mangle rules.

Simple test is just IP based. I am trying to do a VoIP prioritization by just using one IP and tag it as my internal VoIP server. Should be a simple example, right? This all works on my 2.8.26-28 versions, but I cannot do the same on 2.9.x.

First, mark packets:
/ ip firewall mangle
add chain=forward src-address=68.77.78.25 action=mark-packet new-packet-mark=“Local VoIP Flow” passthrough=no
comment=“VoIP” disabled=no
add chain=forward dst-address=68.77.78.25 action=mark-packet new-packet-mark=“Local VoIP Flow” passthrough=no comment=“”
disabled=no

Then Queue them:
/ queue tree
add name=“Global - In” parent=“Wireless Bridge” packet-mark=“” limit-at=0 queue=default priority=8 max-limit=0
burst-limit=0 burst-threshold=0 burst-time=0s disabled=no
add name=“Global - Out” parent=“Ether2 - Backhaul” packet-mark=“” limit-at=0 queue=default priority=8 max-limit=0
burst-limit=0 burst-threshold=0 burst-time=0s disabled=no
add name=“Internet - In” parent=“Global - In” packet-mark=“” limit-at=0 queue=“Internet Global” priority=8 max-limit=0
burst-limit=0 burst-threshold=0 burst-time=0s disabled=no
add name=“Internet - Out” parent=“Global - Out” packet-mark=“” limit-at=0 queue=“Internet Global” priority=8 max-limit=0
burst-limit=0 burst-threshold=0 burst-time=0s disabled=no
add name=“VoIP - In” parent=“Internet - In” packet-mark=“VoIP Flow” limit-at=1500000 queue=VoIP priority=4
max-limit=1500000 burst-limit=0 burst-threshold=0 burst-time=0s disabled=no
add name=“VoIP - Out” parent=“Internet - Out” packet-mark=“VoIP Flow” limit-at=1500000 queue=VoIP priority=4
max-limit=1500000 burst-limit=0 burst-threshold=0 burst-time=0s disabled=no
add name=“Local - In” parent=“Global - In” packet-mark=“Local Traffic Flow” limit-at=0 queue=default priority=8
max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s disabled=no
add name=“Local - Out” parent=“Global - Out” packet-mark=“Local Traffic Flow” limit-at=0 queue=default priority=8
max-limit=0 burst-limit=0 burst-threshold=0 burst-time=0s disabled=no
add name=“Local VoIP - In” parent=“Local - In” packet-mark=“Local VoIP Flow” limit-at=1500000 queue=“Local VoIP”
priority=3 max-limit=3000000 burst-limit=0 burst-threshold=0 burst-time=0s disabled=no
add name=“Local VoIP - Out” parent=“Local - Out” packet-mark=“Local VoIP Flow” limit-at=1500000 queue=“Local VoIP”
priority=3 max-limit=3000000 burst-limit=0 burst-threshold=0 burst-time=0s disabled=no

valens · April 27, 2006, 8:30pm

I’m using Mikrotik 2.9.20 using transparant bridge, and every thing work fine. I’m using this config since 2.9.1

e2346437 · April 28, 2006, 2:43am

I just upgraded to 2.9.22 on my transparent bridge, and I can’t seem to get queue trees (pcq) to work at all. I’ve got it running on an RB500 that is doing routing, but I can’t seem to get it working on bridge.

To be more specific, the example in the Wiki seems to only work for upload on my bridge, not download. The example in the manual does not work at all.

Can anybody confirm for SURE that queue trees DO or DO NOT work with a transparent bridge running 2.9.22?

Eric

valens · April 28, 2006, 11:10am

It DO work.

postmanerk · April 29, 2006, 3:15am

valens,

Would you post a smidgeon of your config so I can try it on my router? I posted my config, and if you run it through (changing your IP), it may not work for you.

I have the exact config on a 2.8.28 router and it works. I have it on a 2.9.22 router and it does not. Same code, just different versions (syntax).

Eric

e2346437 · April 29, 2006, 2:09pm

I can confirm that the exact config does not work on my 2.9.22 bridge either.

Eric

valens · April 30, 2006, 5:33pm

[valens@BM] interface> pr
Flags: X - disabled, D - dynamic, R - running 
 #    NAME                         TYPE             RX-RATE    TX-RATE    MTU  
 0  R ether1                       ether            0          0          1500 
 1  R ether2                       ether            0          0          1500 

[valens@BM] interface bridge port> pr
Flags: X - disabled, I - inactive, D - dynamic 
 #    INTERFACE BRIDGE  PRIORITY PATH-COST
 0    ether1    bridge1 128      10       
 1    ether2    bridge1 128      10       

[valens@BM] ip firewall mangle> pr
16   ;;; Citraweb Office
     chain=forward src-address=202.0.0.0/26 action=mark-connection 
     new-connection-mark=citraweb-conn passthrough=yes 
17   chain=forward connection-mark=citraweb-conn action=mark-packet new-packet-mark=citraweb-flow 
     passthrough=yes 

[valens@BM] queue tree> pr

 6   name="Internal-Downlink" parent=ether2 packet-mark="" limit-at=0 queue=default priority=1 
     max-limit=512000 burst-limit=0 burst-threshold=0 burst-time=0s 

 7   name="Internal-Uplink" parent=ether1 packet-mark="" limit-at=0 queue=default priority=1 
     max-limit=384000 burst-limit=0 burst-threshold=0 burst-time=0s 

115   name="Citraweb-Downlink" parent=Internal-Downlink packet-mark=citraweb-flow limit-at=0 
     queue=default priority=4 max-limit=256000 burst-limit=0 burst-threshold=0 burst-time=0s 

116   name="Citraweb-Uplink" parent=Internal-Uplink packet-mark=citraweb-flow limit-at=0 
     queue=default priority=8 max-limit=128000 burst-limit=0 burst-threshold=0 burst-time=0s

valens · April 30, 2006, 5:34pm

Screen Capture: