Weird, the guideline of enabling IPV6 from the first post mentioned D-Link DIR 615 (I assumed the guideline has typo DOR615? Screenshot mentioned otherwise).

But there is no "Enable Ipv6" checkbox for my friend particular model.
He is using DIR-615 H/W Version G2 with firmware 7.09 and I can't find any IPV6 option.

The highlighted part is what annoyed me to date with this router. Never encountered the problem before with the HE tunnel maybe because HE gives out static /64 and /48. Do you know how to script this so that there is no need to recycle the Ethernet/wireless interfaces in the computers/tablets in the network when a /64 has been assigned?

My new TP-Link TL-WR1043ND with OpenWRT that I have prepared for my other Streamyx 1Mb account doesn't suffer from that problem.

Setting a smaller MTU in the RA's seems the possible using the IPv6 -> ND option in RouterOS

I just tested using both my Windows/Linux boxes.

i. Manually changing the IPv6 address in ROS or disabling/enabling the PPPoE client (sending a PPPoE terminate request and obtaining a new /64 prefix), the Mikrotik sends out an RA and the clients will have the previous + current /64's bound
ii. A BRAS session reset from the headend results in the same behavior from the client .. so hung sessions or administrative disconnects shouldn't be a problem

My Linux client doesn't seem to be unaffected when having multiple /64 prefixes on the interface. Refreshing the client interface may only be needed if you want to purge the older invalid prefixes but it doesn't seem to affect the ability for the clients to utilize IPv6 as long as one of the prefixes is valid. I've tried getting the Routerboard to force the clients to drop the older prefix but nothing seems to work so far.

Interestingly, during one of the server side session terminates I requested.. I was reassigned the same IPv4 address but my IPv6 prefix was incremented by 1.. so it seems the IPv6 prefix isn't being derived from the IPv4 value but rather the session identifier itself.

My experience when using the HE tunnel shows that multiple /64 on client interfaces should not pose any problems. Only that with TM IPv6, I started to have this problem.

Getting the same IPv4 address when recycling the PPPoE connection seems to be common in the pas year or so, that's why I wait for 10 seconds or so between disabling and re-enabling the PPPoE connection.

I think I found out what the problem is:-

Before I recycle the PPPoE connection:-


After I recycle the PPPoE connection:-


This really isn't supposed to happen. The older prefixes are not depreciated.

This post has been edited by Moogle Stiltzkin: Jul 15 2017, 10:31 AM

Hmm, changing the MTU to 1392 in IPv6 seems to done the trick. No problem accessing facebook now.

This post has been edited by vincent_ng86: Oct 20 2013, 12:10 PM

Hmm, how come I don't have the IPv6 tag on my replies although I have gone through the test at http://ipv6test.google.com confirming the availability.

If you use Firefox, then you just have encountered its bug, like I do now.

Just noticed this thread, turned on ipv6 on my router(asus rt n66u) and it works just fine.

Am using Safari on both iOS and OSX. Wondering why.

Firefox seems to prefer IPV4 over IPV6 for some weird reasons

Got it working on my NT-56U. I was using HE.net , finally it is good to have native IPV6 support

This post has been edited by Moogle Stiltzkin: Jul 15 2017, 10:35 AM

I think the IPv6 connectivity to forum.lowyat.net is down ATM.

The TCP MSS fix is applied on '/ipv6 firewall mangle' section. No need to set a static /64 prefix in '/ipv6 address' section either, unlike when you use a HE.net tunnel, because the allocated prefix from TM is dynamic.

This post has been edited by Moogle Stiltzkin: Jul 15 2017, 10:35 AM

In the picture below?



Try DHCPv6 with Prefix Delegation.

This post has been edited by Moogle Stiltzkin: Jul 15 2017, 10:36 AM

Coincidentally, after some downtime on my FTTH link today, at reconnection my BRAS now assigns me an allocation through DHCPv6

Our hosting provider's IPv6 is down, so you guys won't be able to surf the forum over IPv6 until it is rectified.

You can choose to use google's ipv6 dns. Prefix length is 64, yes. Accept RA from WAN only unless this isn't your primary router connecting to the internet.

You could always use wayback machine - http://archive.org/web/ a copy of that site when it was up.