New Build 40260: BS 07-09-2019-r40260

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Goto page Previous  1, 2, 3  Next
Author Message
tinkeruntilitworks
DD-WRT User


Joined: 21 May 2019
Posts: 118

PostPosted: Thu Jul 11, 2019 19:16    Post subject: Reply with quote
Router/Version: Netgear R7000P
Firmware: DD-WRT v3.0-r40260 std (07/09/19)
Kernel: Linux 4.4.184 #411 SMP PREEMPT Tue Jul 9 08:29:23 CEST 2019 armv7l
Mode: Gateway/AP
Status: appears to be running well
Sponsor
ninjadawg
DD-WRT Novice


Joined: 18 Feb 2019
Posts: 26

PostPosted: Fri Jul 12, 2019 0:14    Post subject: Reply with quote
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
Rolling Eyes

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...

New Kong's DD-WRT test build 40270M 2019-07-11
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320460

SinCalChewy
DD-WRT User


Joined: 09 Nov 2014
Posts: 293
Location: Bakersfield, CA

PostPosted: Fri Jul 12, 2019 3:09    Post subject: Reply with quote
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! Smile

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 R7000 - 3x Kong's 40270M (Gateway: USB /w Entware, Stubby, DoT & DoH, QoS)
Linksys E3000 - 2x build 41218M (Client Bridges)
Linksys E900 - 1x build 40723M (Work Client)

Spares/Backups/Collection:
Too many to list. I have old routers, bricked routers, weird routers. You name it.
parco
DD-WRT User


Joined: 10 Sep 2017
Posts: 92

PostPosted: Fri Jul 12, 2019 8:44    Post subject: Reply with quote
SinCalChewy wrote:
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! Smile

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..... Rolling Eyes Confused ¯\_(ツ)_/¯
mbze430
DD-WRT User


Joined: 14 May 2012
Posts: 239

PostPosted: Fri Jul 12, 2019 16:27    Post subject: Reply with quote
ninjadawg wrote:
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
Rolling Eyes

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...

New Kong's DD-WRT test build 40270M 2019-07-11
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320460



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
thommy181
DD-WRT Novice


Joined: 16 Mar 2019
Posts: 30
Location: Szczecin, Poland EU

PostPosted: Fri Jul 12, 2019 19:04    Post subject: Netgear WNR3500L v2 Reply with quote
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.
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 2015
Location: Texas, USA

PostPosted: Fri Jul 12, 2019 20:16    Post subject: Re: Netgear WNR3500L v2 Reply with quote
thommy181 wrote:
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. Cool
parco
DD-WRT User


Joined: 10 Sep 2017
Posts: 92

PostPosted: Sat Jul 13, 2019 8:12    Post subject: Reply with quote
ninjadawg wrote:
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
Rolling Eyes

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...

New Kong's DD-WRT test build 40270M 2019-07-11
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320460


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? Confused
theirix
DD-WRT Novice


Joined: 17 Jul 2019
Posts: 2

PostPosted: Wed Jul 17, 2019 13:25    Post subject: Reply with quote
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:
Code:

Jul 17 15:41:10 netgearouter user.info : timer : #1085 (0x42c980)->0x42c9a0:    0 sec 0 usec   0x4033a9
Jul 17 15:41:10 netgearouter user.info : timer : #1086 (0x42c9a0)->0x0:    0 sec 353 usec   0x4033a9
Jul 17 15:41:10 netgearouter user.info : timer : eventlist is full


Syslog and dmesg attached.



ddwrt-r40260-syslog.txt
 Description:
syslog

Download
 Filename:  ddwrt-r40260-syslog.txt
 Filesize:  298.13 KB
 Downloaded:  115 Time(s)


ddwrt-r40260-dmesg.txt
 Description:
dmesg

Download
 Filename:  ddwrt-r40260-dmesg.txt
 Filesize:  8.49 KB
 Downloaded:  107 Time(s)

kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 2015
Location: Texas, USA

PostPosted: Wed Jul 17, 2019 19:50    Post subject: Reply with quote
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:
Code:

Jul 17 15:41:10 netgearouter user.info : timer : #1085 (0x42c980)->0x42c9a0:    0 sec 0 usec   0x4033a9
Jul 17 15:41:10 netgearouter user.info : timer : #1086 (0x42c9a0)->0x0:    0 sec 353 usec   0x4033a9
Jul 17 15:41:10 netgearouter user.info : timer : eventlist is full


Syslog and dmesg attached.


Old problem. You may wish to flash the latest public beta build : https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2019/07-16-2019-r40352/

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
benguild
DD-WRT Novice


Joined: 30 Jun 2019
Posts: 14

PostPosted: Sat Jul 20, 2019 11:06    Post subject: Reply with quote
Router/Version: ASUS AC-RT3100 (Hardware V6)
File: DD-WRT v3.0-r40260 std (07/09/19)
Kernel: Linux 4.4.184 #411 SMP PREEMPT Tue Jul 9 08:29:23 CEST 2019 armv7l
Mode: 2.4 GHz Repeater (+ VAP), 5 GHz Repeater (+ VAP)
Status: VAP on 2.4 GHz non-functional but SSID appears. Startup script does not help. AP/VAP on 5 GHz normal, repeater normal. Embarassed

Seems fine otherwise. Confused

_________________
https://benguild.com
eginnc
DD-WRT Novice


Joined: 23 Jul 2017
Posts: 49

PostPosted: Sat Jul 20, 2019 14:15    Post subject: Reply with quote
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

_________________
TP-Link Archer C7v2(US) (dd-wrt r40932)
Linksys EA8500 (OpenWrt 18.06.4)
Edgerouter X (OpenWrt 18.06.4)
theirix
DD-WRT Novice


Joined: 17 Jul 2019
Posts: 2

PostPosted: Sun Jul 21, 2019 11:39    Post subject: Reply with quote
kernel-panic69 wrote:


Old problem. You may wish to flash the latest public beta build : https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2019/07-16-2019-r40352/

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.
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 2015
Location: Texas, USA

PostPosted: Sun Jul 21, 2019 11:45    Post subject: Reply with quote
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.
lazardo
DD-WRT User


Joined: 17 Apr 2014
Posts: 101
Location: SF Bay Area

PostPosted: Sun Jul 21, 2019 19:23    Post subject: Reply with quote
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"

######
# prep
_timestamp () { _ts=$( cat /proc/uptime ); echo ${_ts% *}; }
_msg () { logger -st $TAG "$@"; }

cd /tmp

TAILPID=/var/run/rekey.tail.pid
if [ -e $TAILPID ]; then kill -9 $( cat $TAILPID ); rm $TAILPID; fi
[ -e REKEYTAIL ] && rm REKEYTAIL

if [ "$1" == "stop" ]; then exit 0; fi

mkfifo REKEYTAIL
tail -n 0 -F /var/log/messages > REKEYTAIL &
echo $! > $TAILPID

###########
# main loop

awk '$7 == "timer" { print $7; next }' REKEYTAIL |
while read key; do
   case "$key" in
      timer)
         [ "$key" == "$lastkey" ] && continue || lastkey=$key

         TS=$( _timestamp )
         _msg "nas trigger at $TS"

         for PID in $PIDS; do kill -9 $PID; done
         usleep 250000
         stopservice nas && stopservice wlconf
         startservice wlconf && startservice nas

         _msg "nas restart at $( _timestamp )"
         ;;
   esac
done

Today's trap:

Jul 22 08:55:51 dd-wrt user.info : timer : #0 (0x4317e0)->0x430f80: 0 sec 989248 usec 0x402d95
Jul 22 08:55:51 dd-wrt user.info : timer : #1 (0x430f80)->0x430a80: 461 sec 138302 usec 0x4033a9
Jul 22 08:55:51 dd-wrt user.info : timer : #2 (0x430a80)->0x430640: 0 sec 0 usec 0x4033a9
...
Jul 22 08:55:51 dd-wrt user.info : timer : #294 (0x42fae0)->0x42f6e0: 0 sec 0 usec 0x4033a9
Jul 22 08:55:51 dd-wrt user.notice rekey.watchdog: nas trigger at 157097.62
Jul 22 08:55:51 dd-wrt user.info : timer : #295 (0x42f6e0)->0x42f2e0: 0 sec 0 usec 0x4033a9
...
Jul 22 08:55:51 dd-wrt user.info : timer : #315 (0x429da0)->0x429b20: 0 sec 0 usec 0x4033a9
Jul 22 08:55:53 dd-wrt user.info : nas : start nas lan
Jul 22 08:55:53 dd-wrt user.info : nas : start nas for wl0
Jul 22 08:55:53 dd-wrt user.info : nas : NAS lan (wl0 interface) successfully started
Jul 22 08:55:53 dd-wrt user.info : nas : start nas lan
Jul 22 08:55:53 dd-wrt user.info : nas : start nas for wl1
Jul 22 08:55:53 dd-wrt user.info : nas : NAS lan (wl1 interface) successfully started
Jul 22 08:55:53 dd-wrt user.notice rekey.watchdog: nas restart at 157099.22


Last edited by lazardo on Mon Aug 26, 2019 22:42; edited 1 time in total
Goto page Previous  1, 2, 3  Next Display posts from previous:    Page 2 of 3
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum