Can anyone think why having a mangle rule that sets up a static route for an interface would perform so poorly? As in, it gets about 3 orders of magnitude loss of bandwidth at its best.
Also, is there any documentation for this beyond the bare minimum?
This kind of problem results from combining such features with “Fasttrack”.
The majority of the traffic uses the fast track (and thus fails to hit the mangle rule) but a small percentage is still falling through, and hits the mangle rule.
SO make sure you disable fasttrack when you want to use such features.
Without details, do not use mangle to do routing works, use route rules instead…
This is very helpful. It solved the issue.
With multiple WANs and wanting some form of policy-based routing seems to require some mangle rule. If this is not the case, I'd like to see some example(s) where that is possible without mangle rules.
What are you trying to accomplish? I have multiple WANs (two different internet services) and use route rules to determine which LANs use which WAN for outbound connections. No mangle involved.
@k6ccc: It depends. If you want some LAN devices use one WAN and other LAN devices use another, routing rules are good choice. If you want e.g. all web browsing (ports 80 and 443) use one WAN and other traffic use another, you need mangle rules.
You missed the point Sob, until the OP states his requirements, making any assessment on what he needs is a crap shoot.
Odds are that he has mangling because he did some research and that what it pointed to, so yes most likely.
But lets not speculate on speculation and just be patient for OP to be more forthcoming.
DIAGRAM
CONFIG
SET OF REQUIREMENTS
you know the usual ways human beings communicate in software and IT.
(PS I am surprized you have not commented on my new and improved wg user article)