6rd support added
-
Calculate properly your v4 subnet since 0 is 0.
IIRC 0 should be the same as 32 but TBC.
-
Just checking in to state that 6rd is not working in:
2.1.3-RELEASE (i386)
built on Thu May 01 15:52:17 EDT 2014
FreeBSD 8.3-RELEASE-p16 -
It is scheduled to be fixed in v2.2, but not yet. It still does not work in:
2.2-ALPHA (amd64)
built on Tue May 6 04:20:00 CDT 2014
FreeBSD 10.0-STABLE #23 -
Can anyone give me a VM/machine with such connectivity so i can see/fix what the issue is there?
Also give me the expected cofnig there.
-
Hi Ermal,
I'm the guy that opened this ticket:
https://redmine.pfsense.org/issues/2882
I'd be thrilled to set you up a vm so you can sort this out. Message me with what you need (pfSense 2.1.3, 2.2, something else) and we can hash out a time for you to get in and take a look.
-Will
-
Me too. You can access a live system where we accept downtime. Play around and fiddle. If you make it work, you will know immediately.
The Wan config is already in there.
-
Hi guys,
Still waiting for someone to let me know when they want to connect to my 2.2. vm and finally sort this out.
-Will
-
Same here. Always ready!
-
Trying to setup 6rd on AT&T DSL here on 2.1.3-RELEASE (i386)
If I understand this thread … it won't work till something is fixed?
-
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.