6rd support added

pyrodex

How do you have DNS items configured in pfSense DHCP server page?

They are blank which would mean they inherit they are setup as the IPv4 LAN address. But in my case is the PFSense DHCPv4 actually issuing DHCP to my IPv6 clients or is Charter's 6RD platform?

MaxPF

I haven't tried it myself, but in Canada, Rogers offers this:

Setting Confirmation Required
Provider Prefix 2607:F090
Provider Prefix Sites 32
Mask Bits 0
Relay Address 66.185.95.192

kradalby

I guess i am a little too nooby to get all this,

My isp information is:
Altibox 6RD border relay: 213.167.115.92
15 bits prefix.

Can someone explain how this thing works, or is there an article i cant find on the wiki?

-Kristoffer

mgysi

Please note that Swisscom will change the IP of its 6rd Border Relays to 193.5.29.1 at April 9th, 08:00. This change will be reflected in the DNS name 6rd.swisscom.com at the same time (plus some propagation time through DNS).

Nulani

Altibox/Lyse, Norway
6RD IPv6 Prefix: 2a01:79c::/30
6RD Border Relay: 213.167.115.92
6RD IPv4 Prefix length: 0

Results in a /62.

They're using dhcp option 212 to distribute the configuration to the devices that support it.

I haven't managed to get it to work myself yet. It adds the correct address to the interface - the one I've been told I'm supposed to get - but I can't actually reach anything from it. Not entirely sure if the problem is on my end or with my ISP. Running Pfsense 2.1-RC0 (amd64) built on Tue Jun 4 20:54:59 EDT 2013.

survive

Hi Nulani,

As far as I know 6RD has been broken in 2.1 since mid-January.

You can find some additional details in this post:

http://forum.pfsense.org/index.php/topic,62629.0.html

-Will

jimp

Some commits were made this week that others reported fixed the issue. Are you still seeing a problem on a current snapshot?

Nulani

@jimp:

Some commits were made this week that others reported fixed the issue. Are you still seeing a problem on a current snapshot?

I'll update this weekend and see. It isn't working in June 4th.

survive

Hi jimp,

I just gave the June 6th RC-0 build a try and if anything it was working even worse. Ordinarily I can reach the http://test-ipv6.com/ website and confirm that 6RD isn't working but with the RC-0 build I couldn't even do that.

This was with a straight update from Jan 18th to June 6th using the instructions in the sticky.

Rolling back the vm to my Jan 18th build got me right back up & running.

I've been keeping track of the ticket I opened for this: https://redmine.pfsense.org/issues/2882 so I was unaware of any change that had been made that might have fixed 6RD.

-Will

Nulani

No difference in 2.1-RC0 (amd64) built on Thu Jun 6 21:08:57 EDT 2013.

cmb

Should work with tomorrow's snapshot, my test system is working now.

survive

Hi cmb,

I just updated to the Wed, June 12th snapshot and 6RD is still not working.

Please let me know if there is anything I can do or provide to help fix this.

-Will

cmb

I upgrade all my systems with 6rd to today's snapshot and they all work. Do you have a default v6 route listed under Diag>Routes? Getting a v6 IP assigned to the LAN from the PD? radvd running and assigning IPs on the LAN?

survive

Hi Chris,

I can't answer your question right this moment because I gave rolled back to my Jan 18th snap where it all works perfectly. All I do is run the upgrade and the gateway monitor stays down & I can't do any ipv6. It does feel like the rest of the box is dragging when I run the June 12th snap.

Gimme a few minutes to update again and I should be able to get some answers.

-Will

Nulani

Still no change. Gateways shows as down.

2.1-RC0 (amd64) built on Sat Jun 15 05:06:20 EDT 2013

WetWilly

Well, gateway down could be caused by the gateway not responding on ICMP.

You should instead try to ping6 some ipv6 site on the Internet.

6RD has been working for me since the june 12:th build.

Nulani

Can't ping anything but the interface itself across IPv6, I'm afraid.

Nulani

I believe I have spotted what the problem probably is in my case:

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

Prefixlen should be 62, not 30. At least, a 62 is what I'm assigned from my ISP. Manually correcting it makes no difference, however.


[2.1-RC0][root@ginnungagap.nulani.net]/etc(40): ifconfig wan_stf inet6 2a01:79d:469d:6d78:: prefixlen 62
[2.1-RC0][root@ginnungagap.nulani.net]/etc(41): ping6 2a01:79d:469d:6d78::
PING6(56=40+8+8 bytes) 2a01:79d:469d:6d78:: --> 2a01:79d:469d:6d78::
16 bytes from 2a01:79d:469d:6d78::, icmp_seq=0 hlim=64 time=0.349 ms
16 bytes from 2a01:79d:469d:6d78::, icmp_seq=1 hlim=64 time=0.144 ms
^C
--- 2a01:79d:469d:6d78:: ping6 statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.144/0.246/0.349/0.102 ms

[2.1-RC0][root@ginnungagap.nulani.net]/etc(42): ping6 -S 2a01:79d:469d:6d78:: google.com
PING6(56=40+8+8 bytes) 2a01:79d:469d:6d78:: --> 2a00:1450:400f:801::1007
^C
--- google.com ping6 statistics ---
33 packets transmitted, 0 packets received, 100.0% packet loss

```</performnud,accept_rtadv></up,link2>

eri--

You probably need latest snapshot and are missing the default v4 gateway.

Nulani

I'll try again with the latest snapshot, although I do have the default v4 gateway set.