Joined: 26 Mar 2013 Posts: 1748 Location: Hung Hom, Hong Kong
Posted: Tue Sep 06, 2022 3:25 Post subject: DD-WRT BS build 50057 and Asus RT-N18U
Router/Version:Asus RT-N18U (rev. A1)
Firmware: DD-WRT v3.0-r50057 std (09/03/22)
Kernel: Linux 4.4.302-st25 #7239 Sat Sep 3 03:51:17 +07 2022 armv7l
Previous: DD-WRT v3.0-r49792 std (08/20/22)
Mode: WAN @ DHCP, Wireless @ APf
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: Factory RESET during firmware upgrade
File:https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2022/09-03-2022-r50057/asus-rt-n18u/
Warning(s)/Error(s)
1. Enabling CTF broke port-forwarding, which was expected.
2. DD-WRT didn't scan for /jffs/etc/unbound.conf in USB drives when USB drive was mounted as /jffs during sysinit. However, MiniDLNA could detect and load /jffs/etc/minidlna.conf from USB storage.
3. MSTPD reported multiple entries of the same error, not seen in previous builds:
Code:
# grep -i err /var/log/messages | grep mstpd
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: error, ethtool_get_speed_duplex: Cannot get speed/duplex for eth1: Not supported
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: error, ethtool_get_speed_duplex: Cannot get speed/duplex for eth1: Not supported
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: error, ethtool_get_speed_duplex: Cannot get speed/duplex for eth1: Not supported
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: error, ethtool_get_speed_duplex: Cannot get speed/duplex for eth1: Not supported
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: error, ethtool_get_speed_duplex: Cannot get speed/duplex for eth1: Not supported
Jan 1 08:00:33 RT-N18U-HST daemon.info mstpd[634]: error, ethtool_get_speed_duplex: Cannot get speed/duplex for eth1: Not supported
Sep 6 10:59:16 RT-N18U-HST daemon.info mstpd[634]: error, ethtool_get_speed_duplex: Cannot get speed/duplex for eth1: Not supported
All messages about MSTPD:
Code:
# grep -i mstpd /var/log/messages
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: create_br: Add bridge br0
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: create_if: Add iface vlan1 as port#1 to bridge br0
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: set_if_up: Port vlan1 : up
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: create_if: Add iface eth1 as port#2 to bridge br0
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: set_if_up: Port eth1 : up
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: error, ethtool_get_speed_duplex: Cannot get speed/duplex for eth1: Not supported
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: set_br_up: br0 was down. Set up
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: MSTP_OUT_set_state: br0:vlan1:0 entering blocking state
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: MSTP_OUT_set_state: br0:eth1:0 entering blocking state
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: MSTP_OUT_flush_all_fids: br0:vlan1:0 Flushing forwarding database
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: MSTP_OUT_flush_all_fids: br0:eth1:0 Flushing forwarding database
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: MSTP_OUT_set_state: br0:vlan1:0 entering learning state
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: MSTP_OUT_set_state: br0:eth1:0 entering learning state
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: set_if_up: Port eth1 : up
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: error, ethtool_get_speed_duplex: Cannot get speed/duplex for eth1: Not supported
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: set_if_up: Port vlan1 : up
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: set_if_up: Port vlan1 : up
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: set_if_up: Port eth1 : up
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: error, ethtool_get_speed_duplex: Cannot get speed/duplex for eth1: Not supported
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: set_if_up: Port vlan1 : up
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: set_if_up: Port eth1 : up
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: error, ethtool_get_speed_duplex: Cannot get speed/duplex for eth1: Not supported
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: MSTP_OUT_set_state: br0:vlan1:0 entering blocking state
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: MSTP_OUT_set_state: br0:eth1:0 entering blocking state
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: MSTP_OUT_set_ageing_time: br0:vlan1 Setting new ageing time to 15
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: MSTP_OUT_set_ageing_time: br0:eth1 Setting new ageing time to 15
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: set_if_up: Port vlan1 : up
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: set_if_up: Port eth1 : up
Jan 1 08:00:13 RT-N18U-HST daemon.info mstpd[634]: error, ethtool_get_speed_duplex: Cannot get speed/duplex for eth1: Not supported
Jan 1 08:00:28 RT-N18U-HST daemon.info mstpd[634]: MSTP_OUT_set_ageing_time: br0:vlan1 Setting new ageing time to 300
Jan 1 08:00:28 RT-N18U-HST daemon.info mstpd[634]: MSTP_OUT_set_ageing_time: br0:eth1 Setting new ageing time to 300
Jan 1 08:00:33 RT-N18U-HST daemon.info mstpd[634]: MSTP_OUT_set_state: br0:vlan1:0 entering learning state
Jan 1 08:00:33 RT-N18U-HST daemon.info mstpd[634]: MSTP_OUT_set_state: br0:eth1:0 entering learning state
Jan 1 08:00:33 RT-N18U-HST daemon.info mstpd[634]: set_if_up: Port vlan1 : up
Jan 1 08:00:33 RT-N18U-HST daemon.info mstpd[634]: set_if_up: Port eth1 : up
Jan 1 08:00:33 RT-N18U-HST daemon.info mstpd[634]: error, ethtool_get_speed_duplex: Cannot get speed/duplex for eth1: Not supported
Sep 6 10:59:16 RT-N18U-HST daemon.info mstpd[634]: MSTP_OUT_set_state: br0:vlan1:0 entering forwarding state
Sep 6 10:59:16 RT-N18U-HST daemon.info mstpd[634]: MSTP_OUT_set_state: br0:eth1:0 entering forwarding state
Sep 6 10:59:16 RT-N18U-HST daemon.info mstpd[634]: MSTP_OUT_set_ageing_time: br0:eth1 Setting new ageing time to 15
Sep 6 10:59:16 RT-N18U-HST daemon.info mstpd[634]: MSTP_OUT_set_ageing_time: br0:vlan1 Setting new ageing time to 15
Sep 6 10:59:16 RT-N18U-HST daemon.info mstpd[634]: set_if_up: Port vlan1 : up
Sep 6 10:59:16 RT-N18U-HST daemon.info mstpd[634]: set_if_up: Port eth1 : up
Sep 6 10:59:16 RT-N18U-HST daemon.info mstpd[634]: error, ethtool_get_speed_duplex: Cannot get speed/duplex for eth1: Not supported
Sep 6 10:59:31 RT-N18U-HST daemon.info mstpd[634]: MSTP_OUT_set_ageing_time: br0:vlan1 Setting new ageing time to 300
Sep 6 10:59:31 RT-N18U-HST daemon.info mstpd[634]: MSTP_OUT_set_ageing_time: br0:eth1 Setting new ageing time to 300
edit:
4. I did NOT enable any VPN services, but VPN modules were still loaded. Should I worry about security and backdoor?
5. Some errors seen when reloading the firewall, and VPN modules were loaded as well. Removing the 4 VPN modules using rmmod did NOT affect internet access.
Router/Version: Asus RT-N66U
File: dd-wrt.v24-50057_NEWD-2_K3.x-big-RT-N66U.trx
Firmware: DD-WRT v3.0-r50057 big (09/03/22) (prev. DD-WRT v3.0-r49866 big (08/24/22))
Kernel: Linux 4.4.302-st25 #18432 Sat Sep 3 05:05:49 +07 2022 mips
Mode: Gateway, SFE disabled, Wifi disabled, WAN disabled, Wireguard Endpoint for external VPS, connected via LAN to WRT1900ACS v2, Keep Alive reboot 6:05 in the morning
Reset: No
Status: Installed at release, ok.
Router/Version: Asus RT-AC88U/Asus RT-AC88U
File DD-WRT v3.0-r50057 std (09/03/22)
Kernel: Linux 4.4.302-st25 #7240 SMP Sat Sep 3 03:58:21 +07 2022 armv7l
Gateweay (new hardware 2020) Previous/Reset: 49866/no
Mode/Status: gateway, DDNS, Samba, DHCP static leases, MAC filter, port forwarding
Issues/Errors: Lost the 2.4GHz WIFI interface again and wl0 is now the 5GHz interfaces. Configuration is partially messed up since parameters don't fit anymore. After the update (and may be some more traffic data) i hit the 64Kb NVRAM size again. After removing traffic info from 2020 and 2021 the router is working normal again. There is definitely a bug with NVRAM handling if exceeding 64kb.
I also have still random reboots on my both RT-AC88U routers with all previous versions. The new hardware (gateway router) much more often than the other one. This happens 3-5 times the week.
Switch ports 1-4 are still reversed in the web interface. _________________ 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: Cisco Linksys E2000 H.W. Rev 1 https://forum.dd-wrt.com/wiki/index.php/Linksys_E2000
File/Kernel: dd-wrt.v24-50057_NEWD-2_K3.x_mega-e2000.bin / Linux 4.4.302-st25
Previous/Reset: dd-wrt.v24-49212_NEWD-2_K3.x_mega-e2000.bin / yes
Mode/Status: Wifi Off + PPTP Client (Internal Network) + StrongVPN WireGuard Client (WAN) + Not used as primary WAN/NAT Router / working
Issues/Errors: After flashing / 30-30-30 reset; Set up all my configs & saved. Unplugged from testing/setup bench and plugged into my network. All configs wiped. Set up configs again. It worked fine for about 5 days and it just stopped working. I plugged in my bench spare that still had 49212 on it and my internet is back to normal.
50057 seems to boot up a lot slower. Overall didn't work as well.
I have two of these e2000 routers. One as a spare & to test new builds/configs. I use one behind my primary NAT router to put my whole network on WireGuard VPN with Strong VPN configs.
Other internal routers connect to LAN ports wired only.
I will try another new build later to see if there is a more stable one. I apologize, I did not save the logs. I couldn't log in the web interface around the 5th day.
I always lose all settings after a firmware upgrade.
Probably because I always do a erase nvram command before reboot (seeing it advised somewhere).
Yup, don't do that unless you have issues afterward or for large builds jumps. (Ref: #4.3)
Black Tiger wrote:
In the beginning of this thread I see this command:
Code:
CLI Flash: 'cd /tmp' then 'wget {file URL}' (http only) or 'curl -O {file URL}' (http, https, ftp). 'write {file} linux' then 'reboot'.
However, in the installation guide for future upgrades, there it says there to write to linux2 first.
Is it still best to write to linux2 first and afterwards to linux? Or has the writing command to linux2 become obsolete? Since I don't see it in the mentioned command here in this thread.
You're referring to the EA6400 wiki, right:
Linksys_EA6400 wrote:
5d. Flash it to linux2 (TAKES ABOUT 5 MINUTES!!) with Putty (Command is: mtd -f write firmware.bin linux2)
I know it wasn't clear [updated] but those instructions are only for initial flash from Linksys OEM firmware. One would normally just GUI flash from then on (per 'Method 1'), and you don't need to reset.
The build thread CLI flash info is from the Installation wiki. The EA6400 wiki also [now] references how to utilize the linux partitions [on the EA6900 wiki...] here. E.g. for those paranoid, one could flash to the 'other' partition when you upgrade, and switch to it... in the event of an issue it would be easy to switch back. And welcome, btw. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Future Firmware Upgrades
The Firmware Upgrade tab in the web GUI may not be reliable for this router. To upgrade, follow the procedure outlined above (note that you should probably always have SSHd enabled on this device):
Which gave me the impression that it should better be done via console than via the GUI.
Quote:
One would normally just GUI flash from then on (per 'Method 1'), and you don't need to reset. Smile
Oke, I didn't do that because of the above statement in the forum guide.
I will try via the GUI next time. Thank you!
Joined: 08 May 2018 Posts: 13898 Location: Texas, USA
Posted: Thu Sep 15, 2022 15:46 Post subject:
The Linksys EA series webUI flash has to be done twice if you want the same version on both:
tedm wrote:
Router/Version: Broadcom Northstar (Linksys EA6200)
-----
Issues/Errors: Usual Linksys EA6xxx stuff
-----
You have to flash it 2 times since there's 2 partitions. The router does properly switch over to the "backup" partition after flashing it the first time. (well it did for me)
