Notes: 1. SFE accelerated NAT is in 33006+ builds but only in kernel 3.2 and newer 2. 'KRACK' vulnerability fixes were completed in r33678 for Broadcom, including k26 (33655) & k24 (33656); use 33772 or later.
3. Bridge modes on k4.4 devices may sometimes work in some configurations in certain builds but are not supported by the bcmdhd driver. Use client or repeater instead as WDS doesn't work with Broadcom ARM either (see Issues below).
4. PBR/UDP with SFE working again since r40513 (see 6729)
5. CAKE scheduler changes "completed" with r41057 (see 5796) & FQ_CODEL_FAST with r41027 (reset first!)
6. Reset button was broken in 40571; fixed in build 40750.
7. New Broadcom build option for 8MB+ K2.x devices (limited currently):
broadcom_K3X_mipsel32r1 [BS has tested on a WRT600N v1.1]
Issues, observations, and/or workarounds reported: 1.Trendnet 81*DRU models are missing factory-to-flash 2.DNScrypt is mostly only using v2 protocols now, but requires Golang that DD can't use:6246 3.WDS does not work on Broadcom ARM devices (only MIPS<->MIPS) 4.K2.6 builds are broken since 38253(?) (GUI issues):6538 5.VAPs not working at boot; workaround startup command:
sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas
This appears fixed (only for unbridged VAPs?) with r40564:40566...
Important: if reporting any issues, provide applicable info (GUI syslog, `dmesg`, `cat /var/log/messages`, etc.)
Or put into SVN ticket. For firewall issues, also provide "iptables" info (`iptables -L`, `iptables -t nat -L`, & the /tmp/.ipt file).
Template to copy (after "Code:") for posting issues, be sure to include the mode in use (gateway, AP, CB, etc.):
WARNING:This thread is to report on flashing this experimental test build, providing important info for both developers and users. Always state your hardware model, version, mode (e.g. Repeater) and SPECIFIC build (e.g. 33555_NEWD-2_K3.x_mega-nv64k.bin). Please avoid discussions and create a new thread to discuss specific problems or questions, as this thread is for reporting, not support. Posts may be deleted or moved to keep this thread manageable and useful. If you don't understand the risks or what to flash and how, with a means of recovery if it bricks, do NOT flash this experimental test build.
Linksys E2500
DD-WRT v3.0-r41586 mega (11/21/19)
Linux 3.10.108-d8 #480 Thu Nov 21 16:56:40 +04 2019 mips
[dd-wrt.v24-41586_NEWD-2_K3.x_mega.bin]
Reset r41379 and GUI install over it.
All basic wired & wireless working ok.
Linksys E1200 v2
DD-WRT v3.0-r41586 mega (11/21/19)
Linux 3.10.108-d8 #480 Thu Nov 21 16:56:40 +04 2019 mips
[dd-wrt.v24-41586_NEWD-2_K3.x_mega-nv64k.bin]
Reset r33555 and GUI install over it.
All basic wired & wireless working ok.
yea, this unit takes a power cycle if you do a reset
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Fri Nov 22, 2019 22:15 Post subject: Cisco Linksys E4200 v1
Router Model / Version: Cisco Linksys E4200 v1
File: dd-wrt.v24-41586_NEWD-2_K3.x_mega-e4200.bin
Firmware: DD-WRT v3.0-r41586 mega (11/21/19)
Kernel: Linux 3.10.108-d8 #480 Thu Nov 21 16:56:40 +04 2019 mips
Previous: DD-WRT v3.0-r41580 mega (11/20/19)
Reset: No
Mode: Gateway / AP - QoS (HFSC+FQ_CODEL_FAST)
Uptime: ~ 4:25
Status: OK
Issues / Errors: Something I noticed in the serial console output during post-flash reboot:
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r41586 std (11/21/19)
Kernel: Linux 4.4.202 #297 SMP Wed Nov 20 11:06:18 +04 2019 armv7l
Previous: r41517
Mode/Status: Gateway / working
Reset: no
Issues/Errors: Working well so far.
Uptime: 8hrs 13min
Temperatures: CPU 66.4 °C / WL0 47.5 °C / WL1 53.2 °C
Router: Netgear R7000P
Kernel: Linux 4.4.202 #302 SMP Thu Nov 21 12:51:14 +04 2019 armv7l
Mode: Gateway / AP / JFFS2 / Unbound / QoS(HTB FQ_CODEL_FAST) ISP Speed 100 Mbps down 10 Mbps up
Status: now up 2+ days / all still seems well
Last edited by tinkeruntilitworks on Wed Dec 04, 2019 17:29; edited 10 times in total
Router/Version: WNDR4500v2
Mode: AP/switch
File: DD-WRT v3.0-r41586 giga (11/21/19)
Kernel: Linux 3.10.108-d8 #464 Thu Nov 21 16:42:59 +04 2019 mips
Status: Working so far
Temps: WL0 42.5 °C / WL1 43.2 °C
Previous: 41517
Uptime: 22:41
The first flash went well and I didn't have to reset to defaults. I did get a head of myself and ended up flashing the build for WRT54GSv1 on this and doing a cve boot recovery oops. So far stable. I changed the gtk timing back to default for testing.
Router/Version: RT-N66R
Mode: AP/Switch
File: DD-WRT v3.0-r41586 big (11/21/19)
Kernel: Linux 3.10.108-d8 #476 Thu Nov 21 16:52:54 +04 2019 mips
Status: Working (issues below)
Temps: WL0 50.6 °C / WL1 49.3 °C
Previous: 41517
Uptime: 8:42
Only issue with flashing was I had to reboot in order to get the webgui to work right. I didn't copy the message bu it was along these lines "Settings have changed the router will now refresh this page". Also, when I changed the gtk timing on this router I had to reboot to get the webgui back (same approximate message as above). So far it is working well. Time will tell.
I have not updated my WRT54GSv1 yet, it has been up for 9 days with no syslog spam on build 41517.
(anyone have a posting time out when crafting a post that takes a min or two?)
.:EDIT:.
Reviewing the logs I also found these messages in all as indicated.
Code:
httpd : Request Error Code 404: File apple-touch-icon-120x120.png not found. WNDR4500v2 - RT-N66R
httpd : Request Error Code 404: File apple-touch-icon-precomposed.png not found. WNDR4500v2 - RT-N66R
httpd : Request Error Code 404: File apple-touch-icon.png not found. WNDR4500v2 - RT-N66R
httpd : Request Error Code 404: File favicon.ico not found. WNDR4500v2 - RT-N66R - WRT54GSv1
br0: received packet on eth2 with own address as source address WNDR4500v2 - RT-N66R
Router/Version: Asus RT-AC68U rev C1
Mode: Gateway / AP
Reset: No, flashed from command line
Status: Seems to work well after a few hours uptime. Jffs, Samba and Openvpn fully functional _________________ Netgear R7000 on Build 55109
Asus AC-AC68U rev. C1 (AP) on Build 55109
Asus AC-68U rev. A1 on Build 54604
Asus AC-68U rev. A1 on Build 53339
Also, when I changed the gtk timing on this router I had to reboot to get the webgui back
Rekey issue still present on the RT-N66R. Any change to the gtk settings lock up the router and requires a power cycle. A work around for this is to save the settings and reboot the router through the admin section.
.:EDIT:.
I tried to change the gtk settings, saving them, then disabling the wireless radios in an attempt to not reboot the router... nope locked up the router still power cycle required.
Over the weekend my work test router E1200v2 showed the rekey issue since it was flashed on Friday late in the afternoon. This log message just appeared on my WNDR4500v2.
Code:
timer : There are no events in the queue - timer not reset.timer : There are no events in the queue - timer not reset.timer : There are no events in the queue - timer not reset.timer : There are no events in the queue - timer not reset.timer : There are no events in the queue - timer not reset.timer : There are no events in the queue - timer not reset.timer : There are no events in the queue - timer not reset.timer : There are no events in the queue - timer not reset.timer : There are no events in the queue - timer not reset.timer : There are no events in the queue - timer not reset.timer : There are no events in the queue - timer not reset.timer : There are no events in the queue - timer not reset.timer : There are no events in the queue - timer not reset.timer : There are no events in the queue - timer not reset.timer : There are no events in the queue - timer not reset.timer : There are no events in the queue - timer not reset.timer : There are no events in the queue - timer not reset.timer : There are no events in the queue - timer not reset.
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Tue Nov 26, 2019 1:01 Post subject:
It's not renewing GTK because the timer isn't reset. Do you have a bunch of the other associated syslog entries or did it run long enough to get to the reset entries? The only two workarounds are daily reboot or set the interval to 0 AFAIK. Seems like this ain't getting fixed anytime soon. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Do you have a bunch of the other associated syslog entries or did it run long enough to get to the reset entries?
It ran long enough to get these. The only associated entries only show up if the gtk timer is greater than 0. I was able to trip the bug by setting the gtk timer to 1. As soon as it rebooted it lost it in the serial prompt (too quick to catch the before lines). I do have 2 gigs of logs at work from the E1200v2 that did nothing but spam the bug error over the weekend to my syslog server... I'll see if I can find the before entries and if they might point to a possible fix.
Do you have a bunch of the other associated syslog entries or did it run long enough to get to the reset entries?
It ran long enough to get these. The only associated entries only show up if the gtk timer is greater than 0. I was able to trip the bug by setting the gtk timer to 1. As soon as it rebooted it lost it in the serial prompt (too quick to catch the before lines). I do have 2 gigs of logs at work from the E1200v2 that did nothing but spam the bug error over the weekend to my syslog server... I'll see if I can find the before entries and if they might point to a possible fix.
It is probably not the place where to discuss this but anyway, has anyone tried to figure out from which build on this gtk problem started? Would it be possible to set gtk timer to a very small value such that the problem occurs quite fast? If so, would it not be possible to investigate in which build this problem started and then look at the checkins between two builds to see what could be the cause of this?
-- presumably because BS can only fit samba3 there.