We currently have a single customer at the base of a tower who pays for 200 Mb of internet which comes from an airFiber 24. There was absolutely no room in their rack for a switch, so we used a EP-R6 to rate limit them to 200mbit. They have a public IP which comes back to a core router using layer 2, so I had to bridge this vlan through the EP-R6 using the bridge-group commands.
set interfaces ethernet eth0 vif 1105 bridge-group bridge br1105 set interfaces ethernet eth1 bridge-group bridge br1105
Then rate limit the port to 200mb.
set traffic-policy shaper 200mb bandwidth 220mbit set traffic-policy shaper 200mb default bandwidth 100% set traffic-policy shaper 200mb default burst '4k' set traffic-policy shaper 200mb default ceiling 100% set interfaces ethernet eth1 traffic-policy out 200mb
Previous lab testing showed that there is about 557mbit bottleneck through the EP-R6 using the bridge-group command, however this was more than sufficient for this application. We usually use a Cisco switch to do this, but there is ZERO room for a cisco in their rack. The outdoor form factor saved the day, but we now need to add a 2nd customer.
Today I see 1.8.5 has vlans as a new feature. I have tested it this morning, and there is zero bottleneck through the EP-R6 (Well, 700mbit is all I can confirm in my lab). However, this new configuration completely breaks the traffic-policy configuration. Now matter how I apply the policy (eth0 or switch0), I get 700mbit.
Is there a different way to configure the traffic-policy, or is it just not possible?