SecureNAT Weird Route

[marcosmoraesti]

Hi everyone.
Here is my case i need some help, sorry about my english.

I have already did another SecureNAT in other clients with easy, but in this case its a bit weird, heres the scenario.

My Softether Server, is a Windows Server (192.168.15.248/24), behind a pfSense (192.168.15.1/24), with 2 WANs (192.168.160.1 and 192.168.170.1).
The Softether is behind NAT in port 7777 and i already have a HUB with LocalBridge working, but i need to use SecureNAT for security reasons.

The SecureNAT HUB have this SecureNAT DHCP settings:
- Server IP 172.16.0.1/16
- DHCP 172.16.0.100-172.16.100.100
- Static Route Push: 192.168.15.0/255.255.255.0/172.16.0.1

And now the weirdo happens, when i connect to this HUB, i got the IP 172.16.0.100.
When i do a simples tracert, the first hop is the SecureNAT IP 172.16.0.1 and the second is the pfSense first (default) WAN IP 192.168.160.1
And then i cant go anywhere.


In others cases , i do the same configuration and works like a charm.
I tried to Google and ChatGPT this case and finally came here for help.

Any ideas ?

[solo]

set DisableKernelModeSecureNAT to 1