New Build - 04/06/2020 - r42847

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Ralink SoC based Hardware
Author Message
blkt
DD-WRT Guru


Joined: 20 Jan 2019
Posts: 1265

PostPosted: Mon Apr 06, 2020 19:13    Post subject: New Build - 04/06/2020 - r42847 Reply with quote
This thread is for feedback on beta build r42847 for developers and users (configuration, status, errors & logs).
Avoid discussions, create a new thread for specific problems, questions or use search as this is not for support.
Please report hardware model, version, operating & wireless modes along with file name (factory, webflash).


Important: if reporting issues, provide applicable info (syslog output, 'dmesg', 'cat /var/log/messages', serial output etc.)
or place into an SVN ticket. For firewall issues, also provide iptables info ('iptables -L', 'iptables -t nat -L', & the /tmp/.ipt file).
Be sure to include operating and wireless modes (Gateway, AP, CB, etc.) along with any relevant configuration information.

Flashing any beta build assumes you are responsible, have researched, know the risks and recovery methods.
If you don't understand your router, which file or recovery methods do NOT flash this experimental test build.


Downloads: (DD-WRT website) HTTPS & FTP

CLI Flash: 'cd /tmp' then 'wget {file URL}' (or 'curl -k {file URL} -o {file}') with http (not https) or ftp. Then 'write {file} linux'.

Changelogs: SVN changelog since last build: r42819

Notes: 1. CVE-2019-14899 VPN fix from December, since then various revisions including recently 7040.
2. In-kernel Samba has been implemented this year and default min/max versions have changed, with WSD support.

Issues: 1. Client Mode, Client Bridge or WDS + VAP appears to break ath0/ath1 from r42514 onward, possibly earlier (r42287).
2.) There are remaining issues for Samba (for example NTFS), with frequent updates.

Example Template:
Code:
[b]Router/Version: [/b]
[b]Mode: [/b]
[b]Status: [/b]
[b]Errors: [/b]
[b]File: [/b]
[b]Previous: [/b]
[b]Kernel: [/b]
[b]Reset: [/b]
Sponsor
casualtester
DD-WRT User


Joined: 13 Dec 2015
Posts: 314

PostPosted: Sat Apr 11, 2020 3:10    Post subject: Reply with quote
Router: D-Link DIR-878 Rev.A1
File: dlink-dir878-a1-webflash.bin
Firmware: 04-06-2020-r42847
Kernel: Linux 4.14.174 #263 SMP Mon Apr 6 13:42:09 +04 2020 mips
Previous: 03-18-2020-r42729
Reset: Yes
Mode: Gateway|AP
Uptime: 7 days, 6 hrs. Test halted, moving on to testing new firmware(s) release.


Issues/Errors:

*Initial Router Management page suggesting username and password change did not continue on to main menu after waiting several seconds. Refreshing the page permitted continuation to menu.

Details: Firefox ESR 68.7.0 on Win7 Pro 64-bit updated right up to January 2020. Did not bother checking if issue is present in any Linux systems.

Glitch is not new.
Same problem encountered with 03-05-2020-r42617, 03-13-2020-r42681, 03-18-2020-r42729... Even the current 04-10-2020-r42872


Last edited by casualtester on Sun Apr 19, 2020 11:09; edited 5 times in total
AsGF2MX
DD-WRT Novice


Joined: 27 Oct 2006
Posts: 24

PostPosted: Mon Apr 13, 2020 13:12    Post subject: Reply with quote
Router: D-Link DIR-878 Rev.A1
File: dlink-dir878-a1-webflash.bin
Firmware: 04-06-2020-r42847
Kernel: Linux 4.14.174 #263 SMP Mon Apr 6 13:42:09 +04 2020 mips
Previous: r36698
Reset: Yes
Mode: Gateway|AP
Uptime: 4 hours

Issues/Errors:
I'm using PPPoE without issue but when QoS gets enabled, the router LAN interface becomes un-pingable and WiFi is visible but unusable after association (even if I set static IP). Notable WiFi radio indicators start having a ton of activity even if all WiFi devices are off.

QoS tried: HTB/HSFC and all available AQMs.

Only way to get back into the router is to unplug the WAN, reboot and then go in turn off QoS and then resume normal operation.
AsGF2MX
DD-WRT Novice


Joined: 27 Oct 2006
Posts: 24

PostPosted: Mon Apr 13, 2020 16:40    Post subject: Reply with quote
I just got done testing a bit more and it seems at least that I can get back control by waiting a bit after unplugging WAN to force PPPD to go down. Tested 42747 as well and it has the same issue:

When QoS is enabled, iptables drops everything:

Code:
Apr 13 23:19:51 _!!_ daemon.notice pppd[7028]: pppd 2.4.8 started by root, uid 0 
Apr 13 23:19:57 _!!_ kern.info kernel: mtk_soc_eth 1e100000.ethernet eth0: port 4 link up 
Apr 13 23:20:01 _!!_ user.info : dnsmasq : daemon successfully stopped 
Apr 13 23:20:01 _!!_ user.info : dnsmasq : daemon successfully started 
Apr 13 23:20:02 _!!_ kern.info kernel: IMQ driver unloaded successfully. 
Apr 13 23:20:02 _!!_ user.info : wland : daemon successfully started 
Apr 13 23:20:02 _!!_ user.info : wan : WAN is up. IP: 1.2.3.4 
Apr 13 23:20:03 _!!_ user.info : sfe : shortcut forwarding engine successfully stopped 
Apr 13 23:20:03 _!!_ kern.info kernel: IMQ: use 4 as queue number 
Apr 13 23:20:03 _!!_ kern.info kernel: IMQ driver loaded successfully. (numdevs = 2, numqueues = 4, imq_dev_accurate_stats = 1) 
Apr 13 23:20:03 _!!_ kern.info kernel: Hooking IMQ before NAT on PREROUTING. 
Apr 13 23:20:03 _!!_ kern.info kernel: Hooking IMQ after NAT on POSTROUTING. 
Apr 13 23:20:04 _!!_ user.info : process_monitor : daemon successfully stopped 
Apr 13 23:20:04 _!!_ daemon.info process_monitor[1855]: process_monitor : cleanup timers 
Apr 13 23:20:04 _!!_ user.info : process_monitor : successfully started 
Apr 13 23:20:04 _!!_ user.info : ddns : inadyn daemon successfully started 
Apr 13 23:20:04 _!!_ kern.warn kernel: DROP IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=192.168.1.1 DST=192.168.1.1 LEN=64 TOS=0x00 PREC=0x00 TTL=64 ID=16541 DF PROTO=UDP SPT=52094 DPT=53 LEN=44 
Apr 13 23:20:04 _!!_ kern.warn kernel: DROP IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=192.168.1.1 DST=192.168.1.1 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=16542 DF PROTO=UDP SPT=58430 DPT=53 LEN=40 
Apr 13 23:20:04 _!!_ kern.warn kernel: DROP IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=192.168.1.1 DST=192.168.1.1 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=16543 DF PROTO=UDP SPT=58430 DPT=53 LEN=40 
Apr 13 23:20:04 _!!_ kern.warn kernel: DROP IN=br0 OUT= MAC=74:da:da:e3:65:c9:6c:f0:49:e7:7a:0d:08:00 SRC=192.168.1.100 DST=192.168.1.1 LEN=69 TOS=0x00 PREC=0x00 TTL=128 ID=48796 PROTO=UDP SPT=58045 DPT=53 LEN=49 
Apr 13 23:20:04 _!!_ kern.warn kernel: DROP IN=br0 OUT= MAC=74:da:da:e3:65:c9:6c:f0:49:e7:7a:0d:08:00 SRC=192.168.1.100 DST=192.168.1.1 LEN=69 TOS=0x00 PREC=0x00 TTL=128 ID=48797 PROTO=UDP SPT=58045 DPT=53 LEN=49 
Apr 13 23:20:05 _!!_ kern.warn kernel: DROP IN=br0 OUT= MAC=74:da:da:e3:65:c9:6c:f0:49:e7:7a:0d:08:00 SRC=192.168.1.100 DST=192.168.1.1 LEN=60 TOS=0x00 PREC=0x00 TTL=128 ID=48798 PROTO=ICMP TYPE=8 CODE=0 ID=1 SEQ=33983 
Apr 13 23:20:05 _!!_ kern.warn kernel: DROP IN=br0 OUT= MAC=74:da:da:e3:65:c9:6c:f0:49:e7:7a:0d:08:00 SRC=192.168.1.100 DST=192.168.1.1 LEN=52 TOS=0x00 PREC=0x00 TTL=128 ID=48799 DF PROTO=TCP SPT=63735 DPT=443 SEQ=297165044 ACK=0 WINDOW=65535 RES=0x00 SYN URGP=0 OPT 
Apr 13 23:20:05 _!!_ kern.warn kernel: DROP IN=br0 OUT= MAC=74:da:da:e3:65:c9:6c:f0:49:e7:7a:0d:08:00 SRC=192.168.1.100 DST=192.168.1.1 LEN=69 TOS=0x00 PREC=0x00 TTL=128 ID=48800 PROTO=UDP SPT=58045 DPT=53 LEN=49 
Apr 13 23:20:06 _!!_ kern.warn kernel: DROP IN=br0 OUT= MAC=74:da:da:e3:65:c9:6c:f0:49:e7:7a:0d:08:00 SRC=192.168.1.100 DST=192.168.1.1 LEN=52 TOS=0x00 PREC=0x00 TTL=128 ID=48801 DF PROTO=TCP SPT=63735 DPT=443 SEQ=297165044 ACK=0 WINDOW=65535 RES=0x00 SYN URGP=0 OPT 
Apr 13 23:20:07 _!!_ kern.warn kernel: DROP IN=br0 OUT=ppp0 MAC=74:da:da:e3:65:c9:6c:f0:49:e7:7a:0d:08:00 SRC=192.168.1.100 DST=8.8.8.8 LEN=60 TOS=0x00 PREC=0x00 TTL=127 ID=8250 PROTO=ICMP TYPE=8 CODE=0 ID=1 SEQ=33984 
Apr 13 23:20:07 _!!_ kern.warn kernel: DROP IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=192.168.1.1 DST=192.168.1.1 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=16572 DF PROTO=UDP SPT=58430 DPT=53 LEN=40 
Apr 13 23:20:07 _!!_ kern.warn kernel: DROP IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=192.168.1.1 DST=192.168.1.1 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=16573 DF PROTO=UDP SPT=58430 DPT=53 LEN=40 
Apr 13 23:20:07 _!!_ kern.warn kernel: DROP IN=lo OUT= MAC=00:00:00:00:00:00:00:00:00:00:00:00:08:00 SRC=192.168.1.1 DST=192.168.1.1 LEN=64 TOS=0x00 PREC=0x00 TTL=64 ID=16580 DF PROTO=UDP SPT=52094 DPT=53 LEN=44 
Apr 13 23:20:07 _!!_ kern.warn kernel: DROP IN=br0 OUT= MAC=74:da:da:e3:65:c9:6c:f0:49:e7:7a:0d:08:00 SRC=192.168.1.100 DST=192.168.1.1 LEN=69 TOS=0x00 PREC=0x00 TTL=128 ID=48802 PROTO=UDP SPT=58045 DPT=53 LEN=49 
Apr 13 23:20:07 _!!_ kern.warn kernel: DROP IN=br0 OUT= MAC=74:da:da:e3:65:c9:6c:f0:49:e7:7a:0d:08:00 SRC=192.168.1.100 DST=192.168.1.1 LEN=52 TOS=0x00 PREC=0x00 TTL=128 ID=48803 DF PROTO=TCP SPT=63737 DPT=443 SEQ=3979921774 ACK=0 WINDOW=65535 RES=0x00 SYN URGP=0 OP 
Apr 13 23:20:08 _!!_ kern.warn kernel: DROP IN=br0 OUT= MAC=74:da:da:e3:65:c9:6c:f0:49:e7:7a:0d:08:00 SRC=192.168.1.100 DST=192.168.1.1 LEN=52 TOS=0x00 PREC=0x00 TTL=128 ID=48804 DF PROTO=TCP SPT=63735 DPT=443 SEQ=297165044 ACK=0 WINDOW=65535 RES=0x00 SYN URGP=0 OPT 
Apr 13 23:20:08 _!!_ kern.warn kernel: DROP IN=br0 OUT= MAC=74:da:da:e3:65:c9:6c:f0:49:e7:7a:0d:08:00 SRC=192.168.1.100 DST=192.168.1.1 LEN=52 TOS=0x00 PREC=0x00 TTL=128 ID=48805 DF PROTO=TCP SPT=63737 DPT=443 SEQ=3979921774 ACK=0 WINDOW=65535 RES=0x00 SYN URGP=0 OP 
Apr 13 23:20:09 _!!_ daemon.err ntpclient[7448]: Failed resolving address to hostname 2.pool.ntp.org: Try again 
Apr 13 23:20:09 _!!_ daemon.err ntpclient[7448]: Failed resolving server 2.pool.ntp.org: Network is down 


If QoS is disabled

Code:
Apr 13 23:40:05 _!!_ kern.info kernel: mtk_soc_eth 1e100000.ethernet eth0: port 4 link up 
Apr 13 23:40:09 _!!_ kern.info kernel: device vlan2 entered promiscuous mode 
Apr 13 23:40:10 _!!_ kern.info kernel: device vlan2 left promiscuous mode 
Apr 13 23:40:10 _!!_ user.info : pppd : daemon successfully stopped 
Apr 13 23:40:10 _!!_ daemon.info pppd[12432]: Exit. 
Apr 13 23:40:10 _!!_ daemon.notice pppd[12552]: pppd 2.4.8 started by root, uid 0 
Apr 13 23:40:14 _!!_ user.info : dnsmasq : daemon successfully stopped 
Apr 13 23:40:14 _!!_ user.info : dnsmasq : daemon successfully started 
Apr 13 23:40:14 _!!_ user.info : wland : daemon successfully started 
Apr 13 23:40:14 _!!_ user.info : wan : WAN is up. IP: 1.2.3.4 
Apr 13 23:40:15 _!!_ user.info : sfe : shortcut forwarding engine successfully started 
Apr 13 23:40:15 _!!_ user.info : process_monitor : daemon successfully stopped 
Apr 13 23:40:15 _!!_ daemon.info process_monitor[7446]: process_monitor : cleanup timers 
Apr 13 23:40:15 _!!_ user.info : process_monitor : successfully started 
Apr 13 23:40:15 _!!_ user.info : ddns : inadyn daemon successfully started 
Apr 13 23:40:15 _!!_ daemon.debug ntpclient[12652]: Connecting to 2.pool.ntp.org [37.218.240.198] ... 
Apr 13 23:40:15 _!!_ daemon.info ntpclient[12652]: Time set from 2.pool.ntp.org [37.218.240.198]. 
Apr 13 23:40:15 _!!_ daemon.info process_monitor[12650]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22) 
Apr 13 23:40:15 _!!_ daemon.debug process_monitor[12650]: We need to re-update after 3600 seconds 
Apr 13 23:40:15 _!!_ daemon.info process_monitor[12650]: process_monitor : set timer: 3600 seconds, callback: ntp_main() 
Apr 13 23:40:17 _!!_ kern.warn kernel: DROP IN=ppp0 OUT= MAC= SRC=52.221.98.112 DST=1.2.3.4 LEN=132 TOS=0x00 PREC=0x20 TTL=50 ID=59129 DF PROTO=TCP SPT=5223 DPT=37486 SEQ=3547582466 ACK=4195839379 WINDOW=118 RES=0x00 ACK PSH URGP=0 OPT (0101080AAC0918BB009E1B5F) 
Apr 13 23:40:17 _!!_ kern.warn kernel: DROP IN=ppp0 OUT= MAC= SRC=52.221.98.112 DST=1.2.3.4 LEN=83 TOS=0x00 PREC=0x20 TTL=50 ID=59130 DF PROTO=TCP SPT=5223 DPT=37486 SEQ=3547582546 ACK=4195839379 WINDOW=118 RES=0x00 ACK PSH URGP=0 OPT (0101080AAC0918BB009E1B5F) 
Apr 13 23:40:17 _!!_ kern.warn kernel: DROP IN=ppp0 OUT= MAC= SRC=52.221.98.112 DST=1.2.3.4 LEN=52 TOS=0x00 PREC=0x20 TTL=50 ID=59131 DF PROTO=TCP SPT=5223 DPT=37486 SEQ=3547582577 ACK=4195839379 WINDOW=118 RES=0x00 ACK FIN URGP=0 OPT (0101080AAC0918BB009E1B5F) 
Apr 13 23:40:17 _!!_ kern.warn kernel: DROP IN=ppp0 OUT= MAC= SRC=52.221.98.112 DST=1.2.3.4 LEN=52 TOS=0x00 PREC=0x20 TTL=50 ID=59132 DF PROTO=TCP SPT=5223 DPT=37486 SEQ=3547582577 ACK=4195839379 WINDOW=118 RES=0x00 ACK FIN URGP=0 OPT (0101080AAC0918D9009E1B5F) 
Apr 13 23:40:17 _!!_ daemon.debug ntpclient[12614]: Connecting to 2.pool.ntp.org [37.218.240.198] ... 
Apr 13 23:40:17 _!!_ daemon.info ntpclient[12614]: Time set from 2.pool.ntp.org [37.218.240.198]. 
Apr 13 23:40:17 _!!_ kern.warn kernel: DROP IN=ppp0 OUT= MAC= SRC=52.221.98.112 DST=1.2.3.4 LEN=163 TOS=0x00 PREC=0x20 TTL=50 ID=59133 DF PROTO=TCP SPT=5223 DPT=37486 SEQ=3547582466 ACK=4195839379 WINDOW=118 RES=0x00 ACK PSH FIN URGP=0 OPT (0101080AAC09191A009E1B 
Apr 13 23:40:18 _!!_ kern.warn kernel: DROP IN=ppp0 OUT= MAC= SRC=52.221.98.112 DST=1.2.3.4 LEN=163 TOS=0x00 PREC=0x20 TTL=50 ID=59134 DF PROTO=TCP SPT=5223 DPT=37486 SEQ=3547582466 ACK=4195839379 WINDOW=118 RES=0x00 ACK PSH FIN URGP=0 OPT (0101080AAC09199D009E1B 
Apr 13 23:40:19 _!!_ kern.warn kernel: DROP IN=ppp0 OUT= MAC= SRC=52.221.98.112 DST=1.2.3.4 LEN=163 TOS=0x00 PREC=0x20 TTL=50 ID=59135 DF PROTO=TCP SPT=5223 DPT=37486 SEQ=3547582466 ACK=4195839379 WINDOW=118 RES=0x00 ACK PSH FIN URGP=0 OPT (0101080AAC091AA2009E1B 
Apr 13 23:40:33 _!!_ kern.warn kernel: DROP IN=ppp0 OUT= MAC= SRC=52.221.98.112 DST=1.2.3.4 LEN=163 TOS=0x00 PREC=0x20 TTL=50 ID=59138 DF PROTO=TCP SPT=5223 DPT=37486 SEQ=3547582466 ACK=4195839379 WINDOW=118 RES=0x00 ACK PSH FIN URGP=0 OPT (0101080AAC0928E8009E1B


One more item: tc output when QOS disabled:
=============================
Code:
qdisc noqueue 0: dev lo root refcnt 2
qdisc fq_codel 0: dev eth0 root refcnt 2 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 256Kb ecn
qdisc noqueue 0: dev vlan1 root refcnt 2
qdisc noqueue 0: dev vlan2 root refcnt 2
qdisc noqueue 0: dev br0 root refcnt 2
qdisc noqueue 0: dev ath0 root refcnt 2
qdisc noqueue 0: dev ath1 root refcnt 2
qdisc sfq 0: dev ppp0 root refcnt 2 limit 127p quantum 1514b flows 128/1024


I'm a bit puzzled as to why there is fq_codel exists on the eth0 yet SFQ exists on the PPP0 interface. Am I misreading something?
kernel-panic69
DD-WRT Guru


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

PostPosted: Mon Apr 13, 2020 17:55    Post subject: Reply with quote
Please post your QoS configuration.
_________________
Official Forum Rules, Guidelines, and Helpful InformationFirmware FAQInstallation WikiWhere Do I Download Firmware?
DON'T use Chromium-based browsersRTFM/STFW - TL;DR is NOT an excuse. • Why Should I Care What Color the Bikeshed Is?
Please DO NOT PM me with questions; Ask in the forum.

---------------------------------------------------------

Linux User #377467 counter.li.org / linuxcounter.net
AsGF2MX
DD-WRT Novice


Joined: 27 Oct 2006
Posts: 24

PostPosted: Mon Apr 13, 2020 23:35    Post subject: Reply with quote
Here it is. I have one more finding: LAN and WiFi MAC are the same. When I set ath0 to disabled, WAN dropped and although router LAN was pingable via wired static IP, all services and DHCP/DNS were dead (connection refused for ssh/telnet). Had to do factory recovery as reset button doesn't work.

Note that I tried all combinations of HTB/HSFC and disciplines. This is the current one for reference.
kernel-panic69
DD-WRT Guru


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

PostPosted: Tue Apr 14, 2020 0:41    Post subject: Reply with quote
Ok. I see no sign of you rebooting after enabling or disabling QoS. You should try that as well as ensuring SFE is disabled when you enable QoS.
_________________
Official Forum Rules, Guidelines, and Helpful InformationFirmware FAQInstallation WikiWhere Do I Download Firmware?
DON'T use Chromium-based browsersRTFM/STFW - TL;DR is NOT an excuse. • Why Should I Care What Color the Bikeshed Is?
Please DO NOT PM me with questions; Ask in the forum.

---------------------------------------------------------

Linux User #377467 counter.li.org / linuxcounter.net
AsGF2MX
DD-WRT Novice


Joined: 27 Oct 2006
Posts: 24

PostPosted: Sun Apr 19, 2020 13:38    Post subject: Reply with quote
I tried multiple times but at the end of the night I couldn't regain control of my router so I failed to get the logs.

Having said that I also found the WiFi throughput on this version isn't great. I didn't reply as my ISP just flipped us over to FTTH. 1G

Going to stop testing and move to 42914.
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Ralink 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 cannot attach files in this forum
You cannot download files in this forum