6rd support added

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.

survive

Hi ermal,

I just tried with the July 12th snapshot & still no luck.

I took a look and the output of the 2 commands you asked me to run in this ticket:

http://redmine.pfsense.org/issues/2882

seem to be the same.

As always, if there is anything I can provide to help resolve this ticket please just let me know!

-Will

eri--

From relooking at the redmine posts you put your v6 default gateway is using the wrong interface.
It should use the wan_stf rather than the underlying interface.

Can you resave your default gateway for v6?

Also show config.xml of gateways and your wan interface together with ifconfig, netstat -rn

survive

Hi ermal,

I have updated the ticket here:

http://redmine.pfsense.org/issues/2882

with the requested information.

I took a look at "System: Gateways: Edit gateway" and my ipv6 gateway is listed as "dynamic" I tried to re-save it by hitting the save button but there was no change. Is this the right place to check? Charter doesn't specify a default gateway, so I don't know what I should set it to if not dynamic.

-Will

MauriceS

On centurylink with a PPoE i get the following 6rd errors:

system.log:Aug 26 21:19:16 pfsense check_reload_status: updating dyndns WAN_6RD
system.log:Aug 27 20:25:24 pfsense php: rc.bootup: The interface IPv4 '' address on interface 'pppoe0' is not public, not configuring 6RD tunnel
system.log:Aug 27 20:25:56 pfsense check_reload_status: updating dyndns WAN_6RD
system.log:Aug 27 23:10:23 pfsense check_reload_status: updating dyndns WAN_6RD

I don't seem to get an IP address except for these:

inet6 fe80::260:xxxx:xxxx:10a4%fxp0 prefixlen 64 scopeid 0x1
inet6 fd00::260:xxxx:xxxx:10a4 prefixlen 64 autoconf

Any other logs I can look at?

2.1-RC1 (i386)
built on Tue Aug 27 16:56:22 EDT 2013
FreeBSD 8.3-RELEASE-p10

Kind regards,

Maurice

eri--

You guys are running 6rd over pppoe?