CPU temperature isn't reported by the platform on RT-N66U.
RT-N66 Firmware Version 3.0.0.4.374.4561
- Thread starter D2theZ
- Start date
CPU temperature isn't reported by the platform on RT-N66U.
Just my advice.......and opinion.
Anytime you're moving from firmware to firmware with all the different wireless driver changes and other changes..........you'd be better off resetting to defaults after the update and reconfiguring from scratch. You'll waste a lot more time troubleshooting than it takes you to reconfigure from scratch.....especially if you're a beginner.
But to answer your question, your manual shows you how to save your current configuration. But since you had to ask how to do it, I'll assume you're a beginner.....so definitely my previous advice applies to you.
I see this so many times, where a user upgrades their firmware and then either doesn't do a factory reset to defaults after the upgrade, and/or uses their saved configuration file from a previous version of firmware. Then has problems that they spend a LOT of time trying to track down. Eventually they come back to trying the factory default reset plus manual reconfiguration as a last resort, and things finally start working.
Why not short circuit the long period of chasing problems, and just spend a few minutes doing the factory default reset / clear nvram, and manually reconfigure settings? You'll have less problems, it's really worth the time.
My advice there is, if you have wifi issues after a FW upgrade, just make a backup of your settings, do a factory default reset, and only reconfigure the very basics. Then see if your performance issue is resolved. If not, feel free to restore your saved settings, and look elsewhere for the solution. If however it does fix your issues, then you can continue configuring the rest of your settings.
That way, it will only take you 5-10 mins to confirm whether a factory default reset is actually needed or not.
Yes, unless the issue that was caused by restoring your old settings is subtle enough or seen far enough downstream from the upgrade that you don't run into it for a while. Then you have no idea where it came from. Of course, you can always do a factory reset and manually reconfigure your settings to find out if that fixes it. Exactly what I was talking about *smile*.
Never mind, I know what you mean *smile*.
Rt-n66u ipv6?
If ipv6 is enabled does it look for ipv6 address first, then look for ipv4 if no ipv6 available? Also, here is the century link directions for setup on their modem. I have the modem in bridge mode running with the RT-N66 handling the PPOE connection. How would I use those setup guidlines to setup the RT-N66U?
http://internethelp.centurylink.com/internethelp/modem-c1000z-ipv6rd.html
If ipv6 is enabled does it look for ipv6 address first, then look for ipv4 if no ipv6 available? Also, here is the century link directions for setup on their modem. I have the modem in bridge mode running with the RT-N66 handling the PPOE connection. How would I use those setup guidlines to setup the RT-N66U?
http://internethelp.centurylink.com/internethelp/modem-c1000z-ipv6rd.html
To get 6rd ipv6 working on your asus for centurylink:
1. Go to ipv6 tab on n66u
2. Connection Type=tunnel 6rd
3. Disable the "DHCP Option"
4. Enter the required settings for centurylink; e.g. Border relay, ipv6 prefix, MTU of 1472, etc..
Your web browser will mainly determine if you get ipv6 page or ipv4 page. Your web browser doesn't like a slow connection. If ipv6 is too slow (like my AT&T 6rd connection) you'll often get the ipv4 page even if you have a working ipv6 connection. Chrome, Firefox, Safari etc all behave the same way. They want the fastest connection. They will all attempt ipv6 first.
You should start a new thread for this.
Also see links in post 17. Google is your friend.
https://code.google.com/p/rt-n56u/issues/detail?id=775
sinshiva
Very Senior Member
i have centurylink and am using 6rd.
i use the following;
DHCP Option: Disable
prefix: 2602::
prefix length: 24
border router: 205.171.2.64
ipv4 router mask length: 0
TUNNEL MTU: 1280 (6rd automatically chops frames over 1280 in half.)
dns1: 2001:4860:4860::8888
dns2: 2001:4860:4860::8844
router advertisements: enabled
dhcpv6: enabled
http://stage.results.speedtest.comcast.net/result/449863184.png
i use the following;
DHCP Option: Disable
prefix: 2602::
prefix length: 24
border router: 205.171.2.64
ipv4 router mask length: 0
TUNNEL MTU: 1280 (6rd automatically chops frames over 1280 in half.)
dns1: 2001:4860:4860::8888
dns2: 2001:4860:4860::8844
router advertisements: enabled
dhcpv6: enabled
http://stage.results.speedtest.comcast.net/result/449863184.png
Last edited:
I'm not doubting you, but centurylink uses MTU of 1472 on their own ISP equipment. It never hurts to experiment and use what works best for you. Maybe run a comcast ipv6 speed test to see how it affects ping, speed. Compare the different MTUs.
http://internethelp.centurylink.com/internethelp/modem-q1000-ipv6rd.html
sinshiva
Very Senior Member
1272 is what's recommended if you have PPPoE with CL, PPPoE MTU -20. Mine is non-PPPoE
an aside, i have a hard time understanding how 6rd only reduces MTU by 20 bytes if ipv6 is encapsulated by ipv4; shouldn't it be mtu-40 ?
eitherway, after i read the spec on 6rd, i just said f*ck it and set it for 1280. i did speedtests with 6rd using various MTUs and while the overall bandwidth wasn't lower with something other than 1280, i noticed that it seems to bounce up and down a lot more during transfer, which i think has to do with the reassembly of the packets
also, looks like you read the post before i made an edit, i did actually just add a speedtest result; http://stage.results.speedtest.comcast.net/result/449863184.png
[edit/] the latencies are different due to routing issues atm. right now, i get 15ms to ipv6 google, but 30ms to ipv4. and of course, this is an ipv4 connection
an aside, i have a hard time understanding how 6rd only reduces MTU by 20 bytes if ipv6 is encapsulated by ipv4; shouldn't it be mtu-40 ?
eitherway, after i read the spec on 6rd, i just said f*ck it and set it for 1280. i did speedtests with 6rd using various MTUs and while the overall bandwidth wasn't lower with something other than 1280, i noticed that it seems to bounce up and down a lot more during transfer, which i think has to do with the reassembly of the packets
also, looks like you read the post before i made an edit, i did actually just add a speedtest result; http://stage.results.speedtest.comcast.net/result/449863184.png
[edit/] the latencies are different due to routing issues atm. right now, i get 15ms to ipv6 google, but 30ms to ipv4. and of course, this is an ipv4 connection
Last edited:
Yeah, he's got PPPoE. I've got PPPoE. 1280 won't work with AT&T 6rd. Actually the only viable MTU with AT&T 6rd is 1472. I've tried them all. I suspect that is why century link has 1472 on their ISP supplied equipment for 6rd (for PPPoE). AT&T also uses 1472 on the ISP supplied equipment for 6rd.
sinshiva
Very Senior Member
the qos up limit affects 6rd down
I have Qos disabled.
hi
recently got a n66u router, very good but I'm not as impressed as I thought I would be with the wireless range
Its hardly any different from a Virgin media superhub in terms of range, I'm sure its better for everything else though.
I have my vm SH in modem mode and have the n66u connected up.
I'm currently using the latest asus firmware but Im undecided if I should try the merlin firmware?
Is it stable as I have read a few posts of random reboots?
anyone using latest merlin on n66u?
many thanks
recently got a n66u router, very good but I'm not as impressed as I thought I would be with the wireless range
Its hardly any different from a Virgin media superhub in terms of range, I'm sure its better for everything else though.
I have my vm SH in modem mode and have the n66u connected up.
I'm currently using the latest asus firmware but Im undecided if I should try the merlin firmware?
Is it stable as I have read a few posts of random reboots?
anyone using latest merlin on n66u?
many thanks
L&LD
Part of the Furniture
I'm using the latest RMerlin 374.40 firmware for over 4 days with no issues.
Just a basic user here (wired/wireless LAN and internet), but this is the most stable version yet.
This is the recommended version for all Asus routers except for the RT-AC68U (for stable operation with that model you want 374.40 alpha 4).
Very fast and responsive and the range is as good as any of the old -em versions or before.
Make sure you do a full reset to defaults and power cycle the router a couple of times. Also, use a new ssid or 'forget' the old network on all your clients, then re-associate them for the best performance and stability.
I have tried many firmware versions since I bought my RT-N66U almost a year ago; this is easily the best. The most secure, the most stable, the most features and the highest performance too.
I think not upgrading to the latest firmware (especially an RMerlin version) is doing the hardware a disservice and possibly putting the security of the network at risk too.
Just a basic user here (wired/wireless LAN and internet), but this is the most stable version yet.
This is the recommended version for all Asus routers except for the RT-AC68U (for stable operation with that model you want 374.40 alpha 4).
Very fast and responsive and the range is as good as any of the old -em versions or before.
Make sure you do a full reset to defaults and power cycle the router a couple of times. Also, use a new ssid or 'forget' the old network on all your clients, then re-associate them for the best performance and stability.
I have tried many firmware versions since I bought my RT-N66U almost a year ago; this is easily the best. The most secure, the most stable, the most features and the highest performance too.
I think not upgrading to the latest firmware (especially an RMerlin version) is doing the hardware a disservice and possibly putting the security of the network at risk too.
Similar threads
