2.1 with IPv6 Tunnel, HELP?
-
OHHHHHHHH - THAT AON!
::)
Why?????
I have my normal WAN connection, but I also keep a nailed-up OpenVPN connection to StrongVPN. I can dynamically route traffic either out via my ISP or via StrongVPN by simply manipulating a LAN firewall rule. For this to work you have to use AON.
EDIT:
Why would I do this? My ISP has issues with SIP, so I route my SIP phone over the StrongVPN connection. It's just a tunnel via OpenVPN to bypass my ISPs SIP issues.
Of course, I can also use it when I'd rather have the StrongVPN IP appear as my source IP rather than my ISPs IP. ;)
-
Uhm… considering this is the only mention of IPv6 anywhere on their site, don't see what's the plan there.
-
Uhm… considering this is the only mention of IPv6 anywhere on their site, don't see what's the plan there.
I don't use them for IPv6, I only route IPv4 over them.
Basically, they are another gateway, just like Tunnelbroker. So I have 3 gateways - my ISP, StrongVPN, and now HE.net (Tunnelbroker).
-
Yes… so what's the IPv6 NAT for?
-
-
Well, you mentioned you need IPv6 NAT on this thread as well…
-
Well, you mentioned you need IPv6 NAT on this thread as well…
I struck-through (is that even proper grammar?) that comment in my previous post.
I thought my clients couldn't communicate out via IPv6 because of my AON rules, but it in fact was a simple LAN rule I needed to create, which was mentioned in the how-to link you provided.
On the LAN tab: IPv6 * LAN net * * * * none
I now see that your how-to and the official how-to are BOTH missing information, so I'm going to take the correct information from your how-to and see if I can integrate it into the official how-to.
-
Ah, OK.
-
Ah, OK.
Seriously, thank you for your help.
Hopefully the GIF Interface issue is just something borked on my box, but if not, your guidance helped to narrow it down.
-
FYI, the pfSense guys issued a fix.
-
A fix for what exactly?
I tried to make heads or talls of this thread a couple of times now – I have been using he tunnel with pfsense for quite some time, all through the development phase, etc.. And don't recall any issues with using the tunnel.
Now native ipv6 sure - but tunnel has been rock solid.. Still using it - so curious what this fix pfsense issued? Looking at the commits I don't see anything ipv6 related?
-
A fix for what exactly?
I tried to make heads or talls of this thread a couple of times now – I have been using he tunnel with pfsense for quite some time, all through the development phase, etc.. And don't recall any issues with using the tunnel.
Now native ipv6 sure - but tunnel has been rock solid.. Still using it - so curious what this fix pfsense issued? Looking at the commits I don't see anything ipv6 related?
They gave me a patch for post #1 in this thread. That resolved my problems.
-
who game you a patch, and where?
