Posted: Mon May 29, 2017 1:30 Post subject: R7000 random loss of IP configuration<-- Need real advice
Hey guys, as i said in the topic I have a R7000 running : DD-WRT v3.0-r31980M kongac (05/11/17). I also had this issue on the build before this as well. At what seems to be random times the devices lose their IP configs. Not being able to restore this via normal ip renews i have to reset the router. I am able to get the control panel at 10.0.0.1 during this time. Just no internet connection. This issue did just happen about 5 mins ago be fore posting this, I did my normal reset and tried to reconnect and the wired connection has a address of 169.254.246.104/16 <--windows just assigning a address. The wireless has a DHCP address of 10.0.0.153/24, the wireless connection is working normally at this point not the wired. Just for troubleshooting help i do notice every now and again the WAN LED goes amber for a sec and then back to the normal white, i dont know what this means do to DD WRT not having a manual. I also believe i have be the WAN go solid amber and no internet connection forcing me to restart.
Anyone have any clue as to why this is happening?
Last edited by nhagney on Tue May 30, 2017 5:01; edited 1 time in total
Joined: 16 Nov 2015 Posts: 6435 Location: UK, London, just across the river..
Posted: Mon May 29, 2017 10:32 Post subject:
to me it seems like corrupted flash, i also had bad experience setting router address different from 192.168.x.x but that was in the past...so erase nvram, download new build and re-flash (strictly from LAN side/cable) and dial all settings manually if this doesn't work it might be a hardware related issue...who knows?? _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55779 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Last edited by Alozaros on Tue May 30, 2017 17:50; edited 1 time in total
Before I flashed the new firmware I did do a 30 30 30. This was from modded firmware to modded firmware. Think I should flash original then back? The original firmware does not do this. And I use 10.0.0.x cuz it's almost easier to type
OK heres where im at with this. I took screenshots of every tab and then preformed a GUI factory reset. Then a 30-30-30 then reflashed a fresh copy of DD-WRT, and again one more 30-30-30. Now we sit and wait and see if it happens again.
Last edited by nhagney on Tue May 30, 2017 9:29; edited 1 time in total
OK so its late and im kinda tired. someone posting this link in one of my other posts. Read the part about 30-30-30s not working on ARM systems. Also Kong was posting in this same forum post saying you have to use command line to wipe the NVRAM. Can anyone shine some light on this?
<Kong> wrote:
b0xBR wrote:
Hello.
Since last year, my eth2 (5GHZ) has been bugging my router, for that reason, I've disabled it with command (wl -i eth2 down) + Radio Scheduling. Yesterday, I tried to restore my 5GHZ, reconfigured, rebooted and tested. The "funny" thing happened when I did a LAN transfer at 2.4GHZ, which gave me incredible 25mb/s stable transfer speed. Then, the router simply crashed and I had to reboot manually. I reconfigured without eth2 (command + schedule) and router became stable once again. After all that, I did another LAN transfer at 2.4, which gave me 10mb/s stable. Does anyone have any idea to workaround this "issue"?
In case you have never done an erase nvram. I recently flashed several R7000. In a hurry I forgot to run erase nvram on one unit, after flashing dd-wrt. This exact unit randomly crashed once or twice a day, took me a while to nail that down.
I have seen bad params in netgear and tomato dumps, that cause instability. The default var init behavior in dd-wrt is to only initialize vars with defaults, if they do not exist. And since some vars on several units need to be protected they will not even be cleared with factory defaults from webif.
For all netgear units "erase nvram" is safe and the only way to ensure you have the params that I tested/defined.
I have a large number of R7000 with different configs running they are 100% stable, both radios.
slidermike wrote:
**last updated October 30 2016** **as of Feb 2015** BrainSlayer & Kong now have a newer/working Broadcom driver that corrects the issue many users experienced with random router reboots due to certain 2.4ghz clients.
BS builds are all labeled "beta" so your a tester if you install it. Report your findings in the forums but do not complain about free beta software.
Kong builds are personal test builds (also referred to as PTB) so again please report your findings in the forums but do not complain about free beta software.
**WDS MAC BRICKING** :
routers are recoverable through the serial interface. The WDS bricking problem has been known about for months, but was not widely advertised. A trouble ticket was opened in TRAC (a development and bug tracking system), but was closed with no resolution. If you must have WDS then don't use any firmware newer than 25974 which uses older Broadcom drivers.
- Magnetron1.1
With the newer firmware Kong has noted the need to do a command line nvram erase to ensure a full reset to default for proper router operations on all Netgear routers.
The default var init behavior in dd-wrt is to only initialize vars with defaults, if they do not exist. And since some vars on several units need to be protected they will not even be cleared with factory defaults from webif.
How to adjust assign specific cpu to radios.
If you want to try it, add this to your start up script. It is all 1 line.
echo 2 > /proc/irq/163/smp_affinity && echo 1 > /proc/irq/169/smp_affinity
Over Clock router cpu (thanks to Magnetron1.1)
nvram get clkfreq (get current clock rate)
nvram set clkfreq=1200,800 (OC cpu/ram stock)
nvram commit && reboot (write change & reboot)
Changing ram speeds to anything other than 800 appears to default the ram to 400. CPU OC is dependent upon you hardware.
Some get 1400/800 stable, some 1200/800.
Stock is 1000/800.
OC at your own risk.
Transmission on R7000 - how to (thanks to ddaniel51)
First you load the firmware build with BT included.
Then mount a usb drive to /opt.
Go to Services/NAS, enable Transmission, set the path to /opt/transmission, Save, Apply.
Open a browser, go to 192.168.1.1:9091 (router ip address if not default) to access the transmission GUI.
Search on the web for transmission tutorials. You'll find a bunch to choose from.
^^^ dd-wrt to stock firmware ^^^
(from Kongs read me)
To go back to netgear just flash netgear firmware from my build. I implemented this method and this is not always supported for other vendors.
^^^ Reset to default via GUI ^^^
For a reset just use the webif Administration->Factory defaults.
^^^ Reset to default via telnet ^^^
mtd -r erase nvram (this will reset & reboot it)
^^^ clear admin password via command line ^^^
By the way if you don't want to remember the cryptic password you can just set an empty password before flashing, at least this works when flashing back to netgear firmware you can then login without password.
nvram set http_passwd=""
^^^ restart gui interface from command line ^^^
stopservice httpd
startservice httpd
^^^ Disable Lights ^^^
add this to your startup script to disable the lights on your r7000.
for i in 2 3 8 9 12 13 17 18 ; do gpio enable $i ; done
for i in 14 15 ; do gpio disable $i ; done
Run this from the command line to disable the 4 LAN lights.
et robowr 0x0 0x18 0x1ff
et robowr 0x0 0x18 0x0
et robowr 0x0 0x1a 0x0
^^^ Having issues with random reboots? Try this ^^^ On code prior to 2/2015
from the command line run
nvram set wl0_ampdu=off
Install new build and erase again to be sure.
Put your settings in manually.
Latest Kong build can be found at: http://www.desipro.de/ddwrt/K3-AC-Arm/ see the Supported models for which build you have to use, for the R7000 it is the dd-wrt.v24-K3_AC_ARM_STD.bin I think
I think you might be right here. As i have said in other posts im new to DD-WRT, why is it that this is labeled dd-wrt.K3_R7000.chk? This is what i flashed but based on the information in the .txt is says i should have dd-wrt.v24-K3_AC_ARM_STD.bin. My main reason for wanting to learn all of this is because im going to school for Computer Science and working to become a Network Administrator/Engineer. I believe working with this firmware will teach me a lot, not only that it makes my router do everything, not forcing me to get different devices or software to meet my needs/wants.
P.S. 192.168.0.x spectrum failed i was watching a movie and my network took a dump again.
Joined: 16 Nov 2015 Posts: 6435 Location: UK, London, just across the river..
Posted: Tue May 30, 2017 10:16 Post subject:
ok so its not due to bad flash
its not due to reflash
you did erase nvram and manual config
then whats left??
Check your wi-fi clients/devices for corrupted drivers or incompatibility, check your wi-fi settings, check your
power supply, and finally you can get USB to TTL serial connection and connect and debug, i would ve start with that first but consider you are not into a soldering and serial connection establishment you can try all above and keep reading....
Very often wi-fi dumps are due to corrupted power supply, or bad client / settings...
Not bad idea to check for malware especially if you have IP cams or any smart devices connected to the unit....
I've recently found one of my smart devices was generating fair amount of UDP traffic and my router was locking up, so using VLAN i had to isolate this device on its own network at router level, but unfortunately due to bad settings i couldn't make it work, so i just got a managed switch and isolate this device from there
Do you have a lots of WI-FI networks around are you in congested 2,4Ghz area, is the unit too hot or overheating ?? Does your cat sleeps there on the top of it ? _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55779 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
ok so its not due to bad flash
its not due to reflash
you did erase nvram and manual config
then whats left??
Check your wi-fi clients/devices for corrupted drivers or incompatibility, check your wi-fi settings, check your
power supply, and finally you can get USB to TTL serial connection and connect and debug, i would ve start with that first but consider you are not into a soldering and serial connection establishment you can try all above and keep reading....
Very often wi-fi dumps are due to corrupted power supply, or bad client / settings...
Not bad idea to check for malware especially if you have IP cams or any smart devices connected to the unit....
I've recently found one of my smart devices was generating fair amount of UDP traffic and my router was locking up, so using VLAN i had to isolate this device on its own network at router level, but unfortunately due to bad settings i couldn't make it work, so i just got a managed switch and isolate this device from there
Do you have a lots of WI-FI networks around are you in congested 2,4Ghz area, is the unit too hot or overheating ?? Does your cat sleeps there on the top of it ?
Last night I was going to flash with the .bin and tried the erase nvram command via the web GUI interface. This resulted in non of my setting wiping. So I thought maybe the actual RAM is still holding the config. Ran the reboot command, still the same config was there. I then tried erase nvram again and made the device lose power via the power cable. The system booted back up and still nothing I had all the same settings. Then I used the GUI to factory reset. Idk what commands the GUI has for the factory but it worked. Then I flashed the .bin we talked about above ensuring to check via MD5 CHECKSUMS. also is not only the wifi that is affected. Everything I own I plug directly into the R7000 or a 24 port switch running directly from the R7000, the only wifi devices running on wifi are my cell phones, the device does this weather im at home or not because i have my phones with me when im away. I just woke up for the day and am now going to manually config this router once again. SO MANY SETTINGS!!!
egc wrote:
The .chk is for the first flash coming from stock firmware (it has a different header otherwise stock firmware does not want to flash), subsequent flashing can be done with the .bin
Last night when i was trying to "erase NVRAM" be sure to read above for more info, i was looking at the files and i thought this might be the case. So in reality the two config files have the same settings and this would make no real world difference.
So far since i did that last flash with the fail "erase NVRAM" the router has not crashed once today. This might just be luck tho, because i fell like i have had good days before. Anyone have anymore input on this?
The router is still having the same issue. Someone with some advanced command line knowledge ask me what u need from me to find the issue please!! Bump
OK so i have some good news! The router has been up for Time: 00:16:01 up 2 days, 1:42. I have had zero issues BUT i dont believe this issue is fix this is just a bump with updates. Update edit - day 3 the router did it again
BS builds are all labeled "beta" so your a tester if you install it. Report your findings in the forums but do not complain about free beta software.
