Cannot NAT trough OPT1 interface on multiwan
-
This works for me on IPv4 now with a kernel Ermal built with the fix that'll be in the next round of snapshots. Hopefully next snapshot run will be good (first one from the 30th should have it).
-
Thanks Ermal - Everything seems to be working great now :)
-
IPv4 is fixed here, still an issue with IPv6 and TCP but all the common cases confirmed working with today's snapshot.
-
IP4 is working for me now also. Thank you!
-
@cmb:
IPv4 is fixed here, still an issue with IPv6 and TCP but all the common cases confirmed working with today's snapshot.
I can confirm the issue with IPv6, but ICMP does not seem to work in my case. The rule below used to work on my 2.1 install. I have migrated my old config to a 2.2 test machine.
-
I can confirm the issue with IPv6, but ICMP does not seem to work in my case. The rule below used to work on my 2.1 install. I have migrated my old config to a 2.2 test machine.
That's route-to, not reply-to. I'll check that, I'm not aware of any issues there, but that type of scenario isn't as widely used with v6 as with v4.
-
Ah, sorry, I have set this up a long time ago and forgot to mention that there actually is NAT involved. The setup is a workaround to be able to use 2 IPv6 gateways described here:
https://forum.pfsense.org/index.php?topic=71293.msg402861#msg402861
But it was working OK on 2.1. ;) Anyway, thanks for looking into this and if someone has a better idea, feel free to revive that old thread. -
Just another testimonial over here. WAN2 working fine now. I'm not using IPv6 as of yet but will deploy to track development PfSense 2.2 Beta. I'm currently running the snapshot dated Nov 1 64bit.
-
IPv6 should be fixed on new snapshots as well.
-
Works fine now, even with my strange IPv6 NAT config mentioned earlier. Thanks!
-
Also works for me. Thank you