Joined: 16 Apr 2016 Posts: 307 Location: California
Posted: Wed Sep 21, 2016 21:40 Post subject: Ssh In and type erase nvram
Panja wrote:
Router: TP-Link Archer C7 v2
Firmware: Stock firmware --> dd-wrt r30631
Kernel: Linux 3.18.41 #812 Wed Sep 14 04:00:26 CEST 2016 mips
Status: Ok, so far (uptime: 15 minutes)
Reset: Yes
Errors: None so far
Side note though:
I have 2x Archer C7 which I flashed the same way, using:
Stock firmware -> 30/30/30 -> factory-to-ddwrt.bin -> 30/30/30 -> tplink_archer-c7-v2.bin -> 30/30/30
Both are configured the same (dumb wireless ap), though 1 Archer reboots in 31 seconds while the other takes more than 90 seconds!
The one that reboots in 90 seconds also takes 30 seconds more before the dd-wrt webpage/interface can be loaded.
The other Archer can be accessed right after booting up.
Identical devices, very different behaviour...
Anyone have a clue why?
Don't do a 30/30/30
Simply SSH or Telnet into the router and type "erase nvram"
then
reboot && exit
I dont know why ppl keep doing 30/30/30
Probably my guess is one of your 30/30/30 didnt go right or possibly a corrupted flash.
Posted: Thu Oct 06, 2016 11:32 Post subject: Re: Ssh In and type erase nvram
sploit wrote:
Panja wrote:
Router: TP-Link Archer C7 v2
Firmware: Stock firmware --> dd-wrt r30631
Kernel: Linux 3.18.41 #812 Wed Sep 14 04:00:26 CEST 2016 mips
Status: Ok, so far (uptime: 15 minutes)
Reset: Yes
Errors: None so far
Side note though:
I have 2x Archer C7 which I flashed the same way, using:
Stock firmware -> 30/30/30 -> factory-to-ddwrt.bin -> 30/30/30 -> tplink_archer-c7-v2.bin -> 30/30/30
Both are configured the same (dumb wireless ap), though 1 Archer reboots in 31 seconds while the other takes more than 90 seconds!
The one that reboots in 90 seconds also takes 30 seconds more before the dd-wrt webpage/interface can be loaded.
The other Archer can be accessed right after booting up.
Identical devices, very different behaviour...
Anyone have a clue why?
Don't do a 30/30/30
Simply SSH or Telnet into the router and type "erase nvram"
then
reboot && exit
I dont know why ppl keep doing 30/30/30
Probably my guess is one of your 30/30/30 didnt go right or possibly a corrupted flash.
I didn't have time earlier to have a go with it but now I have.
Just tried to flash again, NOT doing the 30/30/30 method but doing erase nvram instead. Same problem. One of the Archers takes forever to boot, the other one is fast as lightning.
