IPv6 tunnel interface incorrectly configured?

bmah

Was your IPv6 route under System > Routing marked as default there?

Yes it was (is). Just to make sure I've got the latest and greatest, I did another update, and am now running this:

2.1-BETA1 (i386) built on Sat Feb 16 22:33:24 EST 2013

Still no default IPv6 route until I SSH in to the pfSense box and add it manually. My IPv4 default route is fine, but that comes via DHCP from my ISP.

UPDATE: Just for kicks I went to System -> Routing and re-saved the entry for my IPv6 gateway, without making any changes. After a reboot (one out of one tries) I got my IPv6 default route back. So I've got a fully-working IPv6 once again, but I don't know exactly why. :-)

Thanks!

Bruce.

Roots0

I'm having the same problem on:
2.1-BETA1 (i386)
built on Sat Feb 23 05:06:42 EST 2013
FreeBSD 8.3-RELEASE-p6

I'm using a /128 prefix from HE.NET

Re configuring the route solved the problem.

Cino

I've noticed the same issue on box today after a firmware/gitsync update this weekend. Default route for IPv6 disappeared. I went to System-Routing and re-saved the default route for my HE tunnel and that resolved the issue.. I'm using a HE tunnel setup as /64.

I haven't rebooted but hopefully it will stick instead of me re-saving the route/gateway config… Last time something like this happen, was when the IPv6 code in pfsense was first implement.

Roots0

I can't re save my Gateway when i go to re-save the un edited page I get the following error:

The gateway address 2001:xxxx:yyyy:zzzz::1 does not lie within the chosen interface's subnet '2001:xxxx:yyyy:zzzz::2/128'.

Also I just reset my cable modem to fix some packet loss due to an ISP problem, and it appears to have lost the IPV6 route again.

jimp

on the assigned interface page, use /126, not /128, that should let it past the gateway error.
Leave it /128 on the GIF config page though.

tebeve

I know this is a week old or so… but I was having this issue as well.

2.1-BETA1 (i386)
built on Thu Feb 21 06:47:29 EST 2013
FreeBSD 8.3-RELEASE-p6

Re-saving the default route config page got my IPv6 back as well.

I'll update my snap and see if anything changes, but I'm assuming since no one has posted in a few days it's good now...

jcyr

Not my experience!

Having followed the instructions at http://doc.pfsense.org/index.php/Using_IPv6_on_2.1_with_a_Tunnel_Broker verbatim, I can attest that either these instruction are incorrect or incomplete or that the latest build does not provide IPV6 connectivity.

BTW. The above documentation makes no mention of setting:

Router Advertisements: Managed

jimp

The page does mention that setting in text and in a screenshot (though that screenshot is from an older version of the page before RA was split off to its own tab).

If you missed that, you likely missed something else. I've followed that nearly to the letter several times and it's always worked for me.

jcyr

Ok, redid the whole thing from scratch… still not working

Perhaps you can explain the following? When I do an ipconfig on my Win 7 64 box, I see the following for the enabled IPV6 interface:

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : dillobits.lan
Link-local IPv6 Address . . . . . : fe80::810e:f844:426a:d714%14
IPv4 Address. . . . . . . . . . . : 192.168.1.32
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Default Gateway . . . . . . . . . : 2001:470:xxxx:xxxx::3
2001:470:xxxx:xxxx:2::1
192.168.0.1

Why am I getting 2001:470:xxxx:xxxx::3 as a gateway address? That address is not used anywhere??? I would have thought that 2001:470:xxxx:xxxx:2::1 would have been the appropriate gateway!

eri--

Can you describe your setup and paste radvd.conf and dhcpd6 config files?