Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Custode]

I've done quite a bit of research here on the forums and to my understanding there seems to be an issue with getting the router to assign IPV6 addresses.  I know for a fact that my ISP (comcast) supports "native" IPv6.  I can see on the status page of the router that it does indeed have a IPv6 address, but I can't for the life of me get it to assign my PC one.  I've tried nearly all of the different options available under the IPv6 manual setup.  I'm using the latest firmware for NA (DIR868LA1_FW109b08).  Does anyone have an additional advice for me, or is there anything that I can do to fix this issue?

[Custode]

Just a quick update, as of this morning I've been able to get it working by manually setting the IPV6 Connection to:
Step 1:
Autoconfig/DHCPv6 
Manually setting the DNS servers to public google addresses: 2001:4860:4860::8888 and 2001:4860:4860::8844
Enable DCHP-PD: checked
Enable Automatic IPv6 address assignment : checked
Enable Automatic DHCP-PD in LAN : checked
Autoconfiguration Type: SLAAC+Stateless DCHP

Step 2:
IPV6 Local Connectivity Settings

Enable ULA : checked
Use default ULA prefix : checked

Step 3: This is the most important and it suddenly started working after I did this
I went to the "Tools" section of the router and clicked "reboot the device"

Boom after that my PC had an IP6 address.  I don't know how consistent it will be, and I'm scared to reboot the router in case I lose the address.  Hope this helps somebody though, I will update the post if anything changes.

[FurryNutz]

Link>Welcome!

• What region are you located?
• Has a Factory Reset been performed?
• Was a Factory Reset performed before and after any firmware updates then set up from scratch?

>FW Update Process

Internet Service Provider and Modem Configurations

• What ISP Service do you have? Cable or DSL?
• What ISP Modem Mfr. and model # do you have?

Yes selecting ULA enable will get you IPv6 addresses on devices.

[Custode]

I'm located in New Jersey, (NA Region  I suppose)
No, I have no performed a factory reset.  To tell you the truth I turned the router on and then went right to the DLink website to see if there was an update available.  No factory reset has been performed at all.

Comcast (Xfinity)
Arris TMG822

[FurryNutz]

Please follow the FW Update Process for future use.

Thanks for sharing your information.

Enjoy. 

[koroziv]

If you have hw rev A do not bother with ipv6, will not work; ULA trick works some times, but after a router restart you have to do it again. I have tried 3 units, all are the same, so no point in changing it, except maybe to a rev B (not sure if that has proper ipv6, but here is hoping)
Maybe a manual routing configuration is a more permanent solution, but I don't know exactly how to do it. For me is pointless anyway, as they resolved pppoe offload  issue just for ipv4, on v6 is maxing out aroun 250 mbps.

[FurryNutz]

The connection between your ISP and the OP ISP differs as well. 

I've used the ULA check an it's maintained addressing for me. I haven't had to re-enable it. There maybe some differences between NA and EU FW since each region does there own thing.

[koroziv]

The op is talking about native ipv6, I also have native ipv6 and I just shared what I know about the issue. As far as I remember you do not have a native ipv6 connection to test this issue, and ULA settings should not be used with native, at least they are not supposed to be mandatory.
For me it is obvious a problem with the router, since I have successfully used 4 other models (not dlink) at my location and configured about 10 other for clients of the same ISP. All of them worked out of the box, no special tricks or advanced know-how required.

[FurryNutz]

Have you contacted D-Link about this? You'll need to talk to your regional office regarding this. If your experiencing IPv6 issues then it's a FW issue, not a HW issue with your router. Your regional office would need to have a look and see where, if any fixes with in the FW, can be done. You did mention that you had enabled ULA and it was working for you:
http://forums.dlink.com/index.php?topic=55423.msg214336#msg214336

It seems that for this user, ULA is working for him and this model router. Possibly the handling between the router, ISP modem and his services are working correctly for him since he hasn't posted back with any issue.

[koroziv]

I have talked to dlink, provided all traffic captures required except the one with the wan packets, I did not had the hardware to do that apparently. They acknowledged the problem but no solution: the router is getting ipv6 address from the isp but is not broadcasting ipv6 addresses in lan; few months later a mysterious hardware revision B appears on the market, not a word with what exactly was changed and why... 
PS: I'm also curios if it still works for OP after router restart.

[FurryNutz]

The NA region it's getting Rev B I guess. If you find a Rev B, let us know if the problem still occurs or not. I think mainly Rev B is the new UI. HW wise, don't know if there is any differences. 

Guess will have to see if he returns or not.