6rd support added

Nulani

Still not working in -RELEASE.

olavgg

I'm on the same network(Altibox) as Nulani and running 2.1-RELEASE. With the same problems as him. Can ping internally, but there is no external communication.

However, if I try to ping ipv6.altibox.no or ipv6.google.com, it does find the external ip address.
If I try to do this from a local Linux system with ipv6, I just get following error message: "connect: Network is unreachable"

Fegu

Although this is an older topic, I am replying since I am working on the exact same issue as users Nolani and olavgg who posted last on this topic.

We want to connect to a network with these 6RD settings on WAN:

IPv4 BR: 213.167.115.92
IPv4 Prefix: 0
IPv6 Prefix: 2a01:79c::
IPv6 Prefix Length: 30
IPv6 DNS: 2a01:798:0:8012::4

In the WAN settings page I have entered:

6RD prefix: 2a01:79c::/30
6RD Border relay: 213.167.115.92
6RD IPv4 Prefix length: 0

Running ifconfig in the shell we can see:

wan_stf: flags=4001 <up,link2>metric 0 mtu 1280
inet6 2a01:79d:3e85:a408:: prefixlen 30
nd6 options=3 <performnud,accept_rtadv>v4net 0.0.0.0/0
v4br 213.167.115.92

Pinging pfSense server works ok. This is the only thing that works ok. All external addresses fail and test-ipv6.com gives 0/10.

On the LAN side I have tried DHCP6 (with several of the RA-options) and Track Interface. Does anything about this setup seem wrong?

Could this problem be related to bug report #2882 as shown here: https://redmine.pfsense.org/issues/2882</performnud,accept_rtadv></up,link2>

eri--

Calculate properly your v4 subnet since 0 is 0.

IIRC 0 should be the same as 32 but TBC.

rwstrehl

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

Fegu

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

eri--

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.

survive

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

Fegu

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.

survive

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

Fegu

Same here. Always ready!

WolphFang

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?

survive

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

eri--

Ok people give it a shot with tomorrows snapshots.

survive

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

eri--

The new snapshots have been fixed for 2.2.
So just give a shot and let me know if it works.

survive

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

puithove

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.

survive

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

Burg3rMak3r

FYI, added a bounty for this issue:
https://forum.pfsense.org/index.php?topic=78216.0

I have the same ISP as 2 users in this thread, hopefully someone picks this up now ;)