Can't get PD /56 to work
-
I'm seeing the exact same thing. I've been using a Sophos UTM box as my main firewall, and recently tried to get IPv6 working with my Telus GPON service. My searches lead me to the same Telus thread you read regarding PD, which the Sophos can't do.
I then tried setting up a Linux box that was conveniently connected to the network, and make it do a PD request only. Didn't work. So I put Wireshark on to see what was going on. I could see the request going out, but nothing in response.
Of course the Actiontec router works fine, but I refuse to use it.
So I thought I'd try pfSense, because I heard that it could do PD.
But I'm seeing the same thing in Wireshark - a request going out but nothing coming in.
Anyone have any suggestions?
-
Since you have gpon, is it possible to have your wireshark connected on the wan side while the actiontec boots up? If so, maybe you could see what's happening. What type of actiontec to you have? Not sure if that would work in my case because I can't get directly on the wan side, only through the bridged port 1. I suppose I could create another windows guest, install wireshark on it and connect it to the virtual switch on the wan side, then powercycle the modem and find out if I can see what's happening.
Also, what settings are you using? Did you manually configure ipv6 or did you let the installer do it?
-
I haven't tried wiresharking the Actiontec box but I can - I'll try setting it up tomorrow and seeing exactly what's being sent and received and see if I can compare that to what pfSense is doing.
As for what ipv6 settings, I manually configured pfSense, and specifically set it to PD only (which is what the telus guy said in his thread) but it didn't make any difference. I'll report back tomorrow with what I find.
-
I installed wireshark on the windows 10 guest and moved it to the other side of my test pfsense guest, which is connected to the bridged port on the actiontec. It's not really a supported configuration for ipv6, so it couldn't acquire an ipv6 address. I rebooted pfsense to see what traffic it generated. I saw messages from the pc trying to get an address, but there was no sign of pfsense trying to acquire a prefix. It doesn't seem right, so I'll try again tomorrow.
-
If any of you experts out there can point me in the right direction, I'd really appreciate it. If there are particular settings I should try or log messages that I should post, let me know. I'd really like to get this working.
-
I haven't looked at this in a couple of months, but I believe the issue with Telus' IPv6 implementation is related to https://redmine.pfsense.org/issues/5993.
If you set up the dhcp6 client to only request an IPv6 prefix, set it to ask for a /56, and to send the IPv6 prefix hint then it should work if you run the following command, assuming em0 is your WAN interface.
/usr/local/sbin/dhcp6c -c /var/etc/dhcp6c_wan.conf -p /var/run/dhcp6c_em0.pid em0 -
I haven't looked at this in a couple of months, but I believe the issue with Telus' IPv6 implementation is related to https://redmine.pfsense.org/issues/5993.
If you set up the dhcp6 client to only request an IPv6 prefix, set it to ask for a /56, and to send the IPv6 prefix hint then it should work if you run the following command, assuming em0 is your WAN interface.
/usr/local/sbin/dhcp6c -c /var/etc/dhcp6c_wan.conf -p /var/run/dhcp6c_em0.pid em0I think it's pretty clear that the problem I'm having is related to bug 5993. I tried your suggestion using hn0, which is my wan interface. pfsense did not grab a prefix and dhcp6 did not start. I'd be glad to post log messages or whatever to get to the bottom of this, but my forehead is sore from banging against the wall.
-
I haven't looked at this in a couple of months, but I believe the issue with Telus' IPv6 implementation is related to https://redmine.pfsense.org/issues/5993.
If you set up the dhcp6 client to only request an IPv6 prefix, set it to ask for a /56, and to send the IPv6 prefix hint then it should work if you run the following command, assuming em0 is your WAN interface.
/usr/local/sbin/dhcp6c -c /var/etc/dhcp6c_wan.conf -p /var/run/dhcp6c_em0.pid em0I think it's pretty clear that the problem I'm having is related to bug 5993. I tried your suggestion using hn0, which is my wan interface. pfsense did not grab a prefix and dhcp6 did not start. I'd be glad to post log messages or whatever to get to the bottom of this, but my forehead is sore from banging against the wall.
I rebooted pfsense and the pc and tried again. This time it worked. No idea why it worked this time, but not before. Now, if we can only get a version of pfsense with this built-in!
UPDATE: The Gateways panel on Status / Dashboard shows ~ for the address and Pending for RTT, RTTsd and Loss, and Unknown for Status. Status / Gateways / Gateways shows blank for Monitor, and Pending for RTT, RTTsd, Loss and Status.
-
I just updated to 2.3.2-DEVELOPMENT which included a update to dhcp6 and seems things are working better. my internal clients have valid ipv6 addresses and ipv6 dns works just fine.
However I can't get any ipv6 traffic to leave my lan, but ipv6 connectivity works just fine on the router.
-
I just updated to 2.3.2-DEVELOPMENT which included a update to dhcp6 and seems things are working better. my internal clients have valid ipv6 addresses and ipv6 dns works just fine.
However I can't get any ipv6 traffic to leave my lan, but ipv6 connectivity works just fine on the router.
I just installed the DEV version and for me there was no difference. I configured the prefix and other settings as before. I had to manually start dhcp6c as above. After that, everything was the same as it was with the other version. The dhcp6 gateway status is "pending", but ipv6 is working.