Print

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

[TheTripod]

Hi all,

I recently purchased a DIR-860L and have been attempting to configure it to get IPv6 working. All of my devices can get IPv6 internet access when connected directly to my ISP's network termination device, however with the DIR-860L none of them are able to get IPv6 WAN access.

I have compiled an image here: http://i.imgur.com/dnWSzKv.png containing screenshots of the DIR-860L's current IPv6 configuration page and the Windows and DIR-860L IPv6 status pages. As can be seen addresses do look like they're being assigned to clients, but no matter what options I select in the router for IPv6 none of the clients, Windows or Android, receive IPv6 internet access. However pinging IPv6 addresses from the DIR-860L's web interface does work, so it would seem the IPv6 WAN settings are correct in the router.

I've disabled all software firewalls, and all of the DIR-860L's internal firewall settings, and attempted disabling IPv4 even to test things, but nothing seems to work. If someone has any idea how to get things working it'd be greatly appreciated.

[FurryNutz]

Link>Welcome!

• What Hardware version is your router? Look at sticker under the router case.
• Link>What Firmware version is currently loaded? Found on the routers web page under status.
• What region are you located?

Internet Service Provider and Modem Configurations

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

See that the IPv6 says NONE. Should here be an address here?

[TheTripod]

Hi, thanks for the amazingly quick reply.

Hardware version is A1, and it came with firmware version 1.08 however I upgraded to 1.10 (found on D-Link's FTP only) while trying to get it working but nothing changed.

I am located in Australia, however the router is a US model shipped from the US. My ISP is Skymesh, and I receive a FTTH service provided over the Australian National Broadband Network. The DIR-860L plugs into the NBN Network Termination device (NTD) https://en.wikipedia.org/wiki/NTD_(NBN) which is the same for all FTTH users on the NBN in the country, a very basic (simple layer 2 I believe) device with no configuration options.

I've confirmed with my ISP that they do indeed use SLAAC and Prefix Delegation, and those options are also what the DIR-860L's IPv6 auto-config selects after running. The fact I can ping external IPv6 addresses through the DIR-860L's web interface ping function again does make it seem like the WAN config at least is correct.

If it helps, this is how an IPv6 tracert from my PC plugged directly into the NBN NTD goes:

tracert -6 google.com

Tracing route to google.com [2404:6800:4006:807::200e]
over a maximum of 30 hops:

  1     4 ms     3 ms     4 ms  2401:a400:c44f:b035:d6ca:6dff:fe01:38ca
  2     1 ms     1 ms     1 ms  2401:a400:100:f00d::b4b5:80c0
  3    18 ms    17 ms    17 ms  intercap1.nsw.skymesh.net.au [2401:a400:e2e:beef
::2:1001]
  4    17 ms    18 ms    17 ms  intercap2.nsw.skymesh.net.au [2401:a400:e2e:beef
::2:1002]
  5    18 ms    18 ms    18 ms  2001:7fa:11:4:0:3b41:0:1
  6    18 ms    19 ms    19 ms  2001:4860:0:1::1671
  7    18 ms    19 ms    20 ms  2001:4860:0:1::443
  8    19 ms    18 ms    19 ms  syd09s13-in-x0e.1e100.net [2404:6800:4006:807::2
00e]

[FurryNutz]

Whats the tracert result if you have the PC connected to the router?

One thing, this model router doesn't seem to be officially supported in your region. It's not in the list. So there could be some incompatibilities with this model router and your ISP service with IPv6:
http://support.dlink.com.au/Default.asp

You might phone contact D-Link support in your region and ask them what model router would be support in your region and compatible with your ISP service and IPv6.

[TheTripod]

As in that screenshot, it just hits that 'LAN IPv6 address' as listed on the DIR-860L's status page and dies after that.

tracert -6 google.com

Tracing route to google.com [2404:6800:4006:806::200e]
over a maximum of 30 hops:

  1     7 ms    <1 ms    <1 ms  2401:a400:4301:e601:6e19:8fff:fecc:b588
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.

The reason it can even find that 2404:6800:4006:806::200e google.com address in the first place is only because my ISP runs DNS6 over IPv4 as well I believe.

Also here's the IPv6 routing table the DIR-860L lists if it's also any help: http://i.imgur.com/Lgylpbe.png

Thanks again for any assistance.

(As for the model not being supported, surely there shouldn't be any unique regional requirements for IPv6, it's a global standard right?)

[FurryNutz]

I'll ask another user about this and see if he can have a look at this as he's a IPv6 god. Hehe.

As for regional support, D-Link does handle things differently when it comes to there products and thus we don't have any idea what may or may not work in other region when using cross regional products. Also if this unit failed and you needed to get D-link to help you, they won't as this model was not marketed in your region thus any HW or FW supported would not be handled there. So if there is a IPv6 issue and something different, D-Link AU will not fix it. Just saying.

There are other DIR series models that are supported in the AU region, i.e. DIR-850L,868L, 880L, 890 or 895L.

[TheTripod]

Thanks for that, the issue has been plaguing me all week, hopefully there is a fix. And yeah, I knew I'd need to ship it back to the US if it ever failed, but it should be compatible with basic global networking standards I'd hope...

[FurryNutz]

I hope there can be a configuration fix for you.

[TheTripod]

Just thought I'd let anyone reading this in future know that I've found a solution via rolling with alternative DD-WRT firmware, seems D-Link's stock one is just bugged for certain ISP's IPv6 configurations, (among other IPv6 issues that have been discussed elsewhere in these forums).

[PacketTracer]

Hi,

looking to the IPv6 configuration you provided, everything looks fine. You have to know, that your device includes an IPv6 firewall (see D-Link manual). The default setting D-Link uses for its home routers in general (at least as far as I have observed) is to block any IPv6 traffic in both (!) directions (which is quite usesless: Default should be to allow everything going out while blocking any connection attempts coming in from the Internet).

Hence, in order to make it work, you should have had to configure a single IPv6 firewall rule, that allows any traffic initiated from LAN to go out via WAN to the Internet.

But okay, after change to DD-WRT this information is obsolete know.

PT

[FurryNutz]

Good Luck.

Just thought I'd let anyone reading this in future know that I've found a solution via rolling with alternative DD-WRT firmware, seems D-Link's stock one is just bugged for certain ISP's IPv6 configurations, (among other IPv6 issues that have been discussed elsewhere in these forums).

[TheTripod]

Hi,

looking to the IPv6 configuration you provided, everything looks fine. You have to know, that your device includes an IPv6 firewall (see D-Link manual). The default setting D-Link uses for its home routers in general (at least as far as I have observed) is to block any IPv6 traffic in both (!) directions (which is quite usesless: Default should be to allow everything going out while blocking any connection attempts coming in from the Internet).

Hence, in order to make it work, you should have had to configure a single IPv6 firewall rule, that allows any traffic initiated from LAN to go out via WAN to the Internet.

But okay, after change to DD-WRT this information is obsolete know.

PT

I actually saw those older threads about the IPv6 firewall issues. I tried every config I could, all Windows firewalls and DIR-860L IPv6 firewalls off, firewalls on, firewalls on with a LAN2WAN/WAN2LAN config that allowed everything from :: to ffff:ffff:/etc

Someone else on another forum said something along the lines of "It's probably that your router doesn't know how to do sub-assignments of a routable /64 inside the LAN, and/or doesn't know how to do packet forwarding properly", not sure if that's the case as IPv6's intricacies are a bit beyond me. All I know is that every single IPv6 config I tried over a week resulted in either no IPv6 assignments, or assignments and timeouts after hitting only that "LAN IPv6 address" from multiple Windows 7, Windows 8, and Android clients.

[FurryNutz]

Hope the 3rd party FW will work better for you.