Joined: 26 Mar 2013 Posts: 1748 Location: Hung Hom, Hong Kong
Posted: Thu Apr 28, 2022 12:42 Post subject: DD-WRT BS build 48741 and Asus RT-N18U
Router/Version:Asus RT-N18U (rev. A1)
Firmware: DD-WRT v3.0-r48741 std (04/26/22)
Kernel: Linux 4.4.302 #5764 Tue Apr 26 05:53:44 +07 2022 armv7l
Previous: DD-WRT v3.0-r48432 std (03/01/22)
Mode: WAN @ DHCP, Wireless @ AP
Status: Working (
Not 24/7; Not using IPv6, VAP, VPN, CTF, FA;
DDNS OK; Port-forwarding OK;
Using NAS (ksmbd, minidlna, lighttpd), USB (jffs, opt), Recursive DNS Unbound;
Entware core (CPU: armv71) installed without problem
)
Reset: NO reset during firmware upgrade but cold boot
File:https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2022/04-26-2022-r48741/asus-rt-n18u/
Warning(s)/Error(s)
Code:
~# lighttpd -f /tmp/lighttpd.conf
2022-04-28 20:36:50: (configfile.c.353) Warning: please add "mod_authn_file" to server.modules list in lighttpd.conf. A future release of lighttpd 1.4.x will not automatically load mod_authn_file and lighttpd will fail to start up since your lighttpd.
onf uses auth.backend = "plain".
2022-04-28 20:36:50: (configfile.c.514) Warning: "mod_compress" is DEPRECATED and has been replaced with "mod_deflate". A future release of lighttpd 1.4.x will not contain mod_compress and lighttpd may fail to start up
2022-04-28 20:36:50: (network.c.419) can't bind to socket: 0.0.0.0:443: Address in use
Sysinit tried to start the same set of processes multiple times,
including the USB Scrtipt (/tmp/.rc.usb). Notice that
Interestingly, the Startup Script (/tmp/rc.startup) was an exception.
Code:
Jan 1 08:00:12 RT-N18U-HST user.info : [klogd] : daemon successfully started
Jan 1 08:00:12 RT-N18U-HST user.info : [resetbutton] : resetbutton daemon successfully started
Jan 1 08:00:12 RT-N18U-HST user.info : [bridge] : bridge br0 successfully added
Jan 1 08:00:12 RT-N18U-HST user.info : [bridge] : interface vlan1 successfully added to bridge br0
Jan 1 08:00:13 RT-N18U-HST user.info : [bridge] : interface eth1 successfully added to bridge br0
Jan 1 08:00:13 RT-N18U-HST user.info : [klogd] : kernel log daemon successfully stopped
Jan 1 08:00:14 RT-N18U-HST user.info : [sfe] : shortcut forwarding engine successfully stopped
Jan 1 08:00:14 RT-N18U-HST user.info : [syslogd] : syslog daemon successfully stopped
Jan 1 08:00:14 RT-N18U-HST user.info : [klogd] : daemon successfully started
Jan 1 08:00:16 RT-N18U-HST user.info : [wland] : daemon successfully started
Jan 1 08:00:16 RT-N18U-HST user.info : [minidlna] : DLNA Media Server successfully started
Jan 1 08:00:17 RT-N18U-HST user.info : [dnsmasq] : daemon successfully started
Jan 1 08:00:18 RT-N18U-HST user.info : [vpn modules] : vpn modules successfully unloaded
Jan 1 08:00:19 RT-N18U-HST user.info : [httpd] : http daemon successfully started
Jan 1 08:00:21 RT-N18U-HST user.info : [sfe] : shortcut forwarding engine successfully started
Jan 1 08:00:23 RT-N18U-HST user.info : [sfe] : shortcut forwarding engine successfully started
Jan 1 08:00:24 RT-N18U-HST user.info : [unbound] : recursive dns resolver daemon successfully started
Jan 1 08:00:29 RT-N18U-HST user.info : [sfe] : shortcut forwarding engine successfully stopped
Jan 1 08:00:29 RT-N18U-HST user.info : [sfe] : shortcut forwarding engine successfully started
Jan 1 08:00:31 RT-N18U-HST user.info : [wland] : daemon successfully stopped
Jan 1 08:00:31 RT-N18U-HST user.info : [wland] : daemon successfully started
Jan 1 08:00:31 RT-N18U-HST user.info : [dnsmasq] : daemon successfully stopped
Jan 1 08:00:31 RT-N18U-HST user.info : [dnsmasq] : daemon successfully started
Jan 1 08:00:31 RT-N18U-HST user.info : [unbound] : daemon successfully stopped
Jan 1 08:00:32 RT-N18U-HST user.info : [unbound] : recursive dns resolver daemon successfully started
Jan 1 08:00:32 RT-N18U-HST user.info : [sfe] : shortcut forwarding engine successfully stopped
Jan 1 08:00:32 RT-N18U-HST user.info : [vpn modules] : vpn modules successfully unloaded
Jan 1 08:00:33 RT-N18U-HST user.info : [sfe] : shortcut forwarding engine successfully started
Jan 1 08:00:34 RT-N18U-HST user.info : [sfe] : shortcut forwarding engine successfully started
Jan 1 08:00:34 RT-N18U-HST user.info : [process_monitor] : successfully started
Jan 1 08:00:34 RT-N18U-HST user.info : [ddns] : inadyn daemon successfully started
Apr 28 19:58:14 RT-N18U-HST daemon.info process_monitor[1925]: cyclic NTP Update success (servers 118.143.17.83)
Apr 28 19:58:15 RT-N18U-HST user.info : [sfe] : shortcut forwarding engine successfully stopped
Apr 28 19:58:15 RT-N18U-HST user.info : [sfe] : shortcut forwarding engine successfully started
Apr 28 19:58:15 RT-N18U-HST user.info : [sfe] : shortcut forwarding engine successfully stopped
Apr 28 19:58:16 RT-N18U-HST user.info : [nas] : NAS lan (wl0 interface) successfully started
Apr 28 19:58:17 RT-N18U-HST user.info : [vpn modules] : vpn modules successfully unloaded
Apr 28 19:58:17 RT-N18U-HST user.info : [sfe] : shortcut forwarding engine successfully started
Apr 28 19:58:17 RT-N18U-HST user.info : [nas] : daemon successfully stopped
Apr 28 19:58:17 RT-N18U-HST user.info : [nas] : NAS lan (wl0 interface) successfully started
Apr 28 19:58:17 RT-N18U-HST user.info : [httpd] : daemon successfully stopped
Apr 28 19:58:17 RT-N18U-HST user.info : [httpd] : http daemon successfully started
Apr 28 19:58:17 RT-N18U-HST user.info : [resetbutton] : daemon successfully stopped
Apr 28 19:58:18 RT-N18U-HST user.info : [resetbutton] : resetbutton daemon successfully started
Apr 28 19:58:19 RT-N18U-HST user.info : [sfe] : shortcut forwarding engine successfully started
Apr 28 19:58:19 RT-N18U-HST user.info : [unbound] : daemon successfully stopped
Apr 28 19:58:19 RT-N18U-HST user.info : [unbound] : recursive dns resolver daemon successfully started
Apr 28 19:58:19 RT-N18U-HST user.info : [unbound] : daemon successfully stopped
Apr 28 19:58:19 RT-N18U-HST user.info : [unbound] : recursive dns resolver daemon successfully started
Apr 28 19:58:19 RT-N18U-HST user.info : [process_monitor] : daemon successfully stopped
Apr 28 19:58:20 RT-N18U-HST user.info : [process_monitor] : successfully started
Apr 28 19:58:21 RT-N18U-HST user.notice root: changmw: rc.startup
Apr 28 19:58:21 RT-N18U-HST user.info : [wsdd2] : windows service discovery daemon successfully stopped
Apr 28 19:58:21 RT-N18U-HST user.info : [minidlna] : DLNA Media Server successfully stopped
Apr 28 19:58:21 RT-N18U-HST user.info : [ksmbd.mountd] : samba daemon successfully stopped
Apr 28 19:58:21 RT-N18U-HST user.info : [lighttpd] : daemon successfully stopped
Apr 28 19:58:24 RT-N18U-HST user.notice root: changmw: rc.usb
Apr 28 19:58:24 RT-N18U-HST user.notice root: changmw: rc.usb
Apr 28 19:58:26 RT-N18U-HST user.info : [minidlna] : DLNA Media Server successfully started
Apr 28 19:58:27 RT-N18U-HST user.info : [minidlna] : DLNA Media Server successfully stopped
Apr 28 19:58:27 RT-N18U-HST user.info : [minidlna] : DLNA Media Server successfully stopped
Apr 28 19:58:27 RT-N18U-HST user.info : [minidlna] : DLNA Media Server successfully started
Apr 28 19:58:27 RT-N18U-HST user.info : [minidlna] : DLNA Media Server successfully started
Firmware Size
From 30515200 (b.31277) to 24711168 (b.33555) = -5804032 bytes
From 24711168 (b.33555) to 27054080 (b.34929) = 2342912 bytes
From 27054080 (b.34929) to 26640384 (b.35531) = -413696 bytes
From 26640384 (b.35531) to 25022464 (b.36995) = -1617920 bytes
From 25022464 (b.36995) to 25427968 (b.37961) = 405504 bytes
... <snipped> ....
From 25870336 (b.46733) to 25153536 (b.46979) = -716800 bytes
From 25153536 (b.46979) to 25145344 (b.47000) = -8192 bytes
From 25145344 (b.47000) to 25145344 (b.47090) = 0 bytes
From 25145344 (b.47090) to 25149440 (b.47206) = 4096 bytes
From 25149440 (b.47206) to 25153536 (b.47282) = 4096 bytes
From 25153536 (b.47282) to 25128960 (b.47474) = -24576 bytes
From 25128960 (b.47474) to 25128960 (b.47581) = 0 bytes
From 25128960 (b.47581) to 25157632 (b.47692) = 28672 bytes
From 25157632 (b.47692) to 25939968 (b.47822) = 782336 bytes
From 25939968 (b.47822) to 25985024 (b.48081) = 45056 bytes
From 25985024 (b.48081) to 26087424 (b.48432) = 102400 bytes
From 26087424 (b.48432) to 26476544 (b.48741) = 389120 bytes
_________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
I still have random reboots on my both RT-AC88U. This happen with all builds more or less i tested during the last months. Is there any more information i can provide to troubleshoot this issue. One is the gateway router using DHCP, MAC filtering, DynDNS and port forwarding. Thes second one is an simple access point with MAC filtering. I actually have an external syslog server to log the info for both of them. _________________ Asus AC-RT88U (Gateway, asus_rt-ac88u-firmware_52459.trx)
Asus AC-RT88U (AP, asus_rt-ac88u-firmware_52459.trx)
Asus AC-RT68U (AP, asus_rt-ac68u-firmware_52459.trx)
Asus AC-RT66U (AP, dd-wrt-52459-Asus_RT-AC66U.trx)
Linksys E3000 (AP, dd-wrt.v24-52459_NEWD-2_K3.x_mega-e3000.bin)
Linksys E4200 V2 (openwrt-18.06.5-kirkwood-linksys_viper-squashfs-sysupgrade.bin) not used at the moment
Joined: 18 Mar 2014 Posts: 12487 Location: Netherlands
Posted: Fri Apr 29, 2022 7:42 Post subject:
mj666 wrote:
I still have random reboots on my both RT-AC88U. This happen with all builds more or less i tested during the last months. Is there any more information i can provide to troubleshoot this issue. One is the gateway router using DHCP, MAC filtering, DynDNS and port forwarding. Thes second one is an simple access point with MAC filtering. I actually have an external syslog server to log the info for both of them.
Im not using the experimental driver. Anyhow it was the same when i used this in the past. Attached you can find the syslog's for both servers of the last days. I was experiencing a few reboots on both of the routers. Many thanks for looking into this.
egc wrote:
mj666 wrote:
I still have random reboots on my both RT-AC88U. This happen with all builds more or less i tested during the last months. Is there any more information i can provide to troubleshoot this issue. One is the gateway router using DHCP, MAC filtering, DynDNS and port forwarding. Thes second one is an simple access point with MAC filtering. I actually have an external syslog server to log the info for both of them.
_________________ Asus AC-RT88U (Gateway, asus_rt-ac88u-firmware_52459.trx)
Asus AC-RT88U (AP, asus_rt-ac88u-firmware_52459.trx)
Asus AC-RT68U (AP, asus_rt-ac68u-firmware_52459.trx)
Asus AC-RT66U (AP, dd-wrt-52459-Asus_RT-AC66U.trx)
Linksys E3000 (AP, dd-wrt.v24-52459_NEWD-2_K3.x_mega-e3000.bin)
Linksys E4200 V2 (openwrt-18.06.5-kirkwood-linksys_viper-squashfs-sysupgrade.bin) not used at the moment
Router/Version: R7000
File/Kernel: DD-WRT v3.0-r48741 std (04/26/22)
Kernel Version: Linux 4.4.302 #5760 SMP Mon Apr 25 03:33:59 +07 2022 armv7l
Previous/Reset: r48540 / No Reset, Remote CLI Update
Mode/Status: GW & AP / Working Well
Issues/Errors: none / none
Services Used: DHCP WAN,IPv6-6to4,NTP,WG Client,VLANx,BRx,SSH,Syslog,Cron,USB Storage,Entware DNSCrypt v2.1.1
Services Disabled: SFE,QoS,ttraff,Telnet,NAS.Samba,YAMon3.4.6
Running over 38 hours.
OffSite #2
Router/Version: R7000
File/Kernel: DD-WRT v3.0-r48741 std (04/26/22)
Kernel Version: Linux 4.4.302 #5760 SMP Mon Apr 25 03:33:59 +07 2022 armv7l
Previous/Reset: r48540 / No Reset, Remote CLI Update
Mode/Status: GW & AP / Working Well
Issues/Errors: none /none
Services Used: DHCP WAN,IPv6-PD,NTP,VLANx,BRx,SSH,Syslog,Cron,USB Storage,Entware DNSCrypt v2.1.1
Services Disabled: SFE,QoS,ttraff,Telnet,NAS.Samba,YAMon3.4.6
Running over 16 hours.
Thank-you BrianSlyer for your Great Work and everyone else who makes DD-WRT Great on the Forum! _________________ Home Network on Telus 1Gb PureFibre - 10GbE Copper Backbone
2x R7800 - Gateway & WiFi & 3xWireGuard - DDWRT r54203 Std k6.1
Off Site 1
R7000 - Gateway & WiFi & WireGuard - DDWRT r54079 Std
E3000 - Station Bridge - DDWRT r49626 Mega K4.4
Off Site 2
R7000 - Gateway & WiFi - DDWRT r52330 Std
E2000 - Wired ISP IPTV PVR Blocker - DDWRT r35531
Router: Netgear R7450
File/Kernel: r7450-webflash.bin
Previous/Reset: r48646 std / no
Mode/Status: Gateway / working
Issues/Errors: wireless devices having this issue where when loading a webpage or YouTube Video it will hang for 2-3 seconds in the beginning then will finish loading with no issues. Happens whether it is connected on 2.4 or 5 GHz. Tried rebooting the router and modem to make sure it wasn't a simple issue but still happening.
Router: Netgear R7450
File/Kernel: r7450-webflash.bin
Previous/Reset: r48646 std / no
Mode/Status: Gateway / working
Issues/Errors: wireless devices having this issue where when loading a webpage or YouTube Video it will hang for 2-3 seconds in the beginning then will finish loading with no issues. Happens whether it is connected on 2.4 or 5 GHz. Tried rebooting the router and modem to make sure it wasn't a simple issue but still happening.
Wifi clients lose internet after a few hours and cannot access router web GUI. Wifi signal strength remains strong and the router GUI shows the clients as connected. Ethernet clients maintain internet and LAN access.
I have no idea why dmesg is showing wl0 since I have 2.4 Ghz disabled. I only use 5 Ghz (wl1).
tail of dmesg:
Code:
CONSOLE: 026754.361 wl0: Proxy STA 6a:9b:26:ed:ed:d5 link is already gone !!??
device oet1 entered promiscuous mode
br0: port 2(eth2) entered forwarding state
br0: port 1(vlan1) entered forwarding state
CONSOLE: 026760.021 wl0: link up (wl0)
FS-Cache: Loaded
CONSOLE: 026761.392 wl0: link up (wl0)
SMB2 server sent bad RFC1001 len 254 not 202
nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
br0: received packet on eth2 with own address as source address
dhd_flow_rings_delete_for_peer: ifindex 0
CONSOLE: 029481.054 wl0: Proxy STA 9c:b6:d0:ec:84:6f link is already gone !!??
br0: received packet on eth2 with own address as source address
dhd_flow_rings_delete_for_peer: ifindex 0
CONSOLE: 031458.044 wl0: Proxy STA 9c:b6:d0:ec:84:6f link is already gone !!??
dhd_flow_rings_delete_for_peer: ifindex 0
dhd_flow_rings_delete_for_peer: ifindex 0
I suspect there is a hardware defect with my R7000P since I have erased nvram twice (and configured from scratch) and I still experience the same issue where wireless clients lose internet access after a few hours. I do not suspect that this is caused by dd-wrt.
^ I second this. Same router, and had some wifi peformance issues that I can't recall right now with a previous build (we discussed them at the time). I rolled back, but pretty sure my router now has AIDS from "uninvited surprise fun time" . Time for a reflash with newer firmware, I think?
. Time for a reflash with newer firmware, I think? 