Upgraded from r32805M to this version and the uptime is 4 days now.
The only observed difference on my system is the wl0.1 and wl1.1 Unbridged networks. DHCP works again with them on r33010M.
But I don't know what version it had started to happen that DHCP did not work on wl1.1 (2.4G guest WiFi network) since there is no visitor to use wl1.1 until 8/10 at my home recently. I did have observed wl0.1 (5G guest WiFi network) was very unstable and hard to get a IP address -- used by my wife's Sony Z3+ phone.
wl0 and wl1 are always ok with both versions although SSID is not broadcasted and MAC filter is applied on these 2 bridged networks. _________________ Buffalo WZR-1750DHP
Router: Netgear R7000
Firmware: DD-WRT v3.0-r33010M kongac (08/09/17)
Kernel: Linux 4.4.80 #422 SMP Wed Aug 9 20:13:10 CEST 2017 armv7l
Upgraded: from 33000 via ddup --flash-latest
Reset: No
Status: Working
Errors: None
Up and running smoothly for 5+ days
PPPoE with SFE disabled, LAN DHCP with static leases, Qos (HTB, FQ_CODEL), AP mode 2.4GHz and 5GHz, USB storage.
Router: Netgear R7000
Firmware: DD-WRT v3.0-r33010M kongac (08/09/17)
Kernel: Linux 4.4.80 #422 SMP Wed Aug 9 20:13:10 CEST 2017 armv7l
Upgraded: from 33000 via ddup --flash-latest
Reset: Yes, gui install with reset, nvram erase, power off power on
Status: Working
Errors: None
Just got another internet service provider today and man oh man its fast. Had to turn on SFE because a stock clocked R7000 was only giving me about 350-400. After SFE was turned on (see attachment)
I don't have any other service outside of the basic settings. Is there a reason no to turn SFE on? I read that there are issues with QOS with SFE and possibly PBR but since I don't use any of those, is there a reason not to have it on? Can anyone report if its buggy or not? I only have had the router loaded with this firmware for like 30 mins and it seems fine for now.
Posted: Thu Aug 17, 2017 15:07 Post subject: Kong's DD-WRT test build 33010M - 2017/08/09 results
Firmware: DD-WRT v3.0-r33010M kongac (08/09/2017)
Kernel: 4.4.80
Status: Working
Reset: No, dirty
Errors: No errors per-se but…
I flashed this version as an upgrade yesterday. So far, everything seems to be working just fine — I am particularly delighted that OpenVPN seems (so far!) solid.
The OpenVPN report window at status/OpenVPN is blank, however. I have tried management localhost 5001, 14, and 16 in the custom code window of the OpenVPN GUI but no luck.
Has anyone else gotten this to work and if so how?
Joined: 10 Aug 2015 Posts: 32 Location: Nashville, TN
Posted: Fri Aug 18, 2017 11:18 Post subject:
I don't have the need for SFE since I only have 150mbps service, but I have have been using for a long time a nicely-tuned QOS using HTB and FQ_Codel to almost eliminate Bufferbloat and achieve a nice quality connection. I think DD-WRT's Bufferbloat solution becomes more necessary to have now that DOCSIS 3.1 and fiber connections are becoming more common.
I have turned on SFE briefly over the last few builds just to see how it would behave, and all I can say is that my Bufferbloat went through the roof with 300-400ms latency, and both upstream and downstream tests were very erratic so I turned it off, again since I don't have a need for it. Not sure of any current bugs, but there have been.
Using a Buffalo WZR-1750DHP
Kloze wrote:
Router: Netgear R7000
Firmware: DD-WRT v3.0-r33010M kongac (08/09/17)
Kernel: Linux 4.4.80 #422 SMP Wed Aug 9 20:13:10 CEST 2017 armv7l
Upgraded: from 33000 via ddup --flash-latest
Reset: Yes, gui install with reset, nvram erase, power off power on
Status: Working
Errors: None
Just got another internet service provider today and man oh man its fast. Had to turn on SFE because a stock clocked R7000 was only giving me about 350-400. After SFE was turned on (see attachment)
I don't have any other service outside of the basic settings. Is there a reason no to turn SFE on? I read that there are issues with QOS with SFE and possibly PBR but since I don't use any of those, is there a reason not to have it on? Can anyone report if its buggy or not? I only have had the router loaded with this firmware for like 30 mins and it seems fine for now.
Route: RT-AC68U
previous version: 32170M
Running since it came out without any issues.
I noticed that in the syslog I'm getting the following error all the times:
user.info : Maybe udhcpd had died, we need to re-exec it
any idea? _________________ Netgear R9000 main router
RAX80 as AP
