Could it be an issue with the newer 1.06TM firmware you've upgraded to? 1.01TM runs really stable for me and I am looking around for this version of the firmware so that I can revert back to it. I don't want to get stuck at 1.06TM after trying it.

Yes, that is just the configuration backup. But what if you want to downgrade to 1.01 firmware? Because 1.06 might be the culprit for frequent dc. I had no dc issues with 1.01

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.

Yes, I wanted to suggest the same as it is more efficient. I've tried matching the MTU advertisement to the pppoe line's MTU (in my case 1492) and it works. I wonder what about the 60 bytes overhead deduction that the linked blog on MSS suggested. 1492 works fine for me. Clamping MSS is a work-around and technically not the solution. As a fail-safe approach, start setting your MTU advertisement to the min value of 1280 and slowly increase from there.

A more conclusive way to test whether your MTU setting works is to use the "Other IPv6 Sites" tab on http://test-ipv6.com/ after successfully running the initial test. This should properly test your MTU against many different servers located all around the world using IPv6. Don't be alarm if you get a grey-bluish dot, as some servers might be down occasionally but you should be getting green ticks otherwise:



By the way, when will lowyat.net's IPv6 connection be up? I am starting to miss those IPv6 tags already.

Your primary router is the device that performs the pppoe connection through your modem. Is that Microtik switch performing the internet connection? Not familiar with that Microtik device as it sounds like just a switch? Anyway, if your Linksys connects to your Microtik via Linksys's WAN port, then yes.

True, it does depend on the websites you use. I personally find google dns much faster compared to open dns. If you want to give priority to local servers, use TM for primary dns and google for secondary dns.

It is indeed a typo. Key "i" and "o" are next to each other on the keyboard. I guess the person who put together that ipv6 guide was pressed for time.

You need to update your firmware.

This post has been edited by Alpha Wolf: Oct 21 2013, 07:34 AM


Attached thumbnail(s)

Like I've mentioned, use wayback machine. Latest snapshot January 2013. I thought his site was down far back than this?
http://web.archive.org/web/20130118122637/...tik_rb250gs.php

Looks like it's just a switch indeed. Dial up is performed by your modem. Which modem are you using?

This post has been edited by Alpha Wolf: Oct 21 2013, 07:12 AM

Yeah, for some reason dual wan cannot be enabled in fw 1.01.

You need to get a copy of the 1.01 firmware first, where DellMalaysia has requested through an email awaiting reply from TM. This is also the reason why I am in search for that firmware.


I was having the same issue with RA clients preferring the older prefixes over the newer ones, thus accumulating a long list of v6 addresses. For wireless devices, his can be fixed by disconnecting and reconnecting to the network. But this can be troublesome. The solution is to shorten the lifetime these prefixes remained preferred in the RA deamon. Most ISP provide static prefixes as v6 prefixes are meant to be static in general, hence why RA deamons have it set to 1 day or more. For some reason, TM is handing out dynamic prefixes. If your router uses radvd like mine for RAs, you can configure this in the config file within the prefix section:

Otherwise, look for settings related to the time advertised prefixes remain valid.


Just when I was about to wonder if anyone else was using DD-WRT with IPv6... I guess technically none yet?

Incidentally, I've spent the last few days relentlessly sorting out and getting IPv6 connection working with DD-WRT. It was an IPv6 learning experience for me too as I was completely new to IPv6. I finally have my Asus RT-N66U running on DD-WRT fully working with Unifi's native IPv6 along side 500 and 600 vlan tagging.

Currently DD-WRT has less support for IPv6 compared to other custom firmwares like Tomato and OpenWRT, at least this is according to the web interface of DD-WRT, most of which needs to be manually configure using the command line interface and script files. But being well accustomed to DD-WRT and its extensive features, I wanted this to work. Only the big builds have IPv6 modules included, but with optware and ipkg and lots of patience, it's fully possible.

In short, here are the applications I am using:
1) rdisc6 to get ICMPv6 from ISP for the WAN interface.
2) DHCPv6 client to get v6 prefix from ISP.
3) and finally radvd to advertise that obtained prefix out to clients.

I also added and configured ip6tables for the v6 firewall.

Here are more details on my setup. Note this is a custom web interface page I included using the MyPage feature of DD-WRT for debugging and status purposes. So far it's been running really stable. No point in masking my IP addresses since they are dynamic plus I run a server.


This post has been edited by Alpha Wolf: Oct 21 2013, 08:17 PM


Attached thumbnail(s)

Good point, I read about that too. I will have it adjusted. The default settings for radvd is 1 day valid and 4 hours preferred.

This post has been edited by Alpha Wolf: Oct 21 2013, 08:18 PM

Honestly, if I did not reconnect to TM with my router so frequently during my debugging phase, this issue would have been non-existent for me. In fact, I could have left them at the default settings because I leave my router running 24/7 and my pppoe connection is rock solid. This setup is only required if you get very frequent disconnects on your pppoe connection and it auto reconnects within less than the preferred lifetime setting.

It's not really a "fault". But if I were to blame something, it's the dynamic prefixes that TM hands out.

If you reboot your router that connects to your client devices, the prefixes would automatically clear themselves, just like how disconnecting and reconnecting the ethernet interface on the client devices solves the problem. Rebooting your router is analogous to disconnecting and reconnecting to your client devices. So I really don't see any issues in this at all.

I have a an access point connected to my router which my wireless laptop still connects to when I reboot my router, hence the old prefixes aren't cleared.

Edit: haha, noticed that you edited to add that picture

This post has been edited by Alpha Wolf: Oct 21 2013, 08:41 PM

Interesting approach but I wonder if it works. This could be scripted in DD-WRT - launch radvd with a separate config file with 0 ValidLifeTime then kill radvd and launch it again with the primary config file.

The web interface for configuring ipv6 on Tomato looks very promising as they have options for native ipv6. I am sure it's possible.

I'm considering where to place such a guide because it is going to be long and it pre-requires enabling jffs for installing additional applications or using optware and most importantly, running startup scripts to automate the process every time it boots up. Depending on the version of dd-wrt, additional ipv6 modules need to be downloaded and loaded onto dd-wrt separately.

As for my setup, the only thing I'm wondering about right now is: Why do I get two different v6 prefixes for my WAN and LAN? Shouldn't they be the same? Also, I can reach my router from the external internet by using both my WAN or LAN v6 IP.

This post has been edited by Alpha Wolf: Oct 21 2013, 09:16 PM

Yes , but this could all be easily scripted. You only need to get the right modules and application for your version of dd-wrt, particularly if you're using a different Linux kernel version. I am using the latest K3.X.

On a side note, I had to modify and compile a switch driver to enable support for vlanids above 15, namely 500 and 600 that Unifi uses, for my Broadcom based router running linux kernel 3.10. This enables me to directly connect my dd-wrt router to the fiber modem. One less device to run 24/7 and no more requiring the use of that TM router as a bridge for internet, plus my IPTV still works when I need it.

I could now use that L7 TM router for testing. Doubt it will work but maybe I could try flashing it with dd-wrt.

This post has been edited by Alpha Wolf: Oct 21 2013, 09:32 PM

Oh good! So I'm not over pulling a prefix too many or anything like that. I still find it interesting how I can use both my WAN and LAN v6 IP as my public IP. It's like I'm having two public addresses. I guess IPv6 has too many addresses to offer. The way IPv6 works is almost entirely different from IPv4, apparently it's not just as simple as "adding more addresses". I've never tried tunnels as I started straight with native IPv6.

You are only required to enable JFFS support on your router to use ipkg. Then, attach a usb drive to your router and bind mount it to /jffs and poof! Your jffs has the space of your USB drive! You have to change your usb mount path accordingly.

Instead of going through the hassle setting up tunnels, an ipv6 proxy could be used. http://www.ipv6proxy.net/

IPv6 and IPv4 can run concurrently so they will have both.

Is there no way to run downloaded ipkg installations on routerOS like WRT-based OS?

good job Took me slightly longer to get it all figured out in dd-wrt. Good to see that the LAN and WAN prefixes are indeed different.


My S2 support IPv6 out-of-the-box without any extra settings, so I'm assuming S3 and Note 2 and any products later should. Just make sure your web browser app supports IPv6. I tested it on Dolphin.

Have you actually tired restarting both the modem and your computer?

Make sure that you are connected to an IPv6 network then visit a site like test-ipv6.com to test your ipv6 connectivity. Most mobile internet do not have ipv6 yet like my umobile.

Here's my test in chome browser app:


My S2 doesn't show the ipv6 address in the wifi connection details nor the phone status page but that test site shows my ipv6 address and it has full 10/10 v6 connectivity.

Btw, this post is sent from my S2 for extra testing too.

As for your dc issues, do you think it's related to your firmware update?