Feature #4405
openTraffic shaping doesn't work when applied to a bridge interface
0%
Description
Having two or more interfaces within a bridge, the traffic shaper doesn't work when applied to it. Traffic is seen on the member interfaces instead of the bridge.
Appropriate tunables are configured (net.link.bridge.pfil_member and net.link.bridge.pfil_bridge). This worked fine on 2.1.x. Should be pretty simple to reproduce.
This behavior is essential to achieve proper download shaping on multi-LAN setups.
Updated by Chris Buechler almost 10 years ago
- Target version changed from 2.2.1 to 2.2.2
Updated by Chris Buechler over 9 years ago
- Target version changed from 2.2.2 to 2.2.3
Updated by Chris Buechler over 9 years ago
- Target version changed from 2.2.3 to 2.3
Updated by William van de Velde over 9 years ago
I have here the exact same issue.
Any news on this one, as this is the only possibility to borrow bandwidth from each other when having multiple physical interfaces.
With kind regards,
William
Updated by Chris Buechler almost 9 years ago
- Category set to Traffic Shaper (ALTQ)
Updated by Luiz Souza almost 9 years ago
- Target version changed from 2.3 to 2.3.1
Updated by Chris Buechler over 8 years ago
- Target version changed from 2.3.1 to 2.3.2
Updated by Chris Buechler over 8 years ago
- Target version changed from 2.3.2 to 2.4.0
Updated by Daniel Greenwald almost 8 years ago
Any news on this? Issue still exists in 2.3.2. No Traffic shaper on bridge0 even with:
net.link.bridge.pfil_member=0
net.link.bridge.pfil_bridge=1
Updated by Luiz Souza over 7 years ago
- Target version changed from 2.4.0 to 2.4.1
Updated by Jim Pingle about 7 years ago
- Target version changed from 2.4.1 to 2.4.2
Updated by Jim Pingle about 7 years ago
- Target version changed from 2.4.2 to 2.4.3
Updated by Luiz Souza almost 7 years ago
- Target version changed from 2.4.3 to 2.4.4
Updated by Jim Pingle almost 6 years ago
- Target version changed from 48 to 2.5.0
Updated by Anonymous almost 4 years ago
- Target version changed from 2.5.0 to CE-Next