Bug #9325
closed
problem with flexible limiter in multiWAN environment
0%
Description
Hi,
I'm observing serious problems with flexible limiters set using floating rules. Let me start from the beginning:
In case the flexible limiter is configured/attached to the LAN-side interface rules, everything works perfectly.
This, however, can't be used in case you have a multiWAN environment and the gateway for the LAN-side rule is a gateway group (assuming your two WANs have different speeds). In this sencario the same flexible limiter would used in case your main WAN works and in case your backupWAN takes over. Assuming your WANs have different speeds, you either have to set your limiter to the values of your slower WAN (awful solution!) or to the values of your faster WAN (which makes the limiter useless when the slower WAN is the only one available).
A logical solution would be set the limiter in a floating rule (type = match, direction = out, IF=WAN, GW=WAN_GW) and a second floating rule for the other WAN. The problem is if you set it up like this the download limiter works fine but the upload limiter does not - it blocks the traffic almost completely.
For example: a 3/5 Mbit limiter gives a 0,2/5Mbit internet access....
I'm on the 2.4.4_2 so basically latest and greatest. I think I tried everything, including all the possible reconfigurations that make sense as well as all those that do not :) Still I can't make this work...
This definitely seems like a bug.
Brg,
Adam
Updated by Adam Lewandowski about 5 years ago
EDIT:
I found a workaround, i.e. I've set up floating rules (direction = in; attached to LAN interfaces; GW = GW1 for one rule and GW2 for the other rule) for those flexible limiters and this works fine.
However, this doesn't change the fact that in case of 'out' floating rules on WAN interfaces, the 'up' limiter does not work - still looks like a bug to me.
Updated by Jim Pingle over 4 years ago
- Category set to Traffic Shaper (ALTQ)
- Status changed from New to Not a Bug
There isn't a way for the LAN-side limiters to know which WAN the traffic will exit, so any further refinement here is not possible.
Updated by Adam Lewandowski over 4 years ago
Agreed. But the problem is that it doesn't work when set up as floating rules on WAN interfaces - "in case of 'out' floating rules on WAN interfaces, the 'up' limiter does not work - still looks like a bug to me."