Posted: Wed Mar 07, 2018 18:37 Post subject: Re: New Build 35244 (BS): 03-05-2018-r35244
Router/Version: Asus WL-520GU
Firmware: DD-WRT v3.0-r35244 std (03/05/18)
Kernel: Linux 2.4.37 #48448 Mon Mar 5 06:37:12 CET 2018 mips
Previous: DD-WRT v3.0-r34929 std (02/12/18)
Mode/Status: WAN-DHCP
Reset: no
Issues/Errors: Internet stops every 24h, in Status-WAN Remaining Lease Time shows 0 days 00:00:00, once I click on "DHCP Renew" button next to it, everything works fine for another 24 hours. Same issue was in previous several firmware releases.
Joined: 13 Jun 2006 Posts: 1608 Location: SE Michigan USA
Posted: Wed Mar 07, 2018 21:46 Post subject: Re: New Build 35244 (BS): 03-05-2018-r35244
workflow wrote:
Router/Version: Asus WL-520GU
Firmware: DD-WRT v3.0-r35244 std (03/05/1
Kernel: Linux 2.4.37 #48448 Mon Mar 5 06:37:12 CET 2018 mips
Previous: DD-WRT v3.0-r34929 std (02/12/1
Mode/Status: WAN-DHCP
Reset: no
Issues/Errors: Internet stops every 24h, in Status-WAN Remaining Lease Time shows 0 days 00:00:00, once I click on "DHCP Renew" button next to it, everything works fine for another 24 hours. Same issue was in previous several firmware releases.
This could be an issue with your ISP. Why things happen is 1/2 through the dhcp lease the client, router in this case, requests a renewal. Normally the ISP dhcp server would see the request and renew the lease so you should never have a situation like you describe with a correct working dhcp server. At the end of the lease that happens again. It would appear the ISP is not honoring those renewal requests. Potentially a dd-wrt issue, but there should be lots of folks, me included with this issue. _________________ Unifi Security Gateway:Unifi Firmware Netgear r7800:Voxel Firmware Modem:Netgear CM500V voice and Data. ISP:Comcast tutorial for flashing "WRT" series: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=287813 DD-WRT Installation, Upgrade & Basic Setup–Cliff Notes: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=311117 Kong DD-WRT Config Tutorial: http://www.instructables.com/id/Install-and-Configure-a-DD-WRT-Kong-Router/ I tried to be normal once. Worst 2 minutes ever.
Last edited by myersw on Fri Mar 09, 2018 20:46; edited 2 times in total
Joined: 05 Mar 2018 Posts: 21 Location: In your Heart
Posted: Thu Mar 08, 2018 0:52 Post subject:
jwh7 wrote:
The E1500 is identical (besides a minor SoC revision; BCM5357 rev B0 vs C0) and both use nv64k firmware. I've been running this build for two days.
Edit: now updated a E2500 (nv60k) too...
Router/Version: Linksys E2500
Firmware: DD-WRT v3.0-r35244 mega ( 03/05/18 )
Kernel: Linux 3.10.108-dd #17976 Mon Mar 5 14:32:56 CET 2018 mips
Previous: 33772 k3x
Mode/Status: Gateway router, inside my LAN
Reset: no
Issues/Errors: only up 10min
Which version do I have to install, to use it as a Client Bridge?
k26 or k3x works fine for that. The nv64k build is all you need, if its available (otherwise use the trailed build).
Also updated my other E2500...
Router/Version: Linksys E2500
Firmware: DD-WRT v3.0-r35244 mega ( 03/05/18 )
Kernel: Linux 3.10.108-dd #17976 Mon Mar 5 14:32:56 CET 2018 mips
Previous: 33772 k3x
Mode/Status: AP
Reset: reset just prior to update, to switch from GW to AP
Issues/Errors: only up 10min _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
If the cat was wearing a feathered scarf and sunglasses, maybe I'd give you some props...
E900 wrote:
Firmware: DD-WRT v3.0-r35244 mega ( 03/05/18 )
Previous: mini variation v24 PreSP2 [Beta] Build 21061
See that was easy
And since I'm here...
Router/Version: Belkin F7D8302
Firmware: DD-WRT v3.0-r35244 mega ( 03/05/18 )
Kernel: Linux 3.10.108-dd #17976 Mon Mar 5 14:32:56 CET 2018 mips
Previous: 34929 k3x
Mode/Status: GW router
Reset: no
Issues/Errors: up 30min
Updated via GUI this time; before I had to wget/write it from telnet. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Joined: 31 Jan 2013 Posts: 9 Location: Ingolstadt, Germany
Posted: Thu Mar 08, 2018 15:47 Post subject:
Router: WRT320N
Firmware: DD-WRT v3.0-r35244 mega (03/05/18)
Kernel: Linux 3.10.108-dd #17976 Mon Mar 5 14:32:56 CET 2018 mips
Previous: DD-WRT v3.0-r33772 mega
Status: working
Reset: no
Errors: none
Posted: Fri Mar 09, 2018 17:34 Post subject: r35244
Router/Version: ASUS AC87U Firmware: DD-WRT v3.0-r35244 std (03/05/18 ) Kernel: Linux 4.4.120 #2692 SMP Mon Mar 5 08:49:09 CET 2018 armv7l Previous: 2018-01-31-r34777 Mode/Status: something is wrong Reset: no Issues/Errors: AP: wrong IP of 5GHz client, NTP still not working
On WL1 (5GHz), this AP shows a WRONG IP of a client:
The AP (ASUS AC87, DNSMASQ is on) shows in Status/LAN client has .193, but I can reach it's GUI on .190 only. IP of client (Buffalo D1800, CB, also on r35244) is set to .190 (fixed).
When the CB is rebooting, .190 and .193 are both shown on the AP for a short while, same MACs. Only .193 remains, as .190 disappears.
IPs on WL0 (2.4GHz) are all shown OK.
This might be an older issue (not noticed before), as downgrading both units 1 or 2 earlier releases doesn't help.
Router/Version: Asus RT-AC68U B1
Firmware: DD-WRT v3.0-r35244 std (03/05/18 )
Kernel: Linux 4.4.120 #2685 SMP Mon Mar 5 08:03:45 CET 2018 armv7l
Previous: DD-WRT v3.0-r35034 std (02/17/18 )
Mode/Status: Gateway/OK
Reset: No
Issues/Errors: None that I am aware of. Network is mostly wired and wifi is not extensively tested but no apparent issues.
Uptime: 4 days
Note: After roughly four days of uptime I did get an interruption in service. I suspect it was the router, as my ISP was unaware of any service interruptions in my area. Power cycling my network eventually fixed it. If I were to finger a culprit I would probably choose the QoS which has in the past been somewhat flaky. _________________ Netgear XR500
Rogers Ignite Cable
150mbps down/15mbps up
Last edited by Drek on Sun Mar 11, 2018 17:01; edited 1 time in total