6rd support added
-
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.92Prefixlen 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> -
You probably need latest snapshot and are missing the default v4 gateway.
-
I'll try again with the latest snapshot, although I do have the default v4 gateway set.
-
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
-
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
-
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
-
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_6RDI 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 autoconfAny other logs I can look at?
2.1-RC1 (i386)
built on Tue Aug 27 16:56:22 EDT 2013
FreeBSD 8.3-RELEASE-p10Kind regards,
Maurice
-
You guys are running 6rd over pppoe?
-
I'm not. I do have a gif tunnel active though (tunnelbroker.net), which seems to be the case for most of the others as well.
-
Can you paste here ifconfig and netstat -rn output?
-
Of course.
[2.1-RC0][root@ginnungagap.nulani.net]/root(3): ifconfig rl0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 options=3808 <vlan_mtu,wol_ucast,wol_mcast,wol_magic>ether 00:e0:4c:f0:07:26 inet6 fe80::2e0:4cff:fef0:726%rl0 prefixlen 64 scopeid 0x1 inet 81.167.91.94 netmask 0xffffff00 broadcast 255.255.255.255 nd6 options=1 <performnud>media: Ethernet autoselect (100baseTX <full-duplex>) status: active rl1: flags=8802 <broadcast,simplex,multicast>metric 0 mtu 1500 options=8 <vlan_mtu>ether 00:00:e8:7f:74:28 media: Ethernet autoselect status: no carrier nfe0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 options=8200b <rxcsum,txcsum,vlan_mtu,wol_magic,linkstate>ether 00:e0:81:5c:ea:4c inet 10.26.16.1 netmask 0xfffffe00 broadcast 10.26.17.255 inet6 fe80::2e0:81ff:fe5c:ea4c%nfe0 prefixlen 64 scopeid 0x3 inet6 2001:470:6a0c:2::1 prefixlen 64 nd6 options=1 <performnud>media: Ethernet autoselect (100baseTX <full-duplex,flowcontrol,rxpause,txpause>) status: active bge0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500 options=8009b <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,linkstate>ether 00:e0:81:5c:ea:4b inet 10.26.12.1 netmask 0xfffffe00 broadcast 10.26.13.255 inet6 fe80::2e0:81ff:fe5c:ea4b%bge0 prefixlen 64 scopeid 0x4 inet6 2001:470:6a0c:1::1 prefixlen 64 nd6 options=1 <performnud>media: Ethernet autoselect (1000baseT <full-duplex,flowcontrol,master,rxpause,txpause>) status: active plip0: flags=8810 <pointopoint,simplex,multicast>metric 0 mtu 1500 enc0: flags=0<> metric 0 mtu 1536 pflog0: flags=100 <promisc>metric 0 mtu 33144 lo0: flags=8049 <up,loopback,running,multicast>metric 0 mtu 16384 options=3 <rxcsum,txcsum>inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 nd6 options=3 <performnud,accept_rtadv>pfsync0: flags=0<> metric 0 mtu 1460 syncpeer: 224.0.0.240 maxupd: 128 syncok: 1 ovpns1: flags=8051 <up,pointopoint,running,multicast>metric 0 mtu 1500 options=80000 <linkstate>inet6 fe80::2e0:4cff:fef0:726%ovpns1 prefixlen 64 scopeid 0xb inet 10.26.18.1 --> 10.26.18.2 netmask 0xffffffff nd6 options=3 <performnud,accept_rtadv>Opened by PID 77418 pptpd0: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500 pptpd1: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500 pptpd2: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500 pptpd3: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500 pptpd4: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500 pptpd5: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500 pptpd6: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500 pptpd7: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500 pptpd8: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500 pptpd9: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500 pptpd10: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500 pptpd11: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500 pptpd12: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500 pptpd13: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500 pptpd14: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500 pptpd15: flags=8890 <pointopoint,noarp,simplex,multicast>metric 0 mtu 1500 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 gif0: flags=9051 <up,pointopoint,running,link0,multicast>metric 0 mtu 1280 tunnel inet 81.167.91.94 --> 216.66.80.26 inet6 fe80::2e0:4cff:fef0:726%gif0 prefixlen 64 scopeid 0xa inet6 2001:470:1f08:489::2 prefixlen 64 nd6 options=3 <performnud,accept_rtadv>options=1 <accept_rev_ethip_ver></accept_rev_ethip_ver></performnud,accept_rtadv></up,pointopoint,running,link0,multicast></performnud,accept_rtadv></up,link2></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></pointopoint,noarp,simplex,multicast></performnud,accept_rtadv></linkstate></up,pointopoint,running,multicast></performnud,accept_rtadv></rxcsum,txcsum></up,loopback,running,multicast></promisc></pointopoint,simplex,multicast></full-duplex,flowcontrol,master,rxpause,txpause></performnud></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,vlan_hwcsum,linkstate></up,broadcast,running,simplex,multicast></full-duplex,flowcontrol,rxpause,txpause></performnud></rxcsum,txcsum,vlan_mtu,wol_magic,linkstate></up,broadcast,running,simplex,multicast></vlan_mtu></broadcast,simplex,multicast></full-duplex></performnud></vlan_mtu,wol_ucast,wol_mcast,wol_magic></up,broadcast,running,simplex,multicast>[2.1-RC0][root@ginnungagap.nulani.net]/root(4): netstat -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 81.167.91.1 UGS 0 21685 rl0 10.26.12.0/23 link#4 U 0 45161905 bge0 10.26.12.1 link#4 UHS 0 0 lo0 10.26.16.0/23 link#3 U 0 62129927 nfe0 10.26.16.1 link#3 UHS 0 0 lo0 10.26.18.0/23 10.26.18.2 UGS 0 0 ovpns1 10.26.18.1 link#11 UHS 0 0 lo0 10.26.18.2 link#11 UH 0 0 ovpns1 81.167.36.11 00:e0:4c:f0:07:26 UHS 0 0 rl0 81.167.91.0/24 link#1 U 0 126 rl0 81.167.91.94 link#1 UHS 0 0 lo0 109.247.114.4 00:e0:4c:f0:07:26 UHS 0 7 rl0 127.0.0.1 link#8 UH 0 14991 lo0 213.167.115.92 81.167.91.1 UGHS 0 0 rl0 216.66.80.26 81.167.91.1 UGHS 3 1628 rl0 Internet6: Destination Gateway Flags Netif Expire default 2001:470:1f08:489::1 UGS gif0 ::1 ::1 UH lo0 2001:470:1f08:489::/64 link#10 U gif0 2001:470:1f08:489::2 link#10 UHS lo0 2001:470:6a0c:1::/64 link#4 U bge0 2001:470:6a0c:1::1 link#4 UHS lo0 2001:470:6a0c:2::/64 link#3 U nfe0 2001:470:6a0c:2::1 link#3 UHS lo0 2a01:79c::/30 link#28 U wan_stf 2a01:79d:469d:6d78:: link#28 UHS lo0 fe80::%rl0/64 link#1 U rl0 fe80::2e0:4cff:fef0:726%rl0 link#1 UHS lo0 fe80::%nfe0/64 link#3 U nfe0 fe80::2e0:81ff:fe5c:ea4c%nfe0 link#3 UHS lo0 fe80::%bge0/64 link#4 U bge0 fe80::2e0:81ff:fe5c:ea4b%bge0 link#4 UHS lo0 fe80::%lo0/64 link#8 U lo0 fe80::1%lo0 link#8 UHS lo0 fe80::%gif0/64 link#10 U gif0 fe80::2e0:4cff:fef0:726%gif0 link#10 UHS lo0 fe80::2e0:4cff:fef0:726%ovpns1 link#11 UHS lo0 ff01::%rl0/32 fe80::2e0:4cff:fef0:726%rl0 U rl0 ff01::%nfe0/32 fe80::2e0:81ff:fe5c:ea4c%nfe0 U nfe0 ff01::%bge0/32 fe80::2e0:81ff:fe5c:ea4b%bge0 U bge0 ff01::%lo0/32 ::1 U lo0 ff01::%gif0/32 fe80::2e0:4cff:fef0:726%gif0 U gif0 ff01::%ovpns1/32 fe80::2e0:4cff:fef0:726%ovpns1 U ovpns1 ff02::%rl0/32 fe80::2e0:4cff:fef0:726%rl0 U rl0 ff02::%nfe0/32 fe80::2e0:81ff:fe5c:ea4c%nfe0 U nfe0 ff02::%bge0/32 fe80::2e0:81ff:fe5c:ea4b%bge0 U bge0 ff02::%lo0/32 ::1 U lo0 ff02::%gif0/32 fe80::2e0:4cff:fef0:726%gif0 U gif0 ff02::%ovpns1/32 fe80::2e0:4cff:fef0:726%ovpns1 U ovpns1 -
Still not working in -RELEASE.
-
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" -
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::4In the WAN settings page I have entered:
6RD prefix: 2a01:79c::/30
6RD Border relay: 213.167.115.92
6RD IPv4 Prefix length: 0Running 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.92Pinging 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>
-
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.
