Joined: 08 May 2018 Posts: 14126 Location: Texas, USA
Posted: Sat May 12, 2018 19:27 Post subject:
Router: Linksys E4200
Firmware: DD-WRT v3.0-r35916 mega - 05/11/18
Kernel: Linux 3.10.108-dd #19122 Fri May 11 18:24:52 CEST 2018 mips
Status: OK
Reset: No
Errors:
Here's something I noticed. Disabling wireless access to the webGUI has NO effect. Is this a known problem? Also have still been having weird issues with DNSMasq, but I think the problem is more related to the garbage Windows IP stack.... who knows.
EDIT: Things seemed to have settled out now. Uptime around 6 hours.
Last edited by kernel-panic69 on Sun May 13, 2018 2:27; edited 1 time in total
Router/Version: RT-AC66U A1
....
Issues/Errors: Yes, need the following command(s) for 5 Ghz connection and NTP time sync
sleep 5; stopservice lan; startservice lan;
sleep 15; ntpclient us.pool.ntp.org;
Router/Version: E4200 V1
.....
Issues/Errors: Yes, need the following command(s) for 5 Ghz connection and NTP time sync
sleep 5; stopservice lan; startservice lan;
sleep 15; ntpclient us.pool.ntp.org;
Smells like wrong timing to start services lan and ntpclient for the 5GHz radio in both routers... maybe a delayed start could avoid the problem?
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r35916 std ( 05/11/18 )
Kernel: Linux 4.4.131 #3073 SMP Mon May 7 08:49:26 CEST 2018 armv7l
Previous: r35898
Mode/Status: Gateway / working
Reset: no
Issues/Errors: Speed tests are worse than usual and bufferbloat is a B or C rather than my usual A or A+... maybe the test site, will try again later.
Uptime: 35m
Temperatures: CPU 62.5 °C / WL0 45.2 °C / WL1 49.0 °C
Aaaaaand, I'm a dumbass... slow speeds (above) were caused by VPN client being active.
Router: Cisco Linksys EA2700
Firmware: DD-WRT v3.0-r35916 (05/11/1
Kernel: Linux 3.10.108-dd #19110 Fri May 11 18:13:34 CEST 2018 mips
Status: running but buggy, AP mode for wireless, ethernet WAN
Reset: yes when flash
Errors: time service ok, wifi ssid connections ok, running "cat /proc/mtd" in Administration -> Commands worked fine like the case of kernel-panic69, but WAN connections from Wifi still hang intermittently whatever TCP or UDP, only packets sent but no responses from router, so I have to disconnect the wifi from my phone and reconnect again so wifi TCP response again. It never happens in wired LAN ethernet connects, wired ethernet always work fine.
Wifi TCP hang whatever Facebook, Whatsapp, Chrome, Line, Wechat, Instagram, Youtube, or even just Google play store...... planning for falling back to the most stabler build 10-20-2017-r33555 of 2017
Oddly enough, my router doesn't stay on 24/7 and powering up, all settings lost. Re-configured, step-by-step, noticed some settings didn't 'take' between saving/applying and reboots and such. Don't know if it was a random glitch or what with 35916. Anyway, here, hold my beer....
Router/Version: Linksys EA6500V2
Firmware: DD-WRT v3.0-r35916 std ( 05/11/18 )
Kernel: Linux 4.4.131 #3073 SMP Mon May 7 08:49:26 CEST 2018 armv7l
Mode: AP/Router/Fprt Forwarding
Issues: None so Far for 1 day
Joined: 23 Jan 2008 Posts: 50 Location: Ulm, Germany
Posted: Sun May 13, 2018 22:59 Post subject: Re: New BS build available for test: r35916 dated 05/11/18
Router: Netgear Nighthawk R7000P
Firmware: DD-WRT v3.0-r35916 std, Release: 05/11/18
Kernel: Linux wl-ap-eg 4.4.131 #3078 SMP Fri May 11 13:38:35 CEST 2018 armv7l DD-WRT
Status: Came up successfully, runs stable. 5 GHz WLAN starts to ignore broadcasts after about 2 hours of operation.
Reset: Tried NVRAM reset via Web GUI, didn't solve the problem.
Errors: 5 GHz WLAN ignores broadcasts after about 2 hours of operation
Details:
I have set up the R7000P in client bridge mode using its 5 GHz WLAN module. The access point the R7000P connects to is a Netgear R7000 which is also running DD-WRT and serving other clients (e.g. Linksys WRT600N). In this scenario, the R7000P (and only the R7000P, the other clients are not affected) seems to start ignoring incoming packets to the broadcast address FF:FF:FF:FF:FF:FF on the 5 GHz device after about two errors of operation. This can be clearly observerd by using "tcpdump -i any".
This problem breaks ARP and DHCP. A DHCP client, which connects to the 2.4 GHz device of the R7000P, or a DHCP client, which connects via wire to the R7000P, doesn't get an IP address.
I suppose that the driver for "eth2" (wl0: May 1 2017 12:43:53 version 10.10.122.301 (r658909) FWID 01-1ebebd8a) is the cause of the problem. I tried earilier versions of KONG and BS builds (which come with the same driver) and discovered the same problem. There are no eth2-related messages in the dmesg log. Especially, there is no log when the problem starts to occur.
Resetting the R7000P to factory defaults didn't help.
It is definitely not a "packet loss" problem caused by bad radio channel conditions. Unicasts come through perfectly. The problem is independent from the channel number.
After reconnecting the 5 GHz link, the problem is gone for another 2 hours
Joined: 26 Mar 2013 Posts: 1855 Location: Hung Hom, Hong Kong
Posted: Tue May 15, 2018 3:18 Post subject: Re: New Build 35927 (BS): 05-13-2018-r35927
kernel-panic69 wrote:
Oddly enough, my router doesn't stay on 24/7 and powering up, all settings lost. Re-configured, step-by-step, noticed some settings didn't 'take' between saving/applying and reboots and such. Don't know if it was a random glitch or what with 35916.
I noticed hitting <Apply> or <Save Settings> sometimes might cause the WEBUI to hang. Hadn't figured out a pattern to report.
Quote:
Anyway, here, hold my beer....
OK, Master (drinking my cup of green tea). _________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
Joined: 08 May 2018 Posts: 14126 Location: Texas, USA
Posted: Tue May 15, 2018 15:11 Post subject: Re: New Build 35927 (BS): 05-13-2018-r35927
mwchang wrote:
kernel-panic69 wrote:
Oddly enough, my router doesn't stay on 24/7 and powering up, all settings lost. Re-configured, step-by-step, noticed some settings didn't 'take' between saving/applying and reboots and such. Don't know if it was a random glitch or what with 35916.
I noticed hitting <Apply> or <Save Settings> sometimes might cause the WEBUI to hang. Hadn't figured out a pattern to report.
Quote:
Anyway, here, hold my beer....
OK, Master (drinking my cup of green tea).
s/beer/coffee. It's rare that I drink adult beverages 35927 seems to be much more stable than 35916. 12-hour uptime yesterday with no incidents. Good to know that the webGUI hang is something to keep a lookout for, although I haven't seen any issues with it on the latest BS build.
Joined: 06 Jun 2006 Posts: 7463 Location: Dresden, Germany
Posted: Wed May 16, 2018 5:37 Post subject:
i really think about removing these fake bridge modes. all newer broadcom drivers using the dhd driver do not support these bridge modes anymore. they may crash. they may not work. sorry. i have to ignore this. use client modes, maybe use the eoip tunnel feature to build your real bridges. fake bridges are shit anyway and they do not have any arp support. they just simulate the behaviour. realize finally that this is no wds mode. it has no real bridge behaviour. this is also not possible without wds _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
i really think about removing these fake bridge modes. all newer broadcom drivers using the dhd driver do not support these bridge modes anymore. they may crash. they may not work. sorry. i have to ignore this. use client modes, maybe use the eoip tunnel feature to build your real bridges. fake bridges are shit anyway and they do not have any arp support. they just simulate the behaviour. realize finally that this is no wds mode. it has no real bridge behaviour. this is also not possible without wds
thanks for the comment BrainSlayer, have you tested WDS lately on ARM? i have not been successful in a working WDS connection between R6300v2 and R7000 (both ARM).
Posted: Wed May 16, 2018 14:44 Post subject: EA6350 v2
Router: Linksys EA6350 v2
Firmware: DD-WRT v3.0-r35916 std (05/11/18)
Kernel: Linux 4.4.131 #3073 SMP Mon May 7 08:49:26 CEST 2018 armv7l
Status: no issue for 2 days
Reset: yes
Errors: before reseting config, LAN didn't work config (PC couldn't get IP), but WAN and WLAN were ok. After reseting config then everything are good, probably old config was corrupted because the router auto reverted to stock firmware in the first few attempts to flash dd-wrt.
Given the amount of pollution on Earth, it's hard to say whether these drinks are safe for consumption or not. Both green tea and beer might have insecticide and weedicide.
Back to our usual DD-WRT testing ...
_________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!