Bug NAT whith multi WAN

[eginfo]

I just identified a bug on this version.
I have a configuration that works on version 16.7.2. My configuration has 3 WAN and NAT routing on the WAN group.
I bought a new router and installed the latest version.
I find myself with the following problem:
When the incoming connection is set to the default WAN, NAT routing works. But when the incoming connection is established on a different WAN, the connection does not work.
For me, it seems that the return of the connection goes through the gateway by default and not by the WAN concerned.
What to do ?
Thank you.

[franco]

Hi there,

16.7.2 and 18.1.8 (possibly?) are not enough data points to go through thousands of changes. Can you be more specific?


Thanks,
Franco

[eginfo]

I have buy à new router and i cave importe the configuration.
It's Ok?

[eginfo]

Hello, I need a fast help and I am ready to take the paying support(medium). How? I ask the question here all the same. I have just redone the configuration in the hand on the version 18 up to date, but I always have the same problem. I do not manage to manage rules NAT on a multi-WAN.

[eginfo]

Hi,
Version :     OPNsense 18.1.9-amd64

My NAT configuration for this rule :
Interface  : GroupeWAN
TCP/IP : IPV4
Protocole : TCP/UDP
Source : any
Range ports : 3061
IP dest  : 192.168.0.250
Port : 3061

I have make a group for my 3 Wan interface : GroupWAN.
Wan 1 : tier1 ==> fiber
Wan 2 : tier 2 ==> Adsl
Wan3 : tier  2  ==> Adsl
Wan 4 : tier 3 ==> Secours

When the connections come from Wan 2 and 3, the NAT rules do not work.
 Sticky connections    : Use sticky connections : OK
Source traking : 90 (for test)

I have about 120 rules that do not work in multiwan. Everything works for WAN1, nothing for others.
I specify that in version 16, this is functional.
What to do ?

[paxonsk]

Hi,

I had similar issue wit multiWAN with two uplinks.
I have configured all corretly with policy based routing over GW group.
If I had disabled Shared forwarding, than multiWAN works(if one uplink down, takeover to second and vice versa), BUT inbound port forward  _not_ works, only if I add default route to system table, but works only for this one uplink which I set in default route.
If I enable Shared forwarding, than multiWAN _not_ works, same as port forward.  This is on version 18.1.x
I take days (2weeks) of testing where I am made something wrong, troubleshooting on opnsense/freebsd level(hacking pf rules, router etc.) and today I test update to development 18.7 version and ALL works perfectly, with or without Shared forwarding, mutliWAN with inboud portforward works over both WAN links.

I read in 18.7 milestones this:
o improved default route handling
o improved default gateway switching

This is related probably to this, or  can you send link to github, where this problem fixed between 18.1 and 18.7 ?
Thank you and again THANK you for perfect project and all work around


@eginfo: try update opnsense

[namezero111111]

Your sticky connections + shared forwarding likely cause the issue:

https://github.com/opnsense/core/issues/2376

Try disabling shared forwarding, then it should work if you don't need shaping also.

If you need shared forwarding for shaping, your only workaround currently is to leave sticky connections alone and
manually make them "sticky" by subnet/IP range into multiple failover groups instead of gateways on the same tier...

[paxonsk]

Hi,

thank you for reply

seems to be familiar, but I think not, because I was try all combinations of Sticky connections,Shared fowarding, Default gw switching and so on, but only update to 18.7dev solve whole issue.