DLink 645 - Compatible with IPv6

[andrue]

Important note: As it comes out of the box (and after a firmware update) the router refuses to route. You have to plug your computer in to it directly(*).

• Get IPv4 working - but don't do anything more than the basics.
• Update the firmware (1.0.3 is what I'm using) - this will clear the settings (charming  ).
• Reinstate your IPv4 settings - maybe some others if you're feeling optimistic.
• For IPv6 choose 'IPv6 over PPPoE' from the drop down. Choose to share the IPv4 session.
• Job's a good 'un - now you can do the rest of your tweaking.

You might want to enable the IPv6 firewall. I checked 'enable simple firewall' and also set it to 'on and allow rules' but haven't given it any rules yet. I also noticed that a new option with that firmware on the generic firewall page is 'enable SPI' which was unchecked by default    so prolly advisable to check that.

You might also want to enable 'Respond to pings from WAN' if you use TBBQM since that defaults to off.

(*)There's probably a good reason for it but I choose to think it's because they want to piss me off. 

[Steve]

Well at least it works which is more than can be said for some IPv6 compatible routers.

[andrue]

Well at least it works which is more than can be said for some IPv6 compatible routers.

Got a nice graph to prove how well it works. IDNet should stick this on their wall given the time it was taken:



Flat as the proverbial pancake and with a sync of 65Mb/s I think that deserves a 

[Steve]

I must give another try with that speedtest I've often been worse than IPv4, I'm currently not using it as the later beta firmwares for my router Asus RT N66U are not compatible with IDNet  IPv6 anymore.

[andrue]

the later beta firmwares for my router Asus RT N66U are not compatible with IDNet  IPv6 anymore.

So more a case of 'worse' rather than 'beta'

[Steve]

 

Sadly I expect the firmware is compatible with other implementations but dynamic via Native DHCP-PD never worked, static IP doesn't work anymore, strangely static used to work before they corrected a genuine Wan prefix length error.

[Steve]

OS X decides which is best for you in terms of latency etc when using IPv4/IPv6, although most browsers should use IPv6 in preference. Having managed to force IPv6 on Chrome. I got this which is not bad for my long connection to the cabinet.