At what point should i perform the nvram erase, and what method should i use to connect to the router to perform this?
You should erase the NVRAM before and after flashing a new build of DD-WRT, and you can use Telnet, SSH, or the CLI in DD-WRT's web GUI to issue the commands.
...
Be sure to always clear the NVRAM before you flash to a newer build of DD-WRT. I also recommend doing so afterwards, although it isn't as important as doing it before a flash.
With all due respect, I think these are bad recommendations.
Firstly, the second command "mtd erase nvram" is VERY dangerous to use and can brick certain units.
Secondly, nvram erase makes much more sense to be run AFTER the flash. Before is fine too, but after is the relevant one. _________________ THERE ARE NO STRANGERS HERE; ONLY FRIENDS YOU HAVEN'T YET MET.
________________________________________________________________________________________________________
DD-WRT CHANGELOG | DEVICES | DD-WRT BUILDS | KONG BUILDS | UNOFFICIAL BUILDS | DD-WRT in VIRTUALBOX
...
Be sure to always clear the NVRAM before you flash to a newer build of DD-WRT. I also recommend doing so afterwards, although it isn't as important as doing it before a flash.
These are some bad recommendations.
Firstly, the second command "mtd erase nvram" is VERY dangerous to use and can brick certain units.
Secondly, nvram erase makes much more sense to be run AFTER the flash. Before is fine too, but after is the relevant one.
Yes, but on the E1000v2 I've seen the "mtd erase nvram" work for people whereas "erase nvram && reboot" didn't. It it possible people are getting the syntax wrong and then bricking their router? As far as clearing NVRAM before and/or after the flash, I was under the impression that a higher importance was placed on getting rid of the old values before flashing a new build. I just do it before and after to be on the safe side.
Router: Buffalo WZR-HP-G300NH
Firmware: DD-WRT v3.0-r28493 std
Kernel: Linux 3.10.94 #13344
Status: OK
Reset: erase nvram (before and after)
Errors: see below.
1) http://svn.dd-wrt.com/ticket/4742 was reopened since webupgrade from r28417 to/from r28444 to r28493 bricks router. this is now with erase nvram/reboot before and after, lets say I had a busy night.
2) Openssl complain that it has no configuration file...
I have to look into adding a non-crippled up-to-date openssl version in ipkg or something, the rsa key and certificates that are shipped are so basic and weak that almost not worth bothering.
Jst wish I had patience to compile and chnage things like this.
3) Disabled cron and router become inaccessible via browser when I pressed apply settings. But everything else was still working. a blurb perhaps?
Good things... Dark styles are all dark now, really nice. Enabling USB worked without a hickup (havent plugged anything into it yet), ssh works, wifi works... _________________ Buffalo WZR-HP-G300NH - Firmware: DD-WRT v3.0-r29440 std (04/11/16)
_________________
Signature truncated: cannot exceed 20.000 lines!
Router: TP-link WDR4300 v1.7
Firmware: r28493
Kernel:
Status: webflash OK
Reset: before and after - "erase NVRAM" and "reboot"
Errors: still testing.
5 ghz wifi working so far....crossing fingers _________________ ----------
TP-LINK WDR4300 V1.7 - version History:
r27944 - 5ghz wifi dissapearing, otherwise fine
r28493 - currently testing
Router Model
TPLINK ARCHER-C7 v2
Firmware Version
DD-WRT v3.0-r28493 std (12/10/15)
Kernel Version
Linux 3.18.24 #6979 Thu Dec 10 05:00:58 CET 2015 mips
Router: WDR4300 v1.7
Firmware: r28493
Kernel: Linux 3.10.94 #13370
Status: OK
Reset: 30/30/30 and erase nvram && reboot before and after
Errors: none
Main reason for this upgrade was 5Ghz line.
It disappeared after a while; now I've ran speed test 10 times and 5Ghz is still live. Hope it'll stay like this.
Error: IPv6 shows in the console but no ipv6 address and even disabled the ipv6 still show in the console
It works for me. So, if you want help we need more details. Post some more details about your IPv6 configuration such as:
Do you use:
6in4 tunnel, native IPv6, IPv6 with prefix delagation?
Do you use:
DHCP6s, Radvd or DNSMasq for advertising and handing out addresses?
Do u have custom or default configuration?
Give us output of:
cat /tmp/radvd.conf
Remember that radvd does not advertise ipv6 dns servers to windows clients via RDNSS. Linux and ios devices work just fine. Radvd provides stateless configuration for ipv6 clients.
My suggestion to you: disable radvd, dhcpv6s, dhcpv6c and try to USE DNSMASQ custom settings for IPv6.
Joined: 24 Feb 2013 Posts: 1634 Location: Belgrade
Posted: Sat Dec 12, 2015 7:22 Post subject:
you are on Comcast and you have prefix delegation... I don't know how to setup DNSMasq for that kind of configuration... I just have 6in4 tunnel... try to contact JAMESMTL (forum member). He knows everything about ipv6...
Posted: Sat Dec 12, 2015 8:58 Post subject: 28493 TP-Link TL-WR841NDv9
Router: TP-Link TL-WR841NDv9
Firmware: DD-WRT v3.0-r28493
Kernel: Linux 3.18.24 #6971
Status: working
Reset: No
Errors: None so far
uptime now about 22h, until now no occasional dropouts of wan-internet-connectivity (we had this with some former builds in the last time). gui fast and nice.
is "erase nvram" also recommended for this kind of router when updating one of these newer builds?
Router: D-Link DIR-859 A2
Firmware: r28493
Kernel: DD-WRT v3.0-r28493 std (12/10/15)
Status: Works fine
Reset: no
Errors: Cosmetic, shows 5ghz side connected at 1.08308e+06 Gb/s , r28211 doesn't do this, r28444 and r28493 both do this.
A bit faster speeds on 2.4 and 5ghz with stock d-link firmware but the dd-wrt software works ok.
Can only use 5ghz channels with +upper, if selecting +lower radio doesn't work.
2.4 Ghz radio stays off unless you enable Mac Address Clone feature.
...
Be sure to always clear the NVRAM before you flash to a newer build of DD-WRT. I also recommend doing so afterwards, although it isn't as important as doing it before a flash.
These are some bad recommendations.
Firstly, the second command "mtd erase nvram" is VERY dangerous to use and can brick certain units.
Secondly, nvram erase makes much more sense to be run AFTER the flash. Before is fine too, but after is the relevant one.
Yes, but on the E1000v2 I've seen the "mtd erase nvram" work for people whereas "erase nvram && reboot" didn't. It it possible people are getting the syntax wrong and then bricking their router? As far as clearing NVRAM before and/or after the flash, I was under the impression that a higher importance was placed on getting rid of the old values before flashing a new build. I just do it before and after to be on the safe side.
As has been mentioned many times, there is no need to reset / erase _________________ TPLINK TL-WR2543ND (5GHz)
WRT160NL (2.4GHz)