New Kong test build: DD-WRT 33525M - 2017/10/16

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


Joined: 18 Oct 2017
Posts: 3

PostPosted: Wed Oct 18, 2017 23:56    Post subject: Reply with quote
I can confirm Kong build works for Asus RT-ac68u, but definitely NOT the brainslayer build.

Router: Asus RT-AC68U B1
Firmware: DD-WRT v3.0-r33525M kongac
Status: OK
Reset: No
Errors: No
Sponsor
mike@minantech.com
DD-WRT Novice


Joined: 19 Oct 2017
Posts: 1

PostPosted: Thu Oct 19, 2017 4:02    Post subject: Reply with quote
Router: R7000
Firmware: v3.0-r33525M kongac
Kernel: Linux 4.4.92 #454 SMP Mon Oct 16 21:39:05 CEST 2017 armv7l
Status: OK
Uptime: 3:28
Reset: no
Errors: no
jazzdude00021
DD-WRT Novice


Joined: 27 Sep 2014
Posts: 7

PostPosted: Thu Oct 19, 2017 4:54    Post subject: Reply with quote
Router: Netgear R6400
Firmware: DD-WRT v3.0-r33525M kongac (10/16/17)
Kernel: Linux 4.4.92 #454 SMP Mon Oct 16 21:39:05 CEST 2017 armv7l
Status: 30 minutes and all seems fine.
Reset: No (ddup --flash-latest works like a charm.)
Errors: None so far.
nolimitz
DD-WRT Guru


Joined: 26 Nov 2010
Posts: 597

PostPosted: Thu Oct 19, 2017 8:13    Post subject: Reply with quote
Hi Kong,

can you look into this?

root@R6700:~# ddup --flash-latest
Auto update for the Netgear R6700 is currently not supported.
r4nd0m
DD-WRT User


Joined: 01 Dec 2006
Posts: 84
Location: UK

PostPosted: Fri Oct 20, 2017 5:59    Post subject: Reply with quote
Router: Netgear X6 R8000
Firmware: DD-WRT v3.0-r33525M kongac (10/16/17)
Kernel: Linux 4.4.92 #454 SMP Mon Oct 16 21:39:05 CEST 2017 armv7l
Status: up 1 day, 9:34 and all seems fine.
Reset: No (ddup --flash-latest works like a charm.)
Errors: None so far.

different VAPs
custom bridges
over 50 DHCP clients
DHCP-DNS-masq
firewall
usb
low RX/TX error rate

_________________
Netgear X6 R8000 - DD-WRT v3.0-r34320M kongac
ddaniel51
DD-WRT Guru


Joined: 19 Feb 2013
Posts: 1464

PostPosted: Fri Oct 20, 2017 7:59    Post subject: Reply with quote
nolimitz wrote:
Hi Kong,

can you look into this?

root@R6700:~# ddup --flash-latest
Auto update for the Netgear R6700 is currently not supported.


All builds include ddup util, which allows update checking
and flashing of the following models:

Netgear EX6200
Netgear AC1450
Netgear R6250
Netgear R6300V2
Netgear R6400
Netgear R7000
Netgear R8000
Netgear R8500
Asus RT-AC68R
Asus RT-AC68U
Asus RT-AC56U
Asus RT-AC3200
Asus RT-AC5300
Buffalo WXR-1900DHP
Linksys EA6900
Linksys EA6700
Netgear R6900P/R7000P

_________________
Segment 1 XR700 10Gb LAN, 1Gb WAN ISP BS
Wired AP 1 Unifi Wifi 6 LR US 1Gb LAN
Wired AP 2 Unifi Wifi 6 LR US 1Gb LAN
Wired AP 3 Unifi Wifi 6 LR US 1Gb LAN
Syslog Services Asustor 7110T NAS 10GB
NetGear XS716T 10GB Switch
download1.dd-wrt.com/dd-wrtv2/downloads/betas/ (Brain Slayer)
YAMon https://usage-monitoring.com/index.php
<Kong>
DD-WRT Guru


Joined: 15 Dec 2010
Posts: 4339
Location: Germany

PostPosted: Fri Oct 20, 2017 10:28    Post subject: Reply with quote
diogosena wrote:
LZ4 compression in Openvpn server is broken.

"Options error: bad comp option: lz4"


It is a bug in openvpn configure script, they already fixed it, not sure how such a bug could make it into a final release, on a sane system you can't compile openvpn, unless you disable lz4, like I had to do, see:

https://github.com/OpenVPN/openvpn/commit/f91e4863bc138213a07a2cf53ad71d8a4532abef


Anyways next build will have openvpns compat lz4 enabled again, but we should probably add regular lz4 to our sources. Not sure if openvpns lz4 support has the same performance as standard lz4.

_________________
KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
zfil
DD-WRT Novice


Joined: 12 Oct 2014
Posts: 31

PostPosted: Fri Oct 20, 2017 10:44    Post subject: Reply with quote
Router: R7000
Firmware: DD-WRT v3.0-r33525M kongac (10/16/17)
Kernel: Linux r7000 4.4.92 #454 SMP Mon Oct 16 21:39:05 CEST 2017 armv7l DD-WRT
Upgraded: from r33520M via ddup --flash-remote http://www.desipro.de/ddwrt/K3-AC-Arm/TEST/dd-wrt.v24-K3_AC_ARM_STD.bin
Reset: erase nvram && reboot
Status: error

Hello,

After 2 days and half uptime freeze again, this time I haven't been able to capture the logs so I don't know if it is a out of memory problem like the other times.

Kong could you please give me some pointers on how I could troubleshoot this ?

I've seen this in the kernel messages, but having 3 bads blocs shouldn't be a problem no ?
Code:
Scanning device for bad blocks
Bad eraseblock 597 at 0x000004aa0000
Bad eraseblock 600 at 0x000004b00000
Bad eraseblock 845 at 0x0000069a0000


I don't use JFFS, here the processes running on the r7000:

Code:
# ps wl
S   UID   PID  PPID   VSZ   RSS TTY   STIME TIME     CMD
S     0     1     0   976   600 ttyS0 12:28 00:00:03 /sbin/init
S     0     2     0     0     0 0:0   12:28 00:00:00 [kthreadd]
S     0     3     2     0     0 0:0   12:28 00:00:00 [ksoftirqd/0]
S     0     4     2     0     0 0:0   12:28 00:00:00 [kworker/0:0]
S     0     5     2     0     0 0:0   12:28 00:00:00 [kworker/0:0H]
S     0     6     2     0     0 0:0   12:28 00:00:00 [kworker/u4:0]
S     0     7     2     0     0 0:0   12:28 00:00:00 [rcu_sched]
S     0     8     2     0     0 0:0   12:28 00:00:00 [rcu_bh]
S     0     9     2     0     0 0:0   12:28 00:00:00 [migration/0]
S     0    10     2     0     0 0:0   12:28 00:00:00 [migration/1]
S     0    11     2     0     0 0:0   12:28 00:00:00 [ksoftirqd/1]
S     0    12     2     0     0 0:0   12:28 00:00:00 [kworker/1:0]
S     0    13     2     0     0 0:0   12:28 00:00:00 [kworker/1:0H]
S     0   120     2     0     0 0:0   12:28 00:00:00 [writeback]
S     0   122     2     0     0 0:0   12:28 00:00:00 [crypto]
S     0   123     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   125     2     0     0 0:0   12:28 00:00:00 [kblockd]
S     0   152     2     0     0 0:0   12:28 00:00:01 [kworker/0:1]
S     0   198     2     0     0 0:0   12:28 00:00:00 [kswapd0]
S     0   199     2     0     0 0:0   12:28 00:00:01 [kworker/1:1]
S     0   200     2     0     0 0:0   12:28 00:00:00 [vmstat]
S     0   201     2     0     0 0:0   12:28 00:00:00 [fsnotify_mark]
S     0   231     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   232     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   233     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   234     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   235     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   236     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   237     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   238     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   239     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   240     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   241     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   242     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   243     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   244     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   245     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   246     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   280     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   283     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   286     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   289     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   292     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   295     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   298     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   301     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   309     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   314     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   319     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   324     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   329     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   354     2     0     0 0:0   12:28 00:00:00 [deferwq]
S     0   357     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   361     2     0     0 0:0   12:28 00:00:00 [kworker/0:1H]
S     0   362     2     0     0 0:0   12:28 00:00:00 [kworker/1:1H]
S     0   615     1   756   564 0:0   12:28 00:00:00 /sbin/hotplug2 --set-rules-file /etc/hotplug2.rules --persistent
S     0   619     1   800   560 0:0   12:28 00:00:00 /sbin/mstpd
S     0  1139     1  1440   836 0:0   12:28 00:00:00 process_monitor
S     0  1144     1  1404   916 0:0   12:28 00:00:00 upnp -D -W vlan2
S     0  1148     1  1372   652 0:0   12:28 00:00:00 wland
S     0  1170     1   728   420 0:0   12:28 00:00:00 cron
S     0  1182     1  1428   816 0:0   12:28 00:00:00 nas -P /tmp/nas.wl0lan.pid -H 34954 -l br0 -i eth1 -A -m 128 -k XXXXXXXXXXXXX
S     0  1183     1  1428   828 0:0   12:28 00:00:00 nas -P /tmp/nas.wl0.1lan.pid -H 34954 -l wl0.1 -i wl0.1 -A -m 128 -k XXXXXXXXXXXXX
S     0  1184     1  1428   816 0:0   12:28 00:00:00 nas -P /tmp/nas.wl1lan.pid -H 34954 -l br0 -i eth2 -A -m 128 -k XXXXXXXXXXXXX
S     0  1203     1  4104  1916 0:0   12:28 00:00:01 httpd -p 80
S     0  1205     1  1184   500 0:0   12:28 00:00:00 resetbutton
S     0  1421     2     0     0 0:0   12:30 00:00:00 [kworker/u4:4]
S     0  1793     1  1656  1084 0:0   12:32 00:00:00 ttraff
S     0  1982     1  1540   828 0:0   12:32 00:00:00 dnsmasq -u root -g root --conf-file=/tmp/dnsmasq.conf --cache-size=1500 --dhcp
S     0  1994     1   860   552 0:0   12:32 00:00:00 dropbear -b /tmp/loginprompt -r /tmp/root/.ssh/ssh_host_rsa_key -p 22
S     0  2115     1  1160   628 0:0   12:32 00:00:00 syslogd -L -R 192.168.X.X
S     0  2117     1  1160   688 0:0   12:32 00:00:00 klogd
R     0  2132  1994   928   656 0:0   12:32 00:00:00 dropbear -b /tmp/loginprompt -r /tmp/root/.ssh/ssh_host_rsa_key -p 22
S     0  2133  2132  1164   844 pts0  12:32 00:00:00 -sh
R     0  2693  2133  1160   708 pts0  12:39 00:00:00 ps wl


Thanks
<Kong>
DD-WRT Guru


Joined: 15 Dec 2010
Posts: 4339
Location: Germany

PostPosted: Fri Oct 20, 2017 11:04    Post subject: Reply with quote
zfil wrote:
Router: R7000
Firmware: DD-WRT v3.0-r33525M kongac (10/16/17)
Kernel: Linux r7000 4.4.92 #454 SMP Mon Oct 16 21:39:05 CEST 2017 armv7l DD-WRT
Upgraded: from r33520M via ddup --flash-remote http://www.desipro.de/ddwrt/K3-AC-Arm/TEST/dd-wrt.v24-K3_AC_ARM_STD.bin
Reset: erase nvram && reboot
Status: error

Hello,

After 2 days and half uptime freeze again, this time I haven't been able to capture the logs so I don't know if it is a out of memory problem like the other times.

Kong could you please give me some pointers on how I could troubleshoot this ?

I've seen this in the kernel messages, but having 3 bads blocs shouldn't be a problem no ?
Code:
Scanning device for bad blocks
Bad eraseblock 597 at 0x000004aa0000
Bad eraseblock 600 at 0x000004b00000
Bad eraseblock 845 at 0x0000069a0000


I don't use JFFS, here the processes running on the r7000:

Code:
# ps wl
S   UID   PID  PPID   VSZ   RSS TTY   STIME TIME     CMD
S     0     1     0   976   600 ttyS0 12:28 00:00:03 /sbin/init
S     0     2     0     0     0 0:0   12:28 00:00:00 [kthreadd]
S     0     3     2     0     0 0:0   12:28 00:00:00 [ksoftirqd/0]
S     0     4     2     0     0 0:0   12:28 00:00:00 [kworker/0:0]
S     0     5     2     0     0 0:0   12:28 00:00:00 [kworker/0:0H]
S     0     6     2     0     0 0:0   12:28 00:00:00 [kworker/u4:0]
S     0     7     2     0     0 0:0   12:28 00:00:00 [rcu_sched]
S     0     8     2     0     0 0:0   12:28 00:00:00 [rcu_bh]
S     0     9     2     0     0 0:0   12:28 00:00:00 [migration/0]
S     0    10     2     0     0 0:0   12:28 00:00:00 [migration/1]
S     0    11     2     0     0 0:0   12:28 00:00:00 [ksoftirqd/1]
S     0    12     2     0     0 0:0   12:28 00:00:00 [kworker/1:0]
S     0    13     2     0     0 0:0   12:28 00:00:00 [kworker/1:0H]
S     0   120     2     0     0 0:0   12:28 00:00:00 [writeback]
S     0   122     2     0     0 0:0   12:28 00:00:00 [crypto]
S     0   123     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   125     2     0     0 0:0   12:28 00:00:00 [kblockd]
S     0   152     2     0     0 0:0   12:28 00:00:01 [kworker/0:1]
S     0   198     2     0     0 0:0   12:28 00:00:00 [kswapd0]
S     0   199     2     0     0 0:0   12:28 00:00:01 [kworker/1:1]
S     0   200     2     0     0 0:0   12:28 00:00:00 [vmstat]
S     0   201     2     0     0 0:0   12:28 00:00:00 [fsnotify_mark]
S     0   231     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   232     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   233     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   234     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   235     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   236     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   237     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   238     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   239     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   240     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   241     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   242     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   243     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   244     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   245     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   246     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   280     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   283     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   286     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   289     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   292     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   295     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   298     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   301     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   309     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   314     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   319     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   324     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   329     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   354     2     0     0 0:0   12:28 00:00:00 [deferwq]
S     0   357     2     0     0 0:0   12:28 00:00:00 [bioset]
S     0   361     2     0     0 0:0   12:28 00:00:00 [kworker/0:1H]
S     0   362     2     0     0 0:0   12:28 00:00:00 [kworker/1:1H]
S     0   615     1   756   564 0:0   12:28 00:00:00 /sbin/hotplug2 --set-rules-file /etc/hotplug2.rules --persistent
S     0   619     1   800   560 0:0   12:28 00:00:00 /sbin/mstpd
S     0  1139     1  1440   836 0:0   12:28 00:00:00 process_monitor
S     0  1144     1  1404   916 0:0   12:28 00:00:00 upnp -D -W vlan2
S     0  1148     1  1372   652 0:0   12:28 00:00:00 wland
S     0  1170     1   728   420 0:0   12:28 00:00:00 cron
S     0  1182     1  1428   816 0:0   12:28 00:00:00 nas -P /tmp/nas.wl0lan.pid -H 34954 -l br0 -i eth1 -A -m 128 -k XXXXXXXXXXXXX
S     0  1183     1  1428   828 0:0   12:28 00:00:00 nas -P /tmp/nas.wl0.1lan.pid -H 34954 -l wl0.1 -i wl0.1 -A -m 128 -k XXXXXXXXXXXXX
S     0  1184     1  1428   816 0:0   12:28 00:00:00 nas -P /tmp/nas.wl1lan.pid -H 34954 -l br0 -i eth2 -A -m 128 -k XXXXXXXXXXXXX
S     0  1203     1  4104  1916 0:0   12:28 00:00:01 httpd -p 80
S     0  1205     1  1184   500 0:0   12:28 00:00:00 resetbutton
S     0  1421     2     0     0 0:0   12:30 00:00:00 [kworker/u4:4]
S     0  1793     1  1656  1084 0:0   12:32 00:00:00 ttraff
S     0  1982     1  1540   828 0:0   12:32 00:00:00 dnsmasq -u root -g root --conf-file=/tmp/dnsmasq.conf --cache-size=1500 --dhcp
S     0  1994     1   860   552 0:0   12:32 00:00:00 dropbear -b /tmp/loginprompt -r /tmp/root/.ssh/ssh_host_rsa_key -p 22
S     0  2115     1  1160   628 0:0   12:32 00:00:00 syslogd -L -R 192.168.X.X
S     0  2117     1  1160   688 0:0   12:32 00:00:00 klogd
R     0  2132  1994   928   656 0:0   12:32 00:00:00 dropbear -b /tmp/loginprompt -r /tmp/root/.ssh/ssh_host_rsa_key -p 22
S     0  2133  2132  1164   844 pts0  12:32 00:00:00 -sh
R     0  2693  2133  1160   708 pts0  12:39 00:00:00 ps wl


Thanks


I see you only have one guest net running, I usually have a guest on both radios and it runs stable. Can you check if you also enable a guest network on both radios if the issue is still there, not sure if some status checker does something stupid if you have 2 physical and only one virtual interface. Your output shows memory runs out, no flash chip issue.

_________________
KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
zfil
DD-WRT Novice


Joined: 12 Oct 2014
Posts: 31

PostPosted: Fri Oct 20, 2017 13:35    Post subject: Reply with quote
<Kong> wrote:
I see you only have one guest net running, I usually have a guest on both radios and it runs stable. Can you check if you also enable a guest network on both radios if the issue is still there, not sure if some status checker does something stupid if you have 2 physical and only one virtual interface. Your output shows memory runs out, no flash chip issue.


Thank you Kong, I try that and report back.
slowmath
DD-WRT Novice


Joined: 08 Oct 2017
Posts: 2

PostPosted: Sat Oct 21, 2017 3:35    Post subject: Reply with quote
Router: Asus RT-AC68U B1
Firmware: DD-WRT v3.0-r33525M kongac (10/16/17)
Previous Firmware: DD-WRT v3.0-r32170M kongac (06/11/17)
Kernel: Linux 4.4.92 #454 SMP Mon Oct 16 21:39:05 CEST 2017
Status: Working
Reset: No
Errors: None so far


I'm not sure if I have the date right for the previous firmware version. I forgot to copy it before I flashed the newest version.

I first tried to use ddup --flash-latest at first, but I received the following error:

Code:
root@RT-AC68U:~# ddup --flash-latest
Auto update for the Asus RT-AC68U B1 is currently not supported.


Decided I would try the --flash-remote switch and issued the following command:

Code:
root@RT-AC68U:~# ddup --flash-remote http://www.desipro.de/ddwrt/K3-AC-Arm/TEST/dd-wrt.v24-K3_AC_ARM_STD.bin
Connecting to www.desipro.de (212.227.247.157:80)
fw.bin               100% |********************************************************************| 23084k  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.bin ok.
Are you sure you want to proceeed (y/n) [default=n]:
y
Closing ssh connections now. Flashing now...


My RT-AC68U came back up almost instantly, it seemed. I didn't issue erase nvram and reboot. I had the VPN server running before the firmware update and it appears to be working with no issues on the latest firmware.

This was the first time I've used ddup. What a great utility, Kong! Thanks for your hard work!
pie1394
DD-WRT Novice


Joined: 09 Apr 2014
Posts: 48

PostPosted: Sat Oct 21, 2017 4:07    Post subject: Reply with quote
Anglophile wrote:
Router: Buffalo WZR-1750DHP
Firmware: DD-WRT v3.0-r33525M kongac (10/16/17)
Previous: DD-WRT v3.0-r33435M kongac (10/08/17)
Kernel: Linux 4.4.92 #454 SMP Mon Oct 16 21:39:05 CEST 2017 armv7l
Previous: Linux 4.4.89 #448 SMP Sun Oct 8 10:09:05 CEST 2017 armv7l
Status: No issues per syslog
Reset: No (upgrade via admin pages)
Errors: None in Syslog. First upgrade attempt left Admin screen for Upgrade spinning with upload at 1% for approx 10 minutes. Soft reboot from command line, and second upgrade attempt succeeded.


Mine was upgraded from r33010Mv2 (uptime from 9/17~10/19) and it does not show such issue with the same upgrading procedure. Maybe it is corner case or r33435M specific one if there is no simple way to reproduce it.

Currently the uptime has been 2.5 days with the new version.

As it was mentioned, the OpenVPN's certificate needs to be rebuilt to make it work on the recently new dd-wrt FW. I did that with OpenVPN-2.4.4's tool and it makes the OpenVPN server works again.

_________________
Buffalo WZR-1750DHP
ricc4rdo
DD-WRT Novice


Joined: 01 Mar 2017
Posts: 15
Location: Italy

PostPosted: Sat Oct 21, 2017 9:11    Post subject: Reply with quote
<Kong> wrote:

I see you only have one guest net running, I usually have a guest on both radios and it runs stable. Can you check if you also enable a guest network on both radios if the issue is still there, not sure if some status checker does something stupid if you have 2 physical and only one virtual interface. Your output shows memory runs out, no flash chip issue.


Just for info, 33525M has been running stable for 3 days on my R7000 with 2 physical interfaces and only 1 vap on 5GHz. Used memory is about 19%.
evolvente23
DD-WRT Novice


Joined: 01 May 2014
Posts: 41

PostPosted: Sat Oct 21, 2017 15:45    Post subject: Reply with quote
Router: Netgear R7000
Firmware: DD-WRT v3.0-r33525M kongac (10/16/17)
Kernel: Linux 4.4.92 #454 SMP Mon Oct 16 21:39:05 CEST 2017 armv7l
Status: running for 2 days
Reset: No, ddup --flash-latest only
Errors: None so far.

Upgraded from 28000M. Noticed that minidlna was not working, but it seems that notify_interval was set to 300s in the config file. Quite high in my opinion...
lesteringber
DD-WRT Novice


Joined: 24 Apr 2017
Posts: 18

PostPosted: Sat Oct 21, 2017 17:34    Post subject: Reply with quote
Firmware: DD-WRT v3.0-r33525M kongac (10/16/17)
R7000

I could not get the OVPN GUI to work. My server also is OVPN-2.4.4.

My server had
compress lz4-v2
which is the only item I saw that might affect anything. I added
comp-lzo
to my server.conf.

Now the dd-wrt OVPN GUI works fine.
Goto page Previous  1, 2, 3, 4, 5  Next Display posts from previous:    Page 4 of 5
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