Joined: 08 May 2018 Posts: 14244 Location: Texas, USA
Posted: Fri May 22, 2020 14:09 Post subject: New Build - 05-22-2020 - r43217
[WARNING]: This thread is only for feedback on this beta release for developers and the community's benefit.
DO NOT flash this beta release unless you understand the risks involved and specific device recovery methods.
Avoid discussions! Create threads for questions, general problems or use search; this thread is not for support.
Please list router model & revision, operating & wireless mode(s) and exact filename/firmware image flashed.
Notes:
• CVE-2019-14899 VPN fix from December, since then various revisions including recently 7040.
• In-kernel Samba has been implemented this year and default min/max versions have changed, with WSD support.
• VAP issue is fixed! For any Wireless Mode, create a VAP and both ath0/ath1 should now function properly.
• WireGuard 1.0 & tools! New GUI Tunnel options since r42872; now with key management! Setup guides: Client & Server by egc
• Local DNS option removed from Services->DNSMasq in changesets 43080 and 43081; ref: #7092
• DHCP and DNS help (English) updated in 43083; ref: #7091
Issues:
• There may be remaining issues for Samba (for example NTFS), with frequent updates.
Important:
• If reporting issues provide applicable info: 'dmesg', 'cat /tmp/var/log/messages', syslog/serial output, strace etc.
• For firewall issues provide 'iptables -L', 'iptables -t nat -L' and the /tmp/.ipt file.
• Search existing SVN tickets before opening a new one. Before reporting, reset and manually setup (no nvram backup).
• Be sure to include operating and wireless modes (Gateway, AP, CB, etc.) along with relevant configuration information.
Firmware: DD-WRT v3.0-r43217 std (05/22/20)
Time: 21:19:30 up 9 min, load average: 0.00, 0.01, 0.00
IPv4: 79..251
IPv6:2a02:fe00:0
Router Model:Linksys WRT1900ACS v2
Firmware Version:DD-WRT v3.0-r43217 std (05/22/20)
Kernel Version:Linux 4.9.224 #1802 SMP Fri May 22 01:18:55 +03 2020 armv7l
Connection Type:PPPoE
Mode/Status:AP 2.4Ghz and 5Ghz
5Ghz-mod AP - Mode Mixed- channel 36- VHT80 Mhz -TX Power 3-Radio Scheduling ON - ALL OK!
2.4Ghz - mod AP - Mode Mixed- channel 9 - Dinamic 20/40 Mhz -TX Power 3-Radio Scheduling ON - ALL OK!
Port Range Forwarding-all ok
Issues/Errors: No
Previous/Reset:I made the switch from partition two with the previous version r43192, I made the switch with saving the settings on partition one, I didn't reset anything!
Browser waterfox the latest version. _________________ Internet provider https://en.wikipedia.org/wiki/RCS_%26_RDS 1Gbps
WDR3600 rev.1.5 - DD-Wrt
Linksys WRT1900ACS v.2 DD-Wrt/-OpenWrt
this one for me hasnt been so wifi problematic like the last 2 builds. other then that all is working well for my setup _________________ Downloads:
ftp site: ftp://ftp.dd-wrt.com/betas/2021 SVN Timeline:
https://svn.dd-wrt.com/timeline Commands: Misc: sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas
samba: { sleep 30; stopservice samba3; startservice samba3; } &
WRT1900ACv1: WIFI: 2.4ghz: NG-mixed, 20mhz channel width, channel follows AP, WPA2-CCMP-128.
WIFI: 5ghz: AC/N mixed, 40mhz channel width, channel 100+upper, WPA2-CCMP-128.
Misc Info: WPA2 Personal: "CCMP-128 (AES)" Static IP's VIA Mac+Host, SFE Enabled, No Rebind, Strict, no-resolv. NOTE: this is now just a wireless access point so to speak but all settings still apply to what ever wireless person connects.
Sometimes when I make some changes and press the save button and apply no longer allocate ipv6!
ipv6 type DHCPV6 with prefix!
it assigns me ipv6, only after i come back and give a connection again to ipv6, this problem is old in the DDWRT web interface!
May 23 22:43:26 DD-WRT kern.info kernel: [21695.536539] br0: port 3(ath1) entered blocking state
May 23 22:43:26 DD-WRT kern.info kernel: [21695.541536] br0: port 3(ath1) entered forwarding state
May 23 22:43:26 DD-WRT kern.info kernel: [21695.546731] IPv6: ADDRCONF(NETDEV_CHANGE): ath1: link becomes ready
May 23 22:43:27 DD-WRT user.info : bridge : interface ath1 successfully added to bridge br0
May 23 22:43:27 DD-WRT kern.info kernel: [21695.645909] device eth0 entered promiscuous mode
May 23 22:43:27 DD-WRT kern.info kernel: [21696.019373] mvneta f1034000.ethernet eth0: configuring for fixed link mode
May 23 22:43:27 DD-WRT kern.info kernel: [21696.027133] device eth0 left promiscuous mode
May 23 22:43:27 DD-WRT kern.info kernel: [21696.032924] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
May 23 22:43:27 DD-WRT kern.info kernel: [21696.039466] mvneta f1034000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
May 23 22:43:27 DD-WRT kern.info kernel: [21696.047485] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
May 23 22:43:27 DD-WRT daemon.notice pppd[8934]: pppd 2.4.8 started by root, uid 0
May 23 22:43:27 DD-WRT user.info : ppp_redial : redial process successfully started
May 23 22:43:27 DD-WRT user.info : dnsmasq : daemon successfully stopped
May 23 22:43:28 DD-WRT user.info : cron : daemon successfully started
May 23 22:43:28 DD-WRT cron.info cron[9102]: (CRON) STARTUP (fork ok)
May 23 22:43:30 DD-WRT user.info : httpd : daemon successfully stopped
May 23 22:43:30 DD-WRT daemon.info httpd[8639]: httpd : httpd server shutdown
May 23 22:43:30 DD-WRT daemon.info httpd[9108]: httpd : httpd server started at port 80
May 23 22:43:30 DD-WRT user.info : httpd : http daemon successfully started
May 23 22:43:31 DD-WRT user.info : dnsmasq : daemon successfully stopped
May 23 22:43:31 DD-WRT daemon.info dnsmasq[8956]: exiting on receipt of SIGTERM
May 23 22:43:31 DD-WRT daemon.info dnsmasq[9128]: started, version 2.81 cachesize 1500
May 23 22:43:31 DD-WRT daemon.info dnsmasq[9128]: compile time options: IPv6 GNU-getopt no-DBus no-UBus no-i18n no-IDN DHCP DHCPv6 no-Lua no-TFTP no-conntrack no-ipset no-auth DNSSEC loop-detect no-inotify no-dumpfile
May 23 22:43:31 DD-WRT daemon.info dnsmasq-dhcp[9128]: DHCP, IP range 192.168.1.100 -- 192.168.1.149, lease time 1d
May 23 22:43:31 DD-WRT daemon.info dnsmasq[9128]: using only locally-known addresses for domain test
May 23 22:43:31 DD-WRT daemon.info dnsmasq[9128]: using only locally-known addresses for domain onion
May 23 22:43:31 DD-WRT daemon.info dnsmasq[9128]: using only locally-known addresses for domain localhost
May 23 22:43:31 DD-WRT daemon.info dnsmasq[9128]: using only locally-known addresses for domain local
May 23 22:43:31 DD-WRT daemon.info dnsmasq[9128]: using only locally-known addresses for domain invalid
May 23 22:43:31 DD-WRT daemon.info dnsmasq[9128]: using only locally-known addresses for domain bind
May 23 22:43:31 DD-WRT daemon.info dnsmasq[9128]: reading /tmp/resolv.dnsmasq
May 23 22:43:31 DD-WRT daemon.info dnsmasq[9128]: using only locally-known addresses for domain test
May 23 22:43:31 DD-WRT user.info : dnsmasq : daemon successfully started
May 23 22:43:31 DD-WRT daemon.info dnsmasq[9128]: using only locally-known addresses for domain onion
May 23 22:43:31 DD-WRT daemon.info dnsmasq[9128]: using only locally-known addresses for domain localhost
May 23 22:43:31 DD-WRT daemon.info dnsmasq[9128]: using only locally-known addresses for domain local
May 23 22:43:31 DD-WRT daemon.info dnsmasq[9128]: using only locally-known addresses for domain invalid
May 23 22:43:31 DD-WRT daemon.info dnsmasq[9128]: using only locally-known addresses for domain bind
May 23 22:43:31 DD-WRT daemon.info dnsmasq[9128]: using nameserver 193.1#53
May 23 22:43:31 DD-WRT daemon.info dnsmasq[9128]: using nameserver 213..1#53
May 23 22:43:31 DD-WRT daemon.info dnsmasq[9128]: read /etc/hosts - 2 addresses
May 23 22:43:31 DD-WRT user.info : wland : daemon successfully stopped
May 23 22:43:31 DD-WRT user.info : wland : daemon successfully started
May 23 22:43:31 DD-WRT user.info : wan : WAN is up. IP: 8 15
May 23 22:43:31 DD-WRT daemon.info radvd[9134]: version 2.18 started
May 23 22:43:31 DD-WRT user.info : radvd : RADVD daemon successfully started
May 23 22:43:32 DD-WRT user.info : vpn modules : vpn modules successfully unloaded
May 23 22:43:32 DD-WRT user.info : vpn modules : nf_conntrack_proto_gre successfully loaded
May 23 22:43:32 DD-WRT user.info : vpn modules : nf_nat_proto_gre successfully loaded
May 23 22:43:32 DD-WRT user.info : vpn modules : nf_conntrack_pptp successfully loaded
May 23 22:43:32 DD-WRT user.info : vpn modules : nf_nat_pptp successfully loaded
May 23 22:43:32 DD-WRT user.info : sfe : shortcut forwarding engine successfully started
May 23 22:43:32 DD-WRT user.info : process_monitor : daemon successfully stopped
May 23 22:43:32 DD-WRT daemon.info process_monitor[5623]: process_monitor : cleanup timers
May 23 22:43:32 DD-WRT user.info : process_monitor : successfully started
May 23 22:43:34 DD-WRT user.info : radvd : daemon successfully stopped
May 23 22:43:34 DD-WRT daemon.warn radvd[9135]: exiting, 1 sigterm(s) received
May 23 22:43:34 DD-WRT daemon.info radvd[9135]: sending stop adverts
May 23 22:43:34 DD-WRT daemon.info radvd[9135]: removing /var/run/radvd.pid
May 23 22:43:34 DD-WRT daemon.info radvd[9135]: returning from radvd main
May 23 22:43:34 DD-WRT daemon.info radvd[9283]: version 2.18 started
May 23 22:43:34 DD-WRT user.info : radvd : RADVD daemon successfully started
May 23 22:43:35 DD-WRT daemon.info dnsmasq[9128]: reading /tmp/resolv.dnsmasq
May 23 22:43:35 DD-WRT daemon.info dnsmasq[9128]: using only locally-known addresses for domain test
May 23 22:43:35 DD-WRT daemon.info dnsmasq[9128]: using only locally-known addresses for domain onion
May 23 22:43:35 DD-WRT daemon.info dnsmasq[9128]: using only locally-known addresses for domain localhost
May 23 22:43:35 DD-WRT daemon.info dnsmasq[9128]: using only locally-known addresses for domain local
May 23 22:43:35 DD-WRT daemon.info dnsmasq[9128]: using only locally-known addresses for domain invalid
May 23 22:43:35 DD-WRT daemon.info dnsmasq[9128]: using only locally-known addresses for domain bind
May 23 22:43:35 DD-WRT daemon.info dnsmasq[9128]: using nameserver 19.1#53
May 23 22:43:35 DD-WRT daemon.info dnsmasq[9128]: using nameserver 2131#53
May 23 22:43:35 DD-WRT daemon.info dnsmasq[9128]: using nameserver 2a01#53
May 23 22:43:35 DD-WRT daemon.info dnsmasq[9128]: using nameserver 2a02:8::1#53
May 23 22:43:35 DD-WRT daemon.debug ntpclient[9280]: Connecting to 2.pool.ntp.org [93.190.144.3] ...
May 23 22:43:35 DD-WRT daemon.info ntpclient[9280]: Time set from 2.pool.ntp.org [93.190.144.3].
May 23 22:43:35 DD-WRT daemon.info process_monitor[9279]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
May 23 22:43:35 DD-WRT daemon.debug process_monitor[9279]: We need to re-update after 3600 seconds
May 23 22:43:35 DD-WRT daemon.info process_monitor[9279]: process_monitor : set timer: 3600 seconds, callback: ntp_main()
May 23 22:43:36 DD-WRT daemon.info hostapd: ath1: STA 1 MLME: auth request, signal -51 (Accepted)
May 23 22:43:36 DD-WRT daemon.info hostapd: ath1: STA 1 IEEE 802.11: authenticated
May 23 22:43:36 DD-WRT daemon.info hostapd: ath1: STA 10:08:c1:8d:3c:49 MLME: assoc request, signal -49 (Accepted)
May 23 22:43:36 DD-WRT daemon.info hostapd: ath1: STA 1 IEEE 802.11: associated (aid 1)
May 23 22:43:36 DD-WRT daemon.info hostapd: ath1: STA 10RADIUS: starting accounting session 810C8C639BCB09F2
May 23 22:43:36 DD-WRT daemon.info hostapd: ath1: STA 1 WPA: pairwise key handshake completed (RSN) _________________ Internet provider https://en.wikipedia.org/wiki/RCS_%26_RDS 1Gbps
WDR3600 rev.1.5 - DD-Wrt
Linksys WRT1900ACS v.2 DD-Wrt/-OpenWrt
@oliver44:
Those warnings do not appear in my log, they are related to "no dns rebind" setting for dnsmasq, since a possible vulnerability was described years ago as dns-rwbind attack.
Your device thinks "omg someone tries this attack" and therefore mentions it in its log.
Regarding your second post, currently no ipv6 available here to test, your logs look fine; but did you edit your public ip and dns server?
@Zyxx
Hello, i did not edit any ip and dns server,i left everything the basic settings, i did not make any changes. _________________ Internet provider https://en.wikipedia.org/wiki/RCS_%26_RDS 1Gbps
WDR3600 rev.1.5 - DD-Wrt
Linksys WRT1900ACS v.2 DD-Wrt/-OpenWrt
Joined: 30 May 2017 Posts: 582 Location: Rural Manitoba
Posted: Sun May 24, 2020 3:46 Post subject:
Earlier today all Routers r43192 -> r43217
Had a lot of strange activity throughout the day. My 5Ghz WDS stations 1900 V1's would periodically drop and re-connect. Had numerous other re-connections all over.
Eventually lost Internet connection even though the Status -> Wan indicated connection.
Rather than try to figure it all out, I simply changed partitions on all routers back to r43192. _________________ Starlink & DSL -> TPLink TL-R470T+
->
WRT3200acm Master WDS 5GHz 80Mhz CH 100 (+6) r55819
Ath1 2.4Ghz Disabled
99 Static Leases
ExpressVPN
WRT3200acm r55819 WDS Station 5Ghz
Ath1 AP N/G Mixed Channel 11 HT40
WRT1900Ac V1 5Ghz r55819 WDS Station
(Defective, no 2.4Ghz but 5Ghz works great)
WRT1900AC V1 5Ghz AC 80Mhz WDS Station r55819
2.4Ghz AP Ch1 HT20 Mixed
WRT1900ACS SPARE r54914
WRT1900AC SPARE r54914
WRT1900AC V1 5Ghz AC 80Mhz WDS-AP r55819
2.4Ghz AP Ch1 HT20 Mixed
WRT54G DD-WRT v3.0-r37305 micro AP CH 6 Mixed - Not in use
The only odd thing is that it runs a bit warmer than usual, at 74C (the CPU) compared to previous builds where it ran around 68C, but that's no biggie. _________________ Router: Linksys WRT3200ACM WLAN0 and 1 have same SSID
88W8964 802.11ac WLAN0 Mode AP VHT80 80MHz Mixed Mode Channel and Extension Channel Auto Extension LL-6
88W8964 802.11ac WLAN1 Mode AP 20 MHz Mixed Mode Channel Auto
SD8887 802.11ac disabled but visible on GUI and CLI
TX Power 18 dBm
Antenna Gain 0 dBi
U-APSD (Automatic Power Save)Enabled
Protection Mode None
RTS Threshold Disabled
Short Preamble Disabled
Short GI Enabled
Single User Beamforming Enabled
Multi User Beamforming Enabled
AP Isolation Disabled
Beacon Interval 100
DTIM Interval 2
WMM Support Enabled
Radar Detection Disabled
ScanList default
Sensitivity Range (ACK Timing) 500 (Default: 500 meters)
Max Associated Clients 256 (Default: 256 Clients)
Minimum Signal for authenticate -128
Minimum Signal for connection -128
Poll Time for signal lookup 10
Amount of allowed low signals 3
Wireless security is WPA2 Personal CCMP-128 only
QAM256 is on
Joined: 12 Dec 2007 Posts: 780 Location: Pittsburgh, PA USA
Posted: Sun May 24, 2020 15:43 Post subject:
oliver44 wrote:
Sometimes when I make some changes and press the save button and apply no longer allocate ipv6!
ipv6 type DHCPV6 with prefix!
it assigns me ipv6, only after i come back and give a connection again to ipv6, this problem is old in the DDWRT web interface!
I've been seeing similar issues on my WRT1900AC, with a IPV6 6in4 tunnel through Hurricane. Have to hit apply on the IPV6 tab after any reboot or configuration change. I rolled back to 42557 and that version seems to be stable. _________________ __________________________
Netgear R7800
DD-WRT v3.0 STD
Linksys WRT1900AC
DD-WRT v3.0 STD
Hi dpp3530,
I'm glad that someone can confirm this problem, it persists on all variants of DD-WRT, especially when you make changes in the tab with settings for wi-fi, Services, if you want to make changes after configuring the settings you will see that you have this problem! _________________ Internet provider https://en.wikipedia.org/wiki/RCS_%26_RDS 1Gbps
WDR3600 rev.1.5 - DD-Wrt
Linksys WRT1900ACS v.2 DD-Wrt/-OpenWrt
@Zyxx
Hello, i did not edit any ip and dns server,i left everything the basic settings, i did not make any changes.
Hmm, ok. I had to ask since those entries look strange to me, maybe only ipv6 related?
Code:
May 23 22:43:31 DD-WRT daemon.info dnsmasq[9128]: using nameserver 193.1#53
May 23 22:43:31 DD-WRT daemon.info dnsmasq[9128]: using nameserver 213..1#53
May 23 22:43:31 DD-WRT user.info : wan : WAN is up. IP: 8 15
Either way, when your Router GUI does not behave, check if problem occur with other browser (not chromium based), too.
No: Blame google
Yes: You need to open a ticket with a description of the problem.
Joined: 08 May 2018 Posts: 14244 Location: Texas, USA
Posted: Sun May 24, 2020 20:35 Post subject:
Zyxx wrote:
oliver44 wrote:
@Zyxx
Hello, i did not edit any ip and dns server,i left everything the basic settings, i did not make any changes.
Hmm, ok. I had to ask since those entries look strange to me, maybe only ipv6 related?
Code:
May 23 22:43:31 DD-WRT daemon.info dnsmasq[9128]: using nameserver 193.1#53
May 23 22:43:31 DD-WRT daemon.info dnsmasq[9128]: using nameserver 213..1#53
May 23 22:43:31 DD-WRT user.info : wan : WAN is up. IP: 8 15
Either way, when your Router GUI does not behave, check if problem occur with other browser (not chromium based), too.
No: Blame google
Yes: You need to open a ticket with a description of the problem.
Router/Version: Linksys WRT3200ACM
Firmware: DD-WRT v3.0-r43217 std (05/22/20)
File/Kernel: Linux 4.9.224 #1802 SMP Fri May 22 01:18:55 +03 2020 armv7l
Previous/Reset: DD-WRT v3.0-r43192 std (05/19/20)
Mode/Status: Main router for home
Reset: No
Uptime: 8 min
Issues/Errors: Not sure, working but I got errors on system logs
May 24 23:15:07 DD-WRT daemon.warn dnsmasq[1533]: nameserver 192.168.0.1 refused to do a recursive query
May 24 23:15:07 DD-WRT daemon.warn dnsmasq[1533]: possible DNS-rebind attack detected: wpad.Home
May 24 23:15:09 DD-WRT daemon.warn dnsmasq[1533]: possible DNS-rebind attack detected: wpad.Home
May 24 23:15:09 DD-WRT daemon.warn dnsmasq[1533]: possible DNS-rebind attack detected: wpad.Home
May 24 23:15:13 DD-WRT daemon.warn dnsmasq[1533]: possible DNS-rebind attack detected: wpad.Home
May 24 23:15:21 DD-WRT daemon.warn dnsmasq[1533]: possible DNS-rebind attack detected: wpad.Home
May 24 23:15:21 DD-WRT daemon.warn dnsmasq[1533]: possible DNS-rebind attack detected: wpad.Home
May 24 23:15:21 DD-WRT daemon.warn dnsmasq[1533]: possible DNS-rebind attack detected: wpad.Home
May 24 23:15:28 DD-WRT daemon.warn dnsmasq[1533]: possible DNS-rebind attack detected: wpad.Home
May 24 23:15:53 DD-WRT daemon.warn dnsmasq[1533]: possible DNS-rebind attack detected: wpad.Home
May 24 23:16:28 DD-WRT daemon.warn dnsmasq[1533]: possible DNS-rebind attack detected: wpad.Home
May 24 23:16:58 DD-WRT daemon.warn dnsmasq[1533]: possible DNS-rebind attack detected: wpad.Home
May 24 23:17:54 DD-WRT daemon.warn dnsmasq[1533]: possible DNS-rebind attack detected: wpad.Home
May 24 23:19:07 DD-WRT daemon.warn dnsmasq[1533]: possible DNS-rebind attack detected: wpad.Home
May 24 23:20:33 DD-WRT daemon.warn dnsmasq[1533]: possible DNS-rebind attack detected: wpad.Home _________________ Router Name: DD-WRT
Router Model: Linksys WRT3200ACM