6rd support added
-
Hi Wolphfang,
I would say most likely not.
The worst part is 6RD has been broken for over a year and the post above is the first real nibble we have gotten about actually fixing it, but that opportunity seems to be fading fast.
-Will
-
Ok people give it a shot with tomorrows snapshots.
-
Hi ermal,
Well I gave the latest snapshot (pfSense-LiveCD-2.2-DEVELOPMENT-amd64-20140530-1557) a try. I did a fresh install but when it's booting I get to:
Starting syslog…done.
Starting CRON...done.And there it hangs, right before the "Welcome to pfSense....." console menu.
-Will
-
The new snapshots have been fixed for 2.2.
So just give a shot and let me know if it works. -
Hi ermal,
I just tried the snapshot from 09-Jun-2014 19:51.
Still doesn't work.
As always, please let me know if you want to remote into my system and see what's going on.
-Will
-
Having the same issue here on snapshot Thu Jun 12 15:49:45 CDT 2014. I'm on Charter and trying to use their 6rd implementation.
I'd really like to see this fixed. It's past time for me to get some experience with IPv6.
-
Hi puithove,
Best I can tell you is to be patient, I've been waiting for a year and a half.
I just hope it gets fixed so there's enough time using it that fixing it was even worthwhile.
That said, based on what I've read in the 2.2 forums here: https://forum.pfsense.org/index.php?topic=78078.msg425758#msg425758
Most of the "problems" lately are non-issues or temporary issues with snapshots. There are a couple more features we're waiting to integrate/test and then it is clear to progress to Beta, so … it's difficult to say. For some, it might be OK now, for most, perhaps not quite yet. If it works, it'll keep working, but if you obsessively track snapshots, maybe not.
6RD might be fixed, might not. Bums me out....
-Will
-
FYI, added a bounty for this issue:
https://forum.pfsense.org/index.php?topic=78216.0I have the same ISP as 2 users in this thread, hopefully someone picks this up now ;)
-
Still doesn't work in snapshot 2.2-BETA (amd64) built on Sun Oct 12 11:15:43 CDT 2014 FreeBSD 10.1-RC2.
-
You can try the latest snapshots.
https://redmine.pfsense.org/issues/2882 Just check that you have a default gw.
The default gw will be fixed ASAP. -
Confirmed this works now. Probably be the first snapshot on the 20th that includes all the changes. Being on a snapshot from the 19th plus a gitsync to master will also fix.
-
@cmb:
Confirmed this works now. Probably be the first snapshot on the 20th that includes all the changes. Being on a snapshot from the 19th plus a gitsync to master will also fix.
Running Nov 19 08:31:57 CST 2014 build and it did not work until I gitsynced it and now it works. Thanks :)
Edit: Gateway still shows as offline though, but I can ping outside addresses.
Your readiness score: 10/10 @ http://test-ipv6.com
-
Put a monitor IP in for the gateway that'll actually reply (such as Google's public DNS 2001:4860:4860::8888), the 6rd gateway generally won't reply, which is why it shows offline.
-
6rd working for me now. using centurylink/qwest. What was the problem?
-
Is 6rd broken again? I noticed on latest snapshot 6rd is not working anymore.
-
I think around late November to make it work I had to gitsync to master. I suppose the latest snapshots are built from master. Am I correct or do I still need to gitsync?
I really enjoyed having working 6rd and IPV6 connectivity and I would love to have it working again.On interface status, WAN gets:
IPv6 address 2602:47:3004:c800:: Subnet mask IPv6 24 Gateway IPv6 2602:cdab:240::LAN set to track wan gets:
IPv6 address 2602:47:3004:c800::1 Subnet mask IPv6 64IPV6 Routing table:
::1 link#11 UH 0 16384 lo0 2602::/24 link#13 U 0 1280 wan_stf 2602:47:3004:c800:: link#13 UHS 0 16384 lo0 2602:47:3004:c800::/64 link#6 U 4713 1500 sk1 2602:47:3004:c800::1 link#6 UHS 0 16384 lo0 fe80::%sk0/64 link#5 U 0 1500 sk0 fe80::290:7fff:fe3c:52bd%sk0 link#5 UHS 0 16384 lo0 fe80::%sk1/64 link#6 U 787 1500 sk1 fe80::1:1%sk1 link#6 UHS 0 16384 lo0 fe80::%sk3/64 link#8 U 0 1500 sk3 fe80::290:7fff:fe3c:52ba%sk3 link#8 UHS 0 16384 lo0 fe80::%lo0/64 link#11 U 0 16384 lo0 fe80::1%lo0 link#11 UHS 0 16384 lo0 fe80::%ovpns1/64 link#14 U 0 1500 ovpns1 fe80::290:7fff:fe3c:52c1%ovpns1 link#14 UHS 0 16384 lo0 ff01::%sk0/32 fe80::290:7fff:fe3c:52bd%sk0 U 0 1500 sk0 ff01::%sk1/32 fe80::1:1%sk1 U 0 1500 sk1 ff01::%sk3/32 fe80::290:7fff:fe3c:52ba%sk3 U 0 1500 sk3 ff01::%lo0/32 ::1 U 0 16384 lo0 ff01::%ovpns1/32 fe80::290:7fff:fe3c:52c1%ovpns1 U 0 1500 ovpns1 ff02::%sk0/32 fe80::290:7fff:fe3c:52bd%sk0 U 0 1500 sk0 ff02::%sk1/32 fe80::1:1%sk1 U 3 1500 sk1 ff02::%sk3/32 fe80::290:7fff:fe3c:52ba%sk3 U 0 1500 sk3 ff02::%lo0/32 ::1 U 0 16384 lo0 ff02::%ovpns1/32 fe80::290:7fff:fe3c:52c1%ovpns1 U 0 1500 ovpns1Is it missing a default gateway?
Please be patient with me as I am learning IPV6 and I may be doing something wrong. With the exception of the routing tabe which I have no way to compare to the previous working setup, interfaces seem to get the same addresses as the previous working setup as my dynamic IPV4 has not changed since (It is dynamic but the same ipv4 address tends to stick for months at the time). Your IPV6 on 6rd is calculated based to your IPV4 right?
Also how do you check if wan_stf is passing traffic?
-
It still works, no need to gitsync. Make sure your 6rd gateway is marked as default for v6 under System>Routing.
-
WAN_6RD gateway already marked as default in system->routing, however I do not see any gateway marked as default in the routing table. Still I have still no traffic routed after a fresh reinstall. I used centurylink/quest 6RD with 2602::/24 prefix, 205.171.2.64 border relay and 0 prefix length as per centurylink docs (this worked previously). LAN is set to track wan. Clients on the network get IPV6 addresses in the 2602:47:3004:c800:: range, can ping6 LAN ipv6 address, can't ping anything past pfsense an address. WAN_6RD shows offline (setup to ping google ipv6 dns). From pfsense shell can ping a plan client, cannot ping google dns -> no route to host. Do you see anything abnormal in my routing table? I did not add or remove any routes. Have 2 pfsense boxes with carp both with same problem.
-
As additional info, I do not see a ::0 route or a default gateway in the routing table.
Looking at the logs I found this:
php-fpm[71649]: /system_gateways.php: The command '/sbin/route change -inet6 default '2602:cdab:240::'' returned exit code '1', the output was 'route: writing to routing socket: No such process route: writing to routing socket: Network is unreachable change net default: gateway 2602:cdab:240:: fib 0: Network is unreachable'So my box is unable to add a default route for IPV6.
I double checked my 6RD configuration and it appears correct for Centurylink/quest which is my isp
Any suggestion or any further test I can do?
-
Can you provide an ifconfig output?
Also your config.xml for this WAN configuration?