2.1 with IPv6 Tunnel, HELP?
-
Did you reboot before trying to do anything else? On another note, no idea what got (mis)saved/(mis)configured when you've been trying to add IPv6-related stuff with IPv6 disabled… Leaving this for support, for me reconfiguring the thing from scratch would be faster than messing with box in unknown state.
-
Did you reboot before trying to do anything else? On another note, no idea what got (mis)saved/(mis)configured when you've been trying to add IPv6-related stuff with IPv6 disabled… Leaving this for support, for me reconfiguring the thing from scratch would be faster than messing with box in unknown state.
Great news.
Checking "Allow IPv6" has allowed me to figure out what the problem is.
It's definitely a problem with the GIF GUI interface on 2.1.
If I try to add a GIF interface via the web GUI, I'm met with that error and it's not actually added. (Even after checking "Allow IPv6")
If I manually type the command:
[2.1-RELEASE][admin@xxx.xxx.xxx]/root(1): /sbin/ifconfig gif0 inet6 2001:470:7:bfd::2 2001:470:7:bfd::1 prefixlen /64
… I am able to add the OPT interface, gateway, and everything works.
It seems like something in 2.1 is not prefixing a / to the subnet, like the previous thread I linked to.
Thanks doktornotor, I can proceed and play around with IPv6 while awaiting an official response from support to see if it's something unique to my config, or an actual problem with the 2.1 release.
-
FYI, after typing the correct command into an SSH window, the IPv6 tunnel is up and I can ping ipv6.google.com via the WAN port successfully.
Ping output:
PING6(56=40+8+8 bytes) 2001:470:7:bfd::2 –> 2607:f8b0:4004:801::1011
16 bytes from 2607:f8b0:4004:801::1011, icmp_seq=0 hlim=59 time=10.487 ms
16 bytes from 2607:f8b0:4004:801::1011, icmp_seq=1 hlim=59 time=10.293 ms
16 bytes from 2607:f8b0:4004:801::1011, icmp_seq=2 hlim=59 time=14.126 ms--- ipv6.l.google.com ping6 statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 10.293/11.635/14.126/1.763 msDoesn't look like there is IPv6 support for AON however, so ultimately I might be out of luck. -
OK - I'll bite… AON?
-
OHHHHHHHH - THAT AON!
::)
Why?????
-
For traffic to flow from my LAN clients to the Internet, an additional LAN rule needs to be created for IPv6, as noted in one of doktornotor's links.
However, his link leaves out a few steps that the official how-to doesn't, so I'm going to submit an update to the official how-to and hopefully combine the two.
So, in a nutshell, everything is now working - as long as I manually add the / via an SSH command so I'm going to keep my support ticket open.
Thanks for the help everyone.
 -
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?
