NAT not working in Multi-WAN environment
-
Have you configured a gateway on the interfaces/wan edit page? Are you using static or dhcp on wan? If you check /tmp/rules.debug the pass rule should contain 'reply-to' i suppose that is not the case?
-
https://redmine.pfsense.org/issues/6986
-
Have you configured a gateway on the interfaces/wan edit page? Are you using static or dhcp on wan? If you check /tmp/rules.debug the pass rule should contain 'reply-to' i suppose that is not the case?
All 5 WAN's are DHCP.
Yes, I configured the gateways under gateway groups, as on 2.3.3, on 2.4.0 they are still there. -
-
Is there are a workaround or can I do something to fix it?
Or do I just need to wait… -
Nothing can be done to workaround the problem. You'll have to wait for a fix from our side.
-
Oh uh…
Is this my problem too?
https://forum.pfsense.org/index.php?topic=123370.0 -
Most likely.
-
I'm waiting for this fix to…so i will test this problem.
-
One more thing…
I really dont know it its connected but still...See attached image.
I start to download some file hosted behind pfsense with 2 wans (download is happening only on DHCP).
It starts sloppy and interrupting as hell, slow dl speeds lots of retransmissions in packet capture.
But when I hit disconnect on pppoe, it starts to fly as expected...Can this 2 things somehow be connected?
-
Forgot to mention that pppoe has ipv6 and client that downloads has ipv6 too. Webserver has also ipv6.
Maybe this is client problem and tries to download with ipv4 and ipv6 together? -
Forgot to mention that pppoe has ipv6 and client that downloads has ipv6 too. Webserver has also ipv6.
Maybe this is client problem and tries to download with ipv4 and ipv6 together?This is confirmed.
When I disable pppoe ipv4 gateway transfers are OK.
This also happens on 2.3.3So 2 IPv4 gateways are causing major problems, at least for me.
-
Seems to be resolved now: https://redmine.pfsense.org/issues/6986
Don't know if the latest snapshots already have the fix, though. -
The latest snapshots have the fix (for almost a day now)
-
works great now :-)
-
Just upgraded from 2.3.3 to 2.4.0, bug is fixed, Problem solved! :D
