Quote from: nero355 on <strong>Today</strong> at 08:10:59 PMDo you use MACVLAN for your Docker Network ?
If not : You should! :)
Quote from: Andreas1 on <strong>Today</strong> at 05:55:04 PMNow I have the current version 26.7.8_2 and no migration assistent anymore.IIRC you don't even need it : Just Export and Import the Rules again and you are done ??
Quote from: pfry on <strong>Today</strong> at 04:26:10 PMrc.conf:The second setting via the webGUI solves update issues for some in certain cases, but none of those things changes anything to a Android/Apple/Linux/Windows Client ofcourse ;)
ip6addrctl_enable = "YES"
ip6addrctl_policy = "ipv4_prefer"
OPNsense: "System: Settings: General" -> "Networking" -> "Prefer IPv4 over IPv6"
I also only use IPv4 only, with no IPv6 address assignments or discovery, and "net.inet6.ip6.auto_linklocal = 0", so I can't comment on effect.
Quote from: FlyveHest on <strong>Today</strong> at 07:00:46 PMThis has unearthed a new problem, unfortunately, because the issue is still present, but only on services published through Docker.Do you use MACVLAN for your Docker Network ?
So, this is probably because there is some form of masquerading or other package mangling happening after routing has happened, leading to the traffic still being sent out the wrong interface.
Quote from: nero355 on November 08, 2026, 06:27:49 PMSounds like A-Symmetric Routing issues and the "Default DENY / State violation Rule" is always right in my experience :)
Quote from: nero355It seems like it's time to apply Policy Base Routing on your Server then :)
Quote from: Wrigleys on <strong>Today</strong> at 07:26:32 AMSince 26.7.8 you can paste your API Token at the end of the Download Section.