Dual WAN + Traffic Shaping

[snakeaj]

Hello!

I wan to use Dual WAN (DSL + 4G) and limit bandtwith for each user to 4 Mbit down and 1 Mbit up.

My Problem: in traffic Shaping i can only use an INTERFACE (wan1 or wan2) and not my WAN GROUP.

one more thing i noticed: i can not find "Sticky Connection" which i want to set (Multi WAN howto)

thx
alexander

OPNsense 16.7.11_1-amd64
FreeBSD 10.3-RELEASE-p14
OpenSSL 1.0.2j 26 Sep 2016

[rackg]

Hello Alexander,

I still have the issue. You can check this out https://forum.opnsense.org/index.php?topic=3856.msg13582#msg13582. My issue was same on similar setup.

[HFsi]

It seems that the issue will see another christmas...I´m stuck with the same problem...

[mimugmail]

I haven't tested it yet but I'd create two pipes, each for 1 WAN, 2 queues for each WAN pointing to their pipes and then create rules pointing to the queues in advanced mode with both interfaces (IN+OUT)

[franco]

It seems that the issue will see another christmas...I´m stuck with the same problem...

It is unclear what the "same" issue could be. There is a lot of time between Christmas 2016 and 2017. ;)


Cheers,
Franco

[HFsi]

Hi Franco!
The "same issue" would be that in traffic Shaping I can only use an INTERFACE (wan1 or wan2) and not my WAN GROUP.
So if one WAN goes down the shaping stops working, wright?

And I want to take the opportunity to thank you people for integrating ClamAV as a plugin!

[mimugmail]

It doesnt make sense to use a Wan group as bandwith amd latency differ for most connections. Just create multiple pipes and rules.

[franco]

Hi there,

GW Groups are abstractions of one underlying firewall in FreeBSD: pf

Traffic shaping works using another firewall in FreeBSD better suited for the task: ipfw

Both only share the knowledge of individual interfaces unless LAGG is used. What is the downside of managing both interfaces independently in traffic shaping? They only apply in a physical scope with its own boundaries like Michael said.

If there is trouble with multi-wan shaping not working in general, make sure you have shared forwarding turned on (Firewall: Settings: Advanced).


Cheers,
Franco