New Kong's test build: DD-WRT 34900M - 2018/02/11

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


Joined: 11 Nov 2017
Posts: 150

PostPosted: Mon Feb 12, 2018 20:31    Post subject: Reply with quote
Router: Netgear R7000
Firmware: DD-WRT v3.0-r34900M kongac 02/11/18
Kernel: Linux 4.4.115 #520 SMP Sun Feb 11 21:44:13 CET 2018 armv7l

update: 34800 (~4 days of uptime) --> 34900
status: operational
reset: no
errors: none so far

This setup is very simple:
    *2.4 GHz only with only 1 wireless device in use most of the time.
    *Some physically connected systems (via unmanaged switch).
    * No USB, no VPN, no entware, etc.
    * QoS for buffer bloat (WTB/FQ_CODEL).
    * Using this test, I get Overall=A+, BufferBloat=A, Quality=A+


Will post back to update after a few days.

Uptime: 8 days, 7 min
Received (RX) 2,833,780 OK, no error
Transmitted (TX) 3,844391 OK, no error


Last edited by thunderhead on Tue Feb 20, 2018 20:34; edited 4 times in total
Sponsor
Katsury
DD-WRT Novice


Joined: 17 Mar 2014
Posts: 1

PostPosted: Mon Feb 12, 2018 22:07    Post subject: Reply with quote
Router: Asus RT-AC68R

Firmware: DD-WRT v3.0-r34900M kongac (02/11/1Cool

Kernel: Linux 4.4.115 #520 SMP Sun Feb 11 21:44:13 CET 2018 armv7l

Status: Good So Far

Reset: Yes

Errors: None So Far.

Will append any issues I run into.
mchaney
DD-WRT User


Joined: 26 Apr 2013
Posts: 389

PostPosted: Mon Feb 12, 2018 23:08    Post subject: Reply with quote
OK, after running 34900 all day, I'm now convinced that what I saw with my 2.4 Ghz b/g WiFi cameras was not placebo. With all prior versions (say in the past 6 months), my WiFi cameras would get "laggy" as the day goes on and they'd start dropping frames and missing motion events the longer the router up-time.

34900 seems a LOT better. My cameras have been stable all day and I'm not seeing the frame stuttering in this 34900 version. Kong, whatever you did WRT 2.4 Ghz b/g WiFi... please don't undo it! Wink

Mike
SinCalChewy
DD-WRT User


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

PostPosted: Mon Feb 12, 2018 23:36    Post subject: Reply with quote
Router: 2x Netgear R7000
Firmware: DD-WRT v3.0-r34900M kongac (02/11/1Cool
Previous: DD-WRT v3.0-r34320M kongac (01/03/1Cool
Kernel: Linux 4.4.115 #520 SMP Sun Feb 11 21:44:13 CET 2018 armv7l
Status: Seems good, speedtests are fine.
Reset: No.
Errors: None thus far.

USB support and OpenVPN server are both running fine.

_________________

Deployed Routers:
Netgear R7800 - 1x build 46979
- Gateway (USB /w Entware, CAKE QoS)
Netgear R7000 - 3x build 46979
sideup66
DD-WRT User


Joined: 26 Nov 2016
Posts: 102

PostPosted: Tue Feb 13, 2018 6:07    Post subject: Reply with quote
Router: Netgear r6300v2
Firmware: DD-WRT v3.0-r34900M kongac (02/11/1Cool
Previous: DD-WRT v3.0-r34320M kongac (01/03/1Cool
Reset: no
Errors: none
Comments: so far so good, running for a few days now, just notice a slight slowdown with this build, not an unusable level but at times during high load things just seem....slower. chalking this up to Kaiser patches...
eywong
DD-WRT User


Joined: 21 Jul 2010
Posts: 120
Location: USA

PostPosted: Tue Feb 13, 2018 7:35    Post subject: Asus RT-AC68U A1 Reply with quote
Router: Asus RT-AC68U (H/W Ver: A1)
Firmware: DD-WRT v3.0-r34900M kongac (02/11/18)
Previous: DD-WRT v3.0-r34800M kongac (02/07/18)
Kernel: Linux 4.4.115 #520 SMP Sun Feb 11 21:44:13 CET 2018 armv7l
Previous: Linux 4.4.114 #518 SMP Wed Feb 7 08:19:26 CET 2018 armv7l
Status: ok
Reset: no (ddup --flash-latest)
Errors: no
Uptime: 14:23

wl0: AP / NG-Mixed / Ch 11
Channel Width: 20 MHz
wl1: AP / NA-Mixed / Ch 52 + 54
Channel Width: Wide HT40
Extension Channel: lower
DHCP Server: Enabled - Running
Static Leases: 4 hardwired NAS, 1 wireless printer
NTP Client: Enable
Server IP/Name: us.pool.ntp.org
hurleyp
DD-WRT User


Joined: 10 Sep 2009
Posts: 425
Location: Ottawa, Ontario, Canada

PostPosted: Tue Feb 13, 2018 13:44    Post subject: Reply with quote
Router/Version: Netgear R7000
Firmware: v3.0-r34900M kongac (02/11/18 )
Kernel: Linux 4.4.115 #520 SMP Sun Feb 11 21:44:13 CET 2018 armv7l
Previous: v3.0-r34800M kongac (02/07/18 )
Mode/Status: Up and running for 24 hours
Reset: Soft boot before and after ddup, no 'erase nvram' this time.
Issues/Errors: Several "SSL accept error" messages in the syslog.

Still plenty of "SSL accept error" messages in the log, as it has for the past two versions of kong. As no one else seems to be encountering this problem, I'll assume it's a local issue. When I have some spare time I'll do some device disconnect/connect trial and error testing. The devices on my LAN are functioning as expected, and the log gives no other details.

I'm seeing the ntpclient errors as reported by others, but the date and time on my R7000 is correct.

The temperatures are good: CPU 54.7 °C / WL0 44.0 °C / WL1 47.0 °C (The R7000 is wall-mounted.)

Current basic R7000 setup (subject to change of course):
- SFE - On
- Static WAN IP
- LAN DHCP Enabled
- IPv4 only
- 1 wireless VLAN on wl0
- Encrypt DNS disabled
- Wireless: Regulatory Domain = UNITED_STATES, wl0 Mixed (ch. 1), wl1 NA-Mixed (ch. 161 + 159), AES
- SNMP enabled, SSH enabled, Telnet disabled
- Firewall enabled, Log Level high
- Syslog: remote to Logentries. klogd: disabled.
- USB Flashdrive mounted as JFFS, adblocking via pixelserv
- NO: ttraf, VNC, Zabbix, VPN, Radius, OpenVPN
- NO: Port forwarding, UPnP, DMZ, QoS
- NO: Samba, CIFS, JFFS2, miniDLNA, Entware, Optware

_________________
Netgear R7000: v3.0-r54248 std (11/29/23)
EdgeRouter-X: EdgeOS v2.0.9-hotfix 7


Last edited by hurleyp on Tue Feb 13, 2018 21:11; edited 1 time in total
blaser
DD-WRT Guru


Joined: 16 Jul 2006
Posts: 525

PostPosted: Tue Feb 13, 2018 17:55    Post subject: Reply with quote
Router AC68U
after installing this version I noticed that I have errors in the syslog that I haven't seen before.
in my configuration:
1) I have IPV6 disabled
2) I entered manually ntp as 3.pool.ntp.org on the main page.

the error I'm getting is as below, looks like it is tying to use 2.pool.ntp.org and not 3.pool.ntp.org and tries to connect via ipv6 first.


    Feb 13 11:56:00 Asus daemon.debug ntpclient[7363]: Connecting to 2.pool.ntp.org [2001:470:e66b:10::13] ...
    Feb 13 11:56:00 Asus daemon.err ntpclient[7363]: Failed connecting to 2.pool.ntp.org [2001:470:e66b:10::13]: Address family not supported by protocol
    Feb 13 11:56:00 Asus daemon.debug ntpclient[7363]: Connecting to 212.18.3.19 [212.18.3.19] ...
    Feb 13 11:56:00 Asus daemon.info ntpclient[7363]: Time set from 212.18.3.19 [212.18.3.19].
    Feb 13 11:56:00 Asus daemon.err process_monitor[1946]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)

_________________
Netgear R9000 main router
RAX80 as AP
jimbo83
DD-WRT Novice


Joined: 05 Jan 2014
Posts: 11

PostPosted: Wed Feb 14, 2018 1:14    Post subject: Reply with quote
blaser wrote:
Router AC68U
after installing this version I noticed that I have errors in the syslog that I haven't seen before.
in my configuration:
1) I have IPV6 disabled
2) I entered manually ntp as 3.pool.ntp.org on the main page.

the error I'm getting is as below, looks like it is tying to use 2.pool.ntp.org and not 3.pool.ntp.org and tries to connect via ipv6 first.


    Feb 13 11:56:00 Asus daemon.debug ntpclient[7363]: Connecting to 2.pool.ntp.org [2001:470:e66b:10::13] ...
    Feb 13 11:56:00 Asus daemon.err ntpclient[7363]: Failed connecting to 2.pool.ntp.org [2001:470:e66b:10::13]: Address family not supported by protocol
    Feb 13 11:56:00 Asus daemon.debug ntpclient[7363]: Connecting to 212.18.3.19 [212.18.3.19] ...
    Feb 13 11:56:00 Asus daemon.info ntpclient[7363]: Time set from 212.18.3.19 [212.18.3.19].
    Feb 13 11:56:00 Asus daemon.err process_monitor[1946]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)


I saw something similar after the restart after installing with ddup --flash-latest

It would not pick up the time until I switched to 1.us.pool.ntp.org. This caused YAMon3 to fail to start.
imalilteapot
DD-WRT User


Joined: 19 Sep 2007
Posts: 66

PostPosted: Wed Feb 14, 2018 1:38    Post subject: Reply with quote
I'm seeing some odd issues with this build, that the prior build did not have. I RDP into my server (port 443) from my laptop nearly all day. However, with this build, if I minimize RDP for a little while, the connection stops (doesnt drop though). I click on something on the desktop, but nothing happens. If I wait on that screen, it will reconnect after 10 seconds or so.

Prior build never dropped the connection, nor "froze" like it did in this one.

_________________
Netgear R8000 (Kong firmware)
31 Wireless Devices
9 hardwired devices
13 ports forwarded
DDNS enabled
No QOS
jheide44
DD-WRT Guru


Joined: 03 Sep 2013
Posts: 739

PostPosted: Wed Feb 14, 2018 2:30    Post subject: Reply with quote
Netgear R6400
Kong PTB 31870 file dated 4/16/2017 --> Kong PTB 34900 file dated 2/11/2018 )

**Dirty Flash -- NO RESET** (I've been "riding dirty" for a long time now, ever since the R6400 was "new to me")

Firmware Version: DD-WRT v3.0-r34900M kongac (02/11/18 )
Kernel Version: Linux 4.4.115 #520 SMP Sun Feb 11 21:44:13 CET 2018 armv7l

File: No real Point in linking official Kong PTB repo as next PTB will overwrite this file... (but HERE is link to my personal repo) or not, i'm too lazy to maintain that historial Kong FW repo
File Name: dd-wrt.v24-K3_AC_ARM_STD_128K.bin
MD5: a1fe90a23803133272d582d6678859ee


DDNS -- OK (custom for dnsomatic)
SSH Tunneling -- OK
RDP session via SSH Tunneling -- OK
OpenDNS Content Filtering -- OK
SAMBA -- OK, 2tb public NAS no security
MiniDLNA -- OK (upon initial review)

no reboots and solid WiFi (will keep this thread updated if anything changes)

**note: Flashed from the far side of an SSH tunnel. Initial testing performed based on 30 minutes observations, I will update if anything above is not accurate**



ddup command love notes:
login as: root
DD-WRT v3.0-r31870M kongac (c) 2017 NewMedia-NET GmbH
Release: 04/16/17
Authenticating with public key "rsa-key-20110928"
Passphrase for key "xxxxxxxxxx":
==========================================================

___ ___ _ _____ ______ ____ ___
/ _ \/ _ \___| | /| / / _ \/_ __/ _ __|_ / / _ \
/ // / // /___/ |/ |/ / , _/ / / | |/ //_ <_/ // /
/____/____/ |__/|__/_/|_| /_/ |___/____(_)___/

DD-WRT v3.0
http://www.dd-wrt.com

==========================================================


BusyBox v1.26.2 (2017-04-16 17:52:03 CEST) built-in shell (ash)

root@DD-WRT:~# ddup --flash-latest
New release 34900 for Netgear R6400 available.
Do you want to update (y/n) [default=n]:
y
Connecting to www.desipro.de (212.227.247.157:80)
fw.bin 100% |*******************************| 22944k 0:00:00 ETA
Connecting to www.desipro.de (212.227.247.157:80)
fw.bin.sig 100% |*******************************| 256 0:00:00 ETA
Signature for http://www.desipro.de/ddwrt/K3-AC-Arm/TEST/dd-wrt.v24-K3_AC_ARM_STD_128K.bin ok.
Are you sure you want to proceeed (y/n) [default=n]:


** REBOOT HERE **


login as: root
DD-WRT v3.0-r34900M kongac (c) 2018 NewMedia-NET GmbH
Release: 02/11/18
Authenticating with public key "xxxxxxxxxx"
Passphrase for key "rsa-key-20110928":
==========================================================

___ ___ _ _____ ______ ____ ___
/ _ \/ _ \___| | /| / / _ \/_ __/ _ __|_ / / _ \
/ // / // /___/ |/ |/ / , _/ / / | |/ //_ <_/ // /
/____/____/ |__/|__/_/|_| /_/ |___/____(_)___/

DD-WRT v3.0
http://www.dd-wrt.com

==========================================================


BusyBox v1.28.0 (2018-02-11 21:49:41 CET) built-in shell (ash)

root@DD-WRT:~# ddup --flash-latest

Your Netgear R6400 is using latest revision
root@DD-WRT:~#

_________________
reenignE esreveR
Resistance is NOT futile... It's Voltage divided by Current!


_.-:Curently Deployed Devices:-._
Loc_1.0: R6400 -- v3.0-r51887 std (02/28/23)
Loc_2.0: R6300v2 -- Kong PTB 35550M 03-28-2018

Others: too many others to list

R7000 (& similar HW) Tips/Tricks HERE.

Assumptions:
1. Everyone on the forum has read the relevant forum section announcements.
2. For Broadcom section we have ALL at least tried to understand the "Peacock" thread,
HERE
imalilteapot
DD-WRT User


Joined: 19 Sep 2007
Posts: 66

PostPosted: Wed Feb 14, 2018 5:56    Post subject: Reply with quote
jheide44 wrote:

File: No real Point in linking official Kong PTB repo as next PTB will overwrite this file... (but HERE is link to my personal repo) or not, i'm too lazy to maintain that historial Kong FW repo
File Name: dd-wrt.v24-K3_AC_ARM_STD_128K.bin
MD5: a1fe90a23803133272d582d6678859ee


Try http://ddwrt-kong.clonevince.fr instead then. It has all versions of Kong builds.

_________________
Netgear R8000 (Kong firmware)
31 Wireless Devices
9 hardwired devices
13 ports forwarded
DDNS enabled
No QOS
wabe
DD-WRT Guru


Joined: 17 Jun 2006
Posts: 889

PostPosted: Wed Feb 14, 2018 20:07    Post subject: Reply with quote
blaser wrote:
Router AC68U
after installing this version I noticed that I have errors in the syslog that I haven't seen before.
in my configuration:
1) I have IPV6 disabled
2) I entered manually ntp as 3.pool.ntp.org on the main page.

the error I'm getting is as below, looks like it is tying to use 2.pool.ntp.org and not 3.pool.ntp.org and tries to connect via ipv6 first.


    Feb 13 11:56:00 Asus daemon.debug ntpclient[7363]: Connecting to 2.pool.ntp.org [2001:470:e66b:10::13] ...
    Feb 13 11:56:00 Asus daemon.err ntpclient[7363]: Failed connecting to 2.pool.ntp.org [2001:470:e66b:10::13]: Address family not supported by protocol
    Feb 13 11:56:00 Asus daemon.debug ntpclient[7363]: Connecting to 212.18.3.19 [212.18.3.19] ...
    Feb 13 11:56:00 Asus daemon.info ntpclient[7363]: Time set from 212.18.3.19 [212.18.3.19].
    Feb 13 11:56:00 Asus daemon.err process_monitor[1946]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)

Me too! Router seems to work well in general but lot's of these messages in the log. No manual entry for ntp in my case.
UPDATE: Got all sort of connectivity problems both on wired and wireless clients. Had to revert to 34800M, a very good build for ASUS AC68U rev C1.

_________________
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


Last edited by wabe on Wed Feb 14, 2018 21:28; edited 1 time in total
Siggyceline
DD-WRT User


Joined: 14 Jan 2018
Posts: 65

PostPosted: Wed Feb 14, 2018 20:34    Post subject: Reply with quote
jheide44 wrote:
Netgear R6400
Kong PTB 31870 file dated 4/16/2017 --> Kong PTB 34900 file dated 2/11/2018 )

**Dirty Flash -- NO RESET** (I've been "riding dirty" for a long time now, ever since the R6400 was "new to me")

Firmware Version: DD-WRT v3.0-r34900M kongac (02/11/18 )
Kernel Version: Linux 4.4.115 #520 SMP Sun Feb 11 21:44:13 CET 2018 armv7l

File: No real Point in linking official Kong PTB repo as next PTB will overwrite this file... (but HERE is link to my personal repo) or not, i'm too lazy to maintain that historial Kong FW repo
File Name: dd-wrt.v24-K3_AC_ARM_STD_128K.bin
MD5: a1fe90a23803133272d582d6678859ee


DDNS -- OK (custom for dnsomatic)
SSH Tunneling -- OK
RDP session via SSH Tunneling -- OK
OpenDNS Content Filtering -- OK
SAMBA -- OK, 2tb public NAS no security
MiniDLNA -- OK (upon initial review)

no reboots and solid WiFi (will keep this thread updated if anything changes)

**note: Flashed from the far side of an SSH tunnel. Initial testing performed based on 30 minutes observations, I will update if anything above is not accurate**



ddup command love notes:
login as: root
DD-WRT v3.0-r31870M kongac (c) 2017 NewMedia-NET GmbH
Release: 04/16/17
Authenticating with public key "rsa-key-20110928"
Passphrase for key "xxxxxxxxxx":
==========================================================

___ ___ _ _____ ______ ____ ___
/ _ \/ _ \___| | /| / / _ \/_ __/ _ __|_ / / _ \
/ // / // /___/ |/ |/ / , _/ / / | |/ //_ <_/ // /
/____/____/ |__/|__/_/|_| /_/ |___/____(_)___/

DD-WRT v3.0
http://www.dd-wrt.com

==========================================================


BusyBox v1.26.2 (2017-04-16 17:52:03 CEST) built-in shell (ash)

root@DD-WRT:~# ddup --flash-latest
New release 34900 for Netgear R6400 available.
Do you want to update (y/n) [default=n]:
y
Connecting to www.desipro.de (212.227.247.157:80)
fw.bin 100% |*******************************| 22944k 0:00:00 ETA
Connecting to www.desipro.de (212.227.247.157:80)
fw.bin.sig 100% |*******************************| 256 0:00:00 ETA
Signature for http://www.desipro.de/ddwrt/K3-AC-Arm/TEST/dd-wrt.v24-K3_AC_ARM_STD_128K.bin ok.
Are you sure you want to proceeed (y/n) [default=n]:


** REBOOT HERE **


login as: root
DD-WRT v3.0-r34900M kongac (c) 2018 NewMedia-NET GmbH
Release: 02/11/18
Authenticating with public key "xxxxxxxxxx"
Passphrase for key "rsa-key-20110928":
==========================================================

___ ___ _ _____ ______ ____ ___
/ _ \/ _ \___| | /| / / _ \/_ __/ _ __|_ / / _ \
/ // / // /___/ |/ |/ / , _/ / / | |/ //_ <_/ // /
/____/____/ |__/|__/_/|_| /_/ |___/____(_)___/

DD-WRT v3.0
http://www.dd-wrt.com

==========================================================


BusyBox v1.28.0 (2018-02-11 21:49:41 CET) built-in shell (ash)

root@DD-WRT:~# ddup --flash-latest

Your Netgear R6400 is using latest revision
root@DD-WRT:~#


I'm using R6400 as an AP (Ethernet-->WiFi). Seems with v3.0-r34900M, R6400 is consistently locking up. I've had to power-cycle-reboot about a dozen times now. Since it requires a power-cycle reboot to get back online, there aren't any logs to see what is happening. Don't mind beta-testing at all, but since this issue is a lock-up requiring power-cycle, I need to reload something that won't require physical power-cycling. (i.e., I'm good testing even if a bug requires a remote reconfig/reboot/etc., but can't keep having to physically power-cycle re-boot... The R6400 sits behind my Home-Theater Center Channel Speaker in my Family Room, and it is a pain to have to keep removing the speaker and get inside the cabinet to power-cycle. )

So, I Re-loaded Firmware: DD-WRT v3.0-r33675M kongac (11/03/17) today via GUI, and so far seems stable.

I'll report back after a few days if I don't have any issues with 33675M.

Thanks Kong for all your hard work! I've moved my R8000, R7800, and R6400 to your builds. R7800 and R8000 are both on 34900M, and seem fine. I've just replaced my R7000 with R8000 as my main router (Wi-Fi disabled), and am using R6400 and R7800 as Wi-FI APs. (R7000 remains on NETGEAR stock offline as a spare, in case things go wrong with R8000 DD-WRT.) This is great, and now I can implement all the features NETGEAR Stock FW doesn't support, but always wished for. VERY Happy camper here...

SIggy.
kendalja
DD-WRT Novice


Joined: 07 Feb 2014
Posts: 45

PostPosted: Wed Feb 14, 2018 22:42    Post subject: Reply with quote
Router: R7000
Firmware: DD-WRT v3.0-r34900M kongac (02/11/1Cool
Kernel: Linux 4.4.115 #520 SMP Sun Feb 11 21:44:13 CET 2018 armv7l
Status: Openrational
Reset: No
Errors: Transmitted (TX)8205558 OK, 16 errors


Everything seems fine except I'm seeing a bunch of these in the logs:

Feb 13 04:41:53 196.52.39.7 openvpn: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #89616 ]

_________________
The opposite of networking is NOT working.
Goto page Previous  1, 2, 3  Next Display posts from previous:    Page 2 of 3
Post new topic   Reply to topic    DD-WRT 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