What I've found with recent Kong & BS builds for the R7000 is that VAP startup commands don't need to be used for an unbridged VAP. But if the VAP if bridged to ie br1, then the startup commands are still needed. Might be worth someone checking on BS builds to confirm tho...
mwchang wrote:
mrjcd wrote:
All three of the units --- same ol broadcom buggy VAP crap been there long time now.
VAP (all its functions) not fully start after an install or reboot.
Just some minor testing --- wired clients to 'Repeater' mode router is fine but wireless clients CANNOT connect to its VAP
until you 'Apply Settings' at ../Wireless_Basic.asp ...even though the VAP does broadcast after reboot.
and yea I know there is various startup commands you can use to make it work besides having to go into the webif but that ain't the point ---
This should be fixed
Someone in the Kong's new build said (again?) VAP was fixed, no work-around needed... is there a bridge to port it over? Meow...
Joined: 09 Nov 2014 Posts: 314 Location: Bakersfield, CA
Posted: Fri Jul 12, 2019 3:09 Post subject:
Router/Version: 2x Linksys E3000
Firmware: dd-wrt.v24-40260_NEWD-2_K3.x_mega-e3000.bin
Previous: dd-wrt.v24-40189_NEWD-2_K3.x_mega-e3000.bin
Kernel: Linux 3.10.108-d8 #25293 Tue Jul 9 15:39:01 CEST 2019 mips
Mode: Client Bridges, all settings not required turned off.
Status: Seem to be working quite well!
Router/Version: Linksys E1200v2
Firmware: dd-wrt.v24-40260_NEWD-2_K3.x_mega-e1200v2.bin
Previous: dd-wrt.v24-40189_NEWD-2_K3.x_mega-e1200v2.bin
Kernel: Linux 3.10.108-d8 #25293 Tue Jul 9 15:39:01 CEST 2019 mips
Mode: Client.
Status: Used for my Mom's work PC, but so far I haven't had any issues come back!
Note: SFE kills (makes it non working) the E1200v2. Didn't test on the E3000, but I spent hours before I figured out SFE doesn't work (it's enabled by default?) _________________ Deployed Routers:
Netgear R7800 - 1x build 46979
- Gateway (USB /w Entware, CAKE QoS)
Netgear R7000 - 3x build 46979
Router/Version: 2x Linksys E3000
Firmware: dd-wrt.v24-40260_NEWD-2_K3.x_mega-e3000.bin
Previous: dd-wrt.v24-40189_NEWD-2_K3.x_mega-e3000.bin
Kernel: Linux 3.10.108-d8 #25293 Tue Jul 9 15:39:01 CEST 2019 mips
Mode: Client Bridges, all settings not required turned off.
Status: Seem to be working quite well!
Router/Version: Linksys E1200v2
Firmware: dd-wrt.v24-40260_NEWD-2_K3.x_mega-e1200v2.bin
Previous: dd-wrt.v24-40189_NEWD-2_K3.x_mega-e1200v2.bin
Kernel: Linux 3.10.108-d8 #25293 Tue Jul 9 15:39:01 CEST 2019 mips
Mode: Client.
Status: Used for my Mom's work PC, but so far I haven't had any issues come back!
Note: SFE kills (makes it non working) the E1200v2. Didn't test on the E3000, but I spent hours before I figured out SFE doesn't work (it's enabled by default?)
You are not alone, and I've update that isuue and provide more info again, @kernel-panic69 agree this is still a serious issue for broadcom soc routers as well, and actually for a very long long time already (since a long time ago.... in a galaxy far.... far away....):
https://svn.dd-wrt.com/ticket/6668
I can't comprehend why a MacDonald restaurant just keep trying to make curry sushi and never give a f**k about their own hamburger taste like shit..... ¯\_(ツ)_/¯
What I've found with recent Kong & BS builds for the R7000 is that VAP startup commands don't need to be used for an unbridged VAP. But if the VAP if bridged to ie br1, then the startup commands are still needed. Might be worth someone checking on BS builds to confirm tho...
mwchang wrote:
mrjcd wrote:
All three of the units --- same ol broadcom buggy VAP crap been there long time now.
VAP (all its functions) not fully start after an install or reboot.
Just some minor testing --- wired clients to 'Repeater' mode router is fine but wireless clients CANNOT connect to its VAP
until you 'Apply Settings' at ../Wireless_Basic.asp ...even though the VAP does broadcast after reboot.
and yea I know there is various startup commands you can use to make it work besides having to go into the webif but that ain't the point ---
This should be fixed
Someone in the Kong's new build said (again?) VAP was fixed, no work-around needed... is there a bridge to port it over? Meow...
on the AC3200 I have a bridged VAP on a VLAN and it works fine on startup or reset without issuing the startup commands or doing it manually. _________________ ASUS RT-AC3200 - Deployed Client's site
ASUS RT-AC5200 - Merlin
ASUS RT-AX88U - Merlin
Router/Version: Netgear WNR3500L v2
File: dd-wrt.v24-40260_NEWD-2_K3.x_mega-WNR3500Lv2.chk
Kernel: Linux 3.10.108-d8 #25277 Tue Jul 9 15:22:36 CEST 2019 mips
Mode: Internet gateway and WIFI AP
Status: Work
Uptime: more than 24 hours
Generally my device working OK. I can't make configure in Basic -> Switch config tab. When I'm change options there and click save and apply settings button configuration back to default values, so I can't change network ports configuration.
Router have something problem cause I have UDP bad checksum one event in device log. IP from the world try operation on 1900 and 9815 port. I'm block this IP in iptables, block ports in port triggering. That problem isn't exist earlier. I think is some problem with security in this firmware build.
Router/Version: Netgear WNR3500L v2
File: dd-wrt.v24-40260_NEWD-2_K3.x_mega-WNR3500Lv2.chk
Kernel: Linux 3.10.108-d8 #25277 Tue Jul 9 15:22:36 CEST 2019 mips
Mode: Internet gateway and WIFI AP
Status: Work
Uptime: more than 24 hours
Generally my device working OK. I can't make configure in Basic -> Switch config tab. When I'm change options there and click save and apply settings button configuration back to default values, so I can't change network ports configuration.
Router have something problem cause I have UDP bad checksum one event in device log. IP from the world try operation on 1900 and 9815 port. I'm block this IP in iptables, block ports in port triggering. That problem isn't exist earlier. I think is some problem with security in this firmware build.
I'm sure the logfile(s) would help determine the problem, if it's in the firmware.
What I've found with recent Kong & BS builds for the R7000 is that VAP startup commands don't need to be used for an unbridged VAP. But if the VAP if bridged to ie br1, then the startup commands are still needed. Might be worth someone checking on BS builds to confirm tho...
mwchang wrote:
mrjcd wrote:
All three of the units --- same ol broadcom buggy VAP crap been there long time now.
VAP (all its functions) not fully start after an install or reboot.
Just some minor testing --- wired clients to 'Repeater' mode router is fine but wireless clients CANNOT connect to its VAP
until you 'Apply Settings' at ../Wireless_Basic.asp ...even though the VAP does broadcast after reboot.
and yea I know there is various startup commands you can use to make it work besides having to go into the webif but that ain't the point ---
This should be fixed
Someone in the Kong's new build said (again?) VAP was fixed, no work-around needed... is there a bridge to port it over? Meow...
Is this issue just affect router which manually added br1 br2 etc other than br0? Or this issue happens on the router with just the default br0 and no other bridges as well?
Router/Version: Netgear WNDR4000
File: dd-wrt.v24-40260_NEWD-2_K3.x_mega-nv64k.bin
Kernel: Linux netgearouter 3.10.108-d8 #25293 Tue Jul 9 15:39:01 CEST 2019 mips DD-WRT
Mode: Gateway
Status: generally ok, connection problems (see below)
Temperature: WL0 49.3 °C / WL1 49.8 °C
Uptime: 18 hours
Recently upgraded from a two-year-old r31690. GUI install, with reverting all settings. UI, NAT, 2.4/5, g/n modes work fine.
One major problem. After a few hours wi-fi client cannot get working network (icmp ping to router, tcp failed) while being connected to Wi-Fi. Reconnecting Wi-Fi (off/on) of the client helps. Seen on both interfaces (2.4/5 GHz). The only thing correlated with a bug is a lot of timer log entries:
Joined: 08 May 2018 Posts: 14125 Location: Texas, USA
Posted: Wed Jul 17, 2019 19:50 Post subject:
theirix wrote:
Router/Version: Netgear WNDR4000
File: dd-wrt.v24-40260_NEWD-2_K3.x_mega-nv64k.bin
Kernel: Linux netgearouter 3.10.108-d8 #25293 Tue Jul 9 15:39:01 CEST 2019 mips DD-WRT
Mode: Gateway
Status: generally ok, connection problems (see below)
Temperature: WL0 49.3 °C / WL1 49.8 °C
Uptime: 18 hours
Recently upgraded from a two-year-old r31690. GUI install, with reverting all settings. UI, NAT, 2.4/5, g/n modes work fine.
One major problem. After a few hours wi-fi client cannot get working network (icmp ping to router, tcp failed) while being connected to Wi-Fi. Reconnecting Wi-Fi (off/on) of the client helps. Seen on both interfaces (2.4/5 GHz). The only thing correlated with a bug is a lot of timer log entries:
BUT, you can also try setting your GTK renewal for 2.4 band to 3610 and the 5GHz band to 3620. I am currently at 22:35 uptime with no timer entries on 40352 with those settings that another user suggested: https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1170177#1170177
Router Model: TP-Link Archer C9v1 (BCM4709 1GHz & BCM4360)
Firmware: DD-WRT v3.0-r40260 std (07/09/19)
Kernel: Linux 4.4.184 #408 SMP PREEMPT Tue Jul 9 08:16:00 CEST 2019 armv7l
Status: 2.4 and 5 GHz WAPs for Edgerouter X, 2.4 Guest VAP (unbridged), switch for PC
Reset: No
Issues: Does not support both 2.4 and 5 GHz Guest VAPs on a bridge _________________ Linksys EA8500
Linksys EA6350v3
Edgerouter X
BUT, you can also try setting your GTK renewal for 2.4 band to 3610 and the 5GHz band to 3620. I am currently at 22:35 uptime with no timer entries on 40352 with those settings that another user suggested: https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1170177#1170177
Thanks for the idea! For the cleanroom experiment, I did a 30-30-30 reset, flashed a trailed build as suggested in WNDR4000 wiki and reconfigured router from the scratch. The problem was still here. Then I tried changing key renewal intervals. Problem is still here, 14h after reboot. I will post results if further tweaks like DTIM or SFE off will help.
Joined: 08 May 2018 Posts: 14125 Location: Texas, USA
Posted: Sun Jul 21, 2019 11:45 Post subject:
It took 3 days for the infamous user.info : timer : syslog message loop that breaks syslog creeped up for me on 40352. BUT, wi-fi never dropped. Part of it was putting my Android phone on the 2.4 band and leaving everything else on the 5GHz band. I haven't tested changing DTIM on the 2.4 band yet, but rebooting once every 3 days isn't nearly as bad as rebooting a dozen times a day. There is also this option, which is a watchdog script from lazardo: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316635 ... I still haven't tried testing it personally but you can probably check it out.
Joined: 17 Apr 2014 Posts: 135 Location: SF Bay Area
Posted: Sun Jul 21, 2019 19:23 Post subject:
kernel-panic69 wrote:
It took 3 days for the infamous user.info : timer : syslog message
...
watchdog script from lazardo: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316635 ... I still haven't tried testing it personally but you can probably check it out.
Update: 'do' loop corrected.
The original script has been simplified here (untested):
Code:
#!/bin/sh
# watchdog for post-KRACK, Broadcom-based K3x nas rekey/timer hang+crash
# new version for 2019
##########
# CAUTION: check/adjust these for your router
PIDS="/tmp/nas.wl0lan.pid /tmp/nas.wl1lan.pid"