Posted: Wed Jan 18, 2017 23:33 Post subject: New r31156 firmware for WRT160NL & E2100L
Attached are r31156 firmware for the WRT160NL & E2100L only
It's been very long time since we had working firmware for these routers.
I installed on the 160NL over current conf (29739) that has been running for months.
I had zero problems installing live but I encourage to do a reboot on the 160NL
before install if it has been up running for long time.
Linksys E2100L
DD-WRT v3.0-r31156 std (01/16/17)
Linux 3.10.104 #751 Mon Jan 16 03:26:53 CET 2017 mips
TEST router
gateway-AP + unbridged ath0.1
SAMBA
QOS
very good
Linksys WRT160NL
DD-WRT v3.0-r31156 std (01/16/17)
Linux 3.10.104 #747 Mon Jan 16 03:24:12 CET 2017 mips
WDS-AP & WDS-Sta
Dedicated wireless bridge. Up couple days -- good
Have you still had no issues with this build on your wrt160nl? I flashed mine yesterday and it has since had to be restarted twice - no contact through web interface and the power led is flashing (as the only one; no lights for the two cables plugged in nor the lan led).
Edit: Didn't have logging enabled, so I can't say what was the issue. Enabled it now.
Just haven't got around to updating this thread --
I never run the test gateway-AP very long. Just enough to see that all main function were working ok.
My WDS-Sta seems perfect.
WDS-AP will drop out after 3 days. Same as some previous builds.
I get these kern err scattered around but I don't think that is really the problem.
ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42100020 DMADBG_7=0x000084c0
ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42100020 DMADBG_7=0x000084c0
ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42100020 DMADBG_7=0x000084c0
ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42100020 DMADBG_7=0x000042c0
ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42100020 DMADBG_7=0x000084c0
ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42100020 DMADBG_7=0x000286c0
ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42100020 DMADBG_7=0x000084c0
The WDS-AP will renew key just like clock work but after few days it just don't. Sometimes it will pick up connection after a
few minutes sometimes it does not. I can go in and click 'Apply Settings' on wireless page and that forces the bridge down/up
and re-negotiates key renewal so it good for while longer.
I've changed wireless setting multiple time and let it run few days but always same problem. Syslog really don't tell much.
Only builds I found that will run WDS for 90+ days are 29739 or 27858 and they still throw the DMA failed to stop in 10 ms but
don't lose key renewal. .... also have slightly less rates with the older builds. 31156 works dang good when its working
BTW, I've run my bridge with 31156 in 'Client Bridge (routed)' setup for a day and never seen DMA failed to stop in 10 ms and it never
lost connection but it is a crappy bridge for what I'm doing.
On my list of things to do this morning is revert back to older build for the WDS setup.
If you have the non-stop flashing power light just TFTP dd-wrt back to 192.168.1.1 (regardless what its previous IP was)
When it reboots it should retain all previous settings you had including its previous IP so be aware of that when trying to reconnect.
Note you will have to set staic IP on your computer accordingly.
Give it plenty of time after TFTP -- takes few minutes -- you'll know when power light quits flashing.
No need to go back to stock --- and don't mess with the reset button.. it's just a waste of time.
Last edited by mrjcd on Wed Jan 25, 2017 12:06; edited 1 time in total
Have you still had no issues with this build on your wrt160nl? I flashed mine yesterday and it has since had to be restarted twice - no contact through web interface and the power led is flashing (as the only one; no lights for the two cables plugged in nor the lan led).
Edit: Didn't have logging enabled, so I can't say what was the issue. Enabled it now.
Shortly after writing the post yesterday I had a 'your-a-dumbass-moment' and realized I should turn off what is causing me grief.
So I set 'Key Renewal Interval' to 0 ...duh, why didn't I do that months ago with other builds???
31156 is working great so far now on the 160NL.
No more kern err ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42100020 DMADBG_7=0x000084c0
No re-autherizathon lags or drops.
This is dedicated WDS link (approx 450 meters antenna to antenna) set to accept only 1 wireless client,
MAC filtered to only each other, WPA2-aes key long as my leg so I am happy without key renewal active.
There is obviously some firmware/kernel issues related to WDS & keyrenewal that have never been sorted.
Couple these cockroach kern.err DMA failed to stop come out of hiding but all in all I've been very impressed.
No lags or disconnects since set key renewal to 0.
Had Sensitivity Range (ACK Timing) set to 900 which is prolly a bit close given both also have 25' LMR 400 coaxial
off antennas. Don't know exact distance to the meter but changed to 1350 (ACK Timing) and rebooted both see if
that will help clean up a bit .... actually the 1350 is what I used on older builds for ages.
It's all good even with the cockroach ---
WDS-AP
root@---:~# tail -15 /var/log/messages
Jan 1 00:00:14 --- user.info : klogd : klog daemon successfully started
Jan 1 00:00:14 --- user.info : resetbutton : resetbutton daemon successfully started
Jan 25 22:47:56 --- user.info : cron : cron daemon successfully stopped
Jan 25 22:47:57 --- daemon.debug process_monitor[951]: Restarting cron (time sync change)
Jan 25 22:47:57 --- daemon.debug process_monitor[951]: We need to re-update after 3600 seconds
Jan 25 22:47:57 --- daemon.info process_monitor[951]: set timer: 3600 seconds, callback: ntp_main()
Jan 25 22:47:57 --- user.info : cron : cron daemon successfully started
Jan 25 22:47:57 --- cron.info cron[1136]: (CRON) STARTUP (fork ok)
Jan 25 23:12:21 --- auth.info login[1368]: root login on 'pts/0'
Jan 26 00:35:05 --- auth.info login[1990]: root login on 'pts/0'
Jan 26 15:12:45 --- auth.info login[8699]: root login on 'pts/0'
Jan 26 15:13:47 --- auth.info login[8704]: root login on 'pts/0'
Jan 26 20:10:09 --- kern.err kernel: [76957.040000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42100020 DMADBG_7=0x000084c0
Jan 27 00:38:47 --- kern.err kernel: [93075.080000] ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42100020 DMADBG_7=0x000286c0
Jan 28 11:37:03 --- auth.info login[28954]: root login on 'pts/0'
root@---:~# uptime
05:37:15 up 2 days, 12:49, load average: 0.00, 0.01, 0.04
WDS-STA
root@---:~# tail -15 /var/log/messages
Dec 31 18:00:12 --- syslog.info syslogd exiting
Dec 31 18:00:12 --- syslog.info syslogd started: BusyBox v1.24.2
Jan 1 00:00:12 --- user.info : klogd : klog daemon successfully started
Jan 1 00:00:12 --- user.info : resetbutton : resetbutton daemon successfully stopped
Jan 1 00:00:12 --- user.info : resetbutton : resetbutton daemon successfully started
Jan 25 22:47:56 --- user.info : cron : cron daemon successfully stopped
Jan 25 22:47:57 --- daemon.debug process_monitor[933]: Restarting cron (time sync change)
Jan 25 22:47:57 --- daemon.debug process_monitor[933]: We need to re-update after 3600 seconds
Jan 25 22:47:57 --- daemon.info process_monitor[933]: set timer: 3600 seconds, callback: ntp_main()
Jan 25 22:47:57 --- user.info : cron : cron daemon successfully started
Jan 25 22:47:57 --- cron.info cron[1118]: (CRON) STARTUP (fork ok)
Jan 25 22:49:10 --- kern.info kernel: [ 97.330000] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
Jan 25 23:13:06 --- auth.info login[1392]: root login on 'pts/0'
Jan 26 15:10:58 --- auth.info login[8795]: root login on 'pts/0'
Jan 28 11:37:41 --- auth.info login[29244]: root login on 'pts/0'
root@---:~# iw ath0 station dump
Station 00:25:9c:c0:6a:cd (on ath0)
inactive time: 0 ms
rx bytes: 15876863585
rx packets: 11055567
tx bytes: 1094806788
tx packets: 5647182
tx retries: 1451528
tx failed: 273
beacon loss: 1
beacon rx: 25991
rx drop misc: 109497
signal: -56 [-58, -92] dBm
signal avg: -55 [-56, -91] dBm
beacon signal avg: 208 dBm
tx bitrate: 108.0 MBit/s MCS 5 40MHz
rx bitrate: 81.0 MBit/s MCS 4 40MHz
expected throughput: 37.994Mbps
authorized: yes
authenticated: yes
associated: yes
preamble: long
WMM/WME: yes
MFP: no
TDLS peer: no
DTIM period: 2
beacon interval:8192
short slot time:yes
connected time: 219027 seconds
root@---:~# uptime
05:38:23 up 2 days, 12:50, load average: 0.03, 0.02, 0.04
160NL WDS-AP & Sta up a bit over 5 days with this build.
After I set key renewal to 0 worked perfectly .... Absolutely no dropouts
Just now updated both to 31221 what a pain in the butt -- both went blinky on me so had to TFTP it.....nice that they come back all good with same conf
Wireless dropouts were common for me too with this 160NL, and exactly the same with the TP-Link, after a couple days wifi bandwidth drops very low down and eventually devices have no network access at all
Was using a scheduled reboot at 5am as a workaround _________________ TPLINK TL-WR2543ND (5GHz)
WRT160NL (2.4GHz)
2 days in and already had to reboot router and change wireless channels and restart wifi to fix a low signal problem
Never had stable wifi with the 160NL, throughout dozens of builds and many years of use
Similar issue with the TP-Link although not as pronounced or regular
Been talking to the better half and think we're gonna invest in something with a lot more grunt in the next few weeks
Trying to keep these old low spec routers providing the needs of 2017 networking with 10's of bandwidth hungry wireless devices connected is becoming more of a chore than fun, seems like every day I have to figure out yet another reason something isn't working _________________ TPLINK TL-WR2543ND (5GHz)
WRT160NL (2.4GHz)
2 days in and already had to reboot router and change wireless channels and restart wifi to fix a low signal problem
Never had stable wifi with the 160NL, throughout dozens of builds and many years of use
Similar issue with the TP-Link although not as pronounced or regular
Been talking to the better half and think we're gonna invest in something with a lot more grunt in the next few weeks
Trying to keep these old low spec routers providing the needs of 2017 networking with 10's of bandwidth hungry wireless devices connected is becoming more of a chore than fun, seems like every day I have to figure out yet another reason something isn't working
Sounds like you are loading it up ... There was a time just couple years back mine would do as main router for me but it wouldn't do so now
Too many wireless devices all screaming for their part of the internet.
I did use the 160nl for long time was a WAP w/5-6 clients without problems.
Have not had any further problems with the 160nl WDS bridged.
They are still good for some things .... admittedly the SAMBA share on it is snail speed compared to the ea8500.
2 days in and already had to reboot router and change wireless channels and restart wifi to fix a low signal problem
Never had stable wifi with the 160NL, throughout dozens of builds and many years of use
Similar issue with the TP-Link although not as pronounced or regular
Been talking to the better half and think we're gonna invest in something with a lot more grunt in the next few weeks
Trying to keep these old low spec routers providing the needs of 2017 networking with 10's of bandwidth hungry wireless devices connected is becoming more of a chore than fun, seems like every day I have to figure out yet another reason something isn't working
Sounds like you are loading it up ... There was a time just couple years back mine would do as main router for me but it wouldn't do so now
Too many wireless devices all screaming for their part of the internet.
I did use the 160nl for long time was a WAP w/5-6 clients without problems.
Have not had any further problems with the 160nl WDS bridged.
They are still good for some things .... admittedly the SAMBA share on it is snail speed compared to the ea8500.
Yea we seem to accumulate an ever growing number of wireless gadgets
SAMBA on the 160NL and the TP-Link both seem to be maxed at 9MB/s - I assumed it was the 100mbps ports of the 160NL causing it, but the TP-Link is gigabit and same speed _________________ TPLINK TL-WR2543ND (5GHz)
WRT160NL (2.4GHz)
How do I first time flash WRT160NL? I've had experience with Linksys E4200, and following the standard guide here, there was needed an initial trailed flash and then any K26 build was good.
How does this work for WRT160NL? It runs standard factory Linksys firmware. Do I simply flash wrt160nl-firmware.bin from the OP to it and that's that?
What about other builds, e.g. from here ftp://ftp.dd-wrt.com/betas/2017? There's always a dir with WRT160NL bin. Can I simply use any of those in the future?
How do I first time flash WRT160NL? I've had experience with Linksys E4200, and following the standard guide here, there was needed an initial trailed flash and then any K26 build was good.
How does this work for WRT160NL? It runs standard factory Linksys firmware. Do I simply flash wrt160nl-firmware.bin from the OP to it and that's that?
What about other builds, e.g. from here ftp://ftp.dd-wrt.com/betas/2017? There's always a dir with WRT160NL bin. Can I simply use any of those in the future?
The latest public release will work but many prior to that have firmware size too big and will not install.
Also these routers are fussy about lots things. You should reset it before update and it may still go to
a blinky power light after installing some builds. This is nothing to worry about -- I have 3 and
have never bricked one or ever had to open one up. If after several minutes you still have blinky power light
just set static IP on your computer to 192.168.1.7 and TFTP the wrt160nl-firmware.bin to it at 192.168.1.1
It can take several minutes after TFTP before firmware will completly load -- power light will quit blinking then.
Noticed installing 31277 from a reset 160NL all went well but the webif never loaded. Had to unplug for 20 seconds
plug back and all is good --- like I said they can be fussy
