Hi guys,
I’m struggling to implement traffic shaping with a hEX S (v6.45.6) for the following design, involving traffic tagged and untagged. All my attempts were unsuccessful either with simple queue or with mangle rules + queues.
I’ve created two bridges on hEX S:
Bridge_A = traffic tagged vlan_id 101 from ether2 to ether4
Bridge_B =
a. traffic tagged vlan_id 102 from ether2 to ether 4
b. traffic tagged vlan_id 102 from ether2 to untagged port ether 3 (access)
I’ve tried to create simple queues to limit the traffic based of the interface (target port) but nothing’s happening
I’ve tried to create mangle rules marking in/out connections on interface and then making queues to limit the traffic but nothing’s happening
Could you please help me to implement this traffic shaping & policing?
The only point where I can control the bandwidth is on ether3, since the traffic is untagged and I can create a simple queue which can have as target the IP address of the ServerA.
I didn’t find yet a solution for those two vlans (101,102) which are bridged from ether2 to ether4.
Is there anybody can help on this matter please?
Thank you advance!
Hi Sindy,
Sorry for this late reply. I did not manage to make any progress to fix it up, so I still need your help.
Indeed, I want to limit throughput for the traffic being bridged between ether2 and ether4. I had many attempts to use as target the interface the all of them were unsuccessful.
Do you have an idea how can I do it?
Sorry, I’ve confused two similar topics so I didn’t care much about the notifications of this one.
To make it possible for bridged packets to be queued, you have to disable hardware acceleration of the bridge (/interface bridge port set [find interface~“ether[24]”] hw=no), and under /interface bridge settings, you have to set use-ip-firewall and use-ip-firewall-for-vlan (in your case) to yes.
Once you do this, you can use /interface bridge filter rules with action=mark-packet to assign packet-marks to frames being bridged depending on their in-interface, vlan-id, and maybe other criteria, and use queues in /queue tree marked with those packet-marks to handle the traffic.
If you need a more detailed description, give me more detailed classification criteria.