Joined: 08 May 2018 Posts: 14125 Location: Texas, USA
Posted: Sun Aug 09, 2020 19:42 Post subject: New Build - 08-09-2020-r44112
[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 (applicability depends on VPN setup) and GUI toggle. 6920, 6928, 6931, 6932 (WIP 7040)
• In-kernel Samba has been implemented this year and default min/max versions have changed 6954, 6957, with WSD support.
• VAP issue is fixed! For any Wireless Mode, create a VAP and both ath0/ath1 should now function properly.
• Local DNS option removed from Services->DNSMasq in changesets 43080 and 43081; ref: #7092
• DHCP and DNS help (English) updated in 43083; ref: #7091
• WireGuard 1.0.20200712: PBR, Kill Switch, Inbound Firewall, Naming of Peers, Status, Key, Guides. Thanks egc!
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.
Router : Linksys WRT1200AC
I'm experiencing same issue with WiFi(5ghz and 2.4ghz). Connection drops or not responding. I had similar issue with all of August releases.
I had to go back to r43904 to get functional connection.
Router/Version: WRT32x
File/Kernel: DD-WRT v3.0-r44112 std (08/09/20)
Previous/Reset: 06-25-2020-r43516/ (roll back from 08-07-2020-r44085)
Mode/Status: AP mode only, NO DHCP
Issues/Errors:
Everything works fine after web update. Look pretty fast response than r44112.
r44085 looks problematic on wifi connection
ESP8266 need restart WMM support then it is able to connect.
Loading average still 50% load under idle.
Error log:
Jan 1 08:00:12 DD-WRT kern.warn kernel: [ 0.000000] mvebu_mbus: [Firmware Warn]: deprecated mbus-mvebu Device Tree, suspend/resume will not work
Jan 1 08:00:12 DD-WRT kern.warn kernel: [ 0.004100] mvebu-pmsu: CPU hotplug support is currently broken on Armada 38x: disabling
Jan 1 08:00:12 DD-WRT kern.warn kernel: [ 0.004106] mvebu-pmsu: CPU idle is currently broken on Armada 38x: disabling
Jan 1 08:00:12 DD-WRT kern.warn kernel: [ 0.863748] pxa3xx-nand f10d0000.flash: This platform can't do DMA on this device
Jan 1 08:00:12 DD-WRT kern.err kernel: [ 10.921413] sdio platform data not available
Aug 10 14:25:12 DD-WRT daemon.err httpd[1702]: httpd : Request Error Code 408: Unexpected connection close in intitial request
Router/Version: Linksys WRT1900ACS v2
File: ddwrt-linksys-wrt1900acsv2-webflash.bin
Firmware: DD-WRT v3.0-r44112 std (08/09/20) (prev. DD-WRT v3.0-r44048 std (08/02/20))
Kernel: Linux 4.9.232 #2005 SMP Sun Aug 9 04:08:26 +03 2020 armv7l
Mode: Gateway, 2.4G and 5G wifi, Wireguard for external access, WAN to 4G
Reset: No
Status: 4h up, load average 0.00, 0.00, 0.00, Temperatures CPU 80.3 °C / WL0 51.7 °C / WL1 53.6 °C, everything fine, WiFi feels snappier than before.
Router: Linksys WRT1900ACSv2
Firmware: DD-WRT v3.0-r44112 std (08/09/20) prev. r44085
Kernel: Linux 4.9.232 #2005 SMP Sun Aug 9 04:08:26 +03 2020 armv7ll
Browser: Opera Stable 70.0 (Windows 10 64-bit)
Reset: No
Mode:
Ignore WAN DNS, DHCP Server, DHCP-Authoritative, Forced DNS Redirection.
Dnsmasq: Cache DNSSEC data, Validate DNS Replies (DNSSEC), Check unsigned DNS replies, No DNS Rebind.
DNSCrypt2 (2.0.39 Entware)
addn-hosts=Mr. SurprisedItWorks code AdBlock
5 GHz: AP AC/N-Mixed, Channel 161+Lower, Wide HT40, Allow Channel Overlapping, Short Preamble, Short GI, Single User Beamforming.
2.4 GHz: AP NG-Mixed, Channel 5, Full 20 MHz,TurboQAM (QAM256) support, Short Preamble, Short GI.
Security: WPA2 Personal CCMP-128 (AES).
NAS via USB:
/dev/sda - Block device, size 931.5GiB, Partition: 1-Ext4, 2-Ext4 , 3-swap.
Samba shared: Protocol Version SMB 3.00\SMB 3.11
NFS Server shared: Shared the same partitions as in Samba.
Transmission Daemon: Off in GUI, but run from Startup team:
The GUI interface removes the support for "watch-dir" and "watch-dir-enabled" from the file "settings.json". (Ticket #6689)
When you start, a message appears in the log (the work is not affected):
Code:
Aug 10 19:48:31 LinkSYS daemon.err transmission-daemon[2691]: UDP Failed to set receive buffer: requested 4194304, got 360448 (tr-udp.c:97)
Aug 10 19:48:31 LinkSYS daemon.err transmission-daemon[2691]: UDP Failed to set send buffer: requested 1048576, got 360448 (tr-udp.c:105)
Router: WRT3200ACM
THIS BUILD WIFI IS DIRTY. (CONNECTION DROPS)
SAME PROBLEM WITH R44085.
Rolled back to R44048.
R44048 HIGHLY RECOMMENDED.
I probably should have explained better my apologies.
Both r44085, and r44112 are having authentication failed error's in Syslog with Android devices connected to WiFi. All other devices connect without fail. R44048 recommended because it doesn't have the issue.
Router/Version: WRT32x
File/Kernel: DD-WRT v3.0-r44112 std (08/09/20)
Previous/Reset: 06-25-2020-r43516/ (roll back from 08-07-2020-r44085)
Mode/Status: AP mode only, NO DHCP
Issues/Errors:
Everything works fine after web update. Look pretty fast response than r44112.
r44085 looks problematic on wifi connection
ESP8266 need restart WMM support then it is able to connect.
Loading average still 50% load under idle.
Error log:
Jan 1 08:00:12 DD-WRT kern.warn kernel: [ 0.000000] mvebu_mbus: [Firmware Warn]: deprecated mbus-mvebu Device Tree, suspend/resume will not work
Jan 1 08:00:12 DD-WRT kern.warn kernel: [ 0.004100] mvebu-pmsu: CPU hotplug support is currently broken on Armada 38x: disabling
Jan 1 08:00:12 DD-WRT kern.warn kernel: [ 0.004106] mvebu-pmsu: CPU idle is currently broken on Armada 38x: disabling
Jan 1 08:00:12 DD-WRT kern.warn kernel: [ 0.863748] pxa3xx-nand f10d0000.flash: This platform can't do DMA on this device
Jan 1 08:00:12 DD-WRT kern.err kernel: [ 10.921413] sdio platform data not available
Aug 10 14:25:12 DD-WRT daemon.err httpd[1702]: httpd : Request Error Code 408: Unexpected connection close in intitial request
My smartphone cannot get IP in 2.4Ghz but it shown that it is connected to wrt32x in ddwrt. If the phone changed to connect 5Ghz, it is able to get IP without any problem.
I tried to change the DHCP forwarder to DHCP server disable mode. The smartphone is able to get IP in both 2.4Ghz and 5Ghz channel. In the previous build, i was not suffering this problem.
OpenVPN CLIENT seems fine (nordvpn server)
5GHz wpa2 CCMP-128 (AES) Conditional 40MHz Mixed
2.4GHz wpa2 CCMP-128 (AES) Conditional 20MHz N Only
NAS via USB Samba Conditional - Abends with out of memory errors from time to time.
Wifi Stays more or less clean as long as I "keep alive" auto boot every 24 hours
Joined: 04 Aug 2018 Posts: 1444 Location: Appalachian mountains, USA
Posted: Tue Aug 11, 2020 18:38 Post subject:
raywan wrote:
My smartphone cannot get IP in 2.4Ghz but it shown that it is connected to wrt32x in ddwrt. If the phone changed to connect 5Ghz, it is able to get IP without any problem.
What I see in my router (all recent builds) is that DHCP is up and handing out IPs before network time is set. So your phone gets an IP on 2.4GHz just fine. But when network time is set, dnsmasq is restarted and begins the DHCP process again, apparently (if we are to believe the lease list in Status), and all the previously assigned DHCP leases are forgotten. Now it looks like you are connected in wifi, and indeed you can use the phone. If you look in the phone's settings you can find that IP you were handed out early on. But it doesn't show in the lease list in Status. When you disconnect and reconnect to 5GHz, you are talking to the new dnsmasq and get a new lease and it goes into the Status list properly. So it looks like 2.4G has a problem and 5G works, but really if your phone tried to connect on 5G at boot time and you later switched to 2.4, you'd conclude the opposite. Tricky! _________________ 2x Netgear XR500 and 3x Linksys WRT1900ACSv2 on 53544: VLANs, VAPs, NAS, station mode, OpenVPN client (AirVPN), wireguard server (AirVPN port forward) and clients (AzireVPN, AirVPN, private), 3 DNSCrypt providers via VPN.
I'm taking the first steps in using OpenVPN Client and I'm not sure of my conclusions, but it seems to me that the team:
Code:
cat /tmp/resolv.dnsmasq
"Ignore WAN DNS" and "no-resolv" give an unexpected result:
Ignore WAN DNS - Off, Additional Dnsmasq Options On - no-resolv
nameserver 192.168.104.1 - (IP OpenVPN Client)
nameserver 192.168.1.1
nameserver 1.1.1.1 - (Static DNS 1)
nameserver 9.9.9.9 - (Static DNS 2)
nameserver 8.8.8.8 - (Static DNS 3)
nameserver 10.180.90.249 - (IPv4 DNS 4)
nameserver 10.180.90.142 - (IPv4 DNS 5)
Ignore WAN DNS - Off, Additional Dnsmasq Options Off - no-resolv
nameserver 192.168.1.1
nameserver 1.1.1.1 - (Static DNS 1)
nameserver 9.9.9.9 - (Static DNS 2)
nameserver 8.8.8.8 - (Static DNS 3)
nameserver 10.180.90.249 - (IPv4 DNS 4)
nameserver 10.180.90.142 - (IPv4 DNS 5)
Ignore WAN DNS - On, Additional Dnsmasq Options Off - no-resolv
nameserver 192.168.1.1
nameserver 1.1.1.1 - (Static DNS 1)
nameserver 9.9.9.9 - (Static DNS 2)
nameserver 8.8.8.8 - (Static DNS 3)
Joined: 06 Jun 2006 Posts: 7463 Location: Dresden, Germany
Posted: Wed Aug 12, 2020 9:15 Post subject:
ignore wan dns has nothing todo with openvpn. i dont even now how you add your openvpn to the resolv.conf file. ignore wan dns does not ignore the wan supplied dns entries and nothing more. any custom hack of the resolv.conf file is something you have to check
according to the code. openvpn adds a own entry to the resolv file. the problem is you restarted dnsmasq, but not openvpn. so you overwrote all settings, but openvpn was not reconnected so openvpn did not write its own dns again to it. this has nothing todo with the option. but it seems you just changed the options of dnsmasq for testing without taking care that openvpn works indepenend here
i wrote now a workaround for such issues in build 44178. so the openvpn supplied dns gets saved and will be used in case the resolv.conf is rewritten _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Ok.
I assure you that I have not added anything to resolv.conf myself. Rechecked myself, here are my actions:
Enabled OpenVPN Client, Ignore WAN DNS -Off, no-resolv installed, reboot. I see the status of Status-OpenVPN - Client: CONNECTED SUCCESS.
Those. I only change the checkboxes of two options and reboot the router, no more action.
A little clarification: the entry "nameserver 192.168.104.1" appears in "resolv.dnsmasq" if "no-resolv" is enabled.
In the OpenVPN connection log, I see the following entry:
Joined: 18 Mar 2014 Posts: 12837 Location: Netherlands
Posted: Wed Aug 12, 2020 12:06 Post subject:
Adding no-resolv to the DNSMasq options simply tells DNSMasq to ignore resolv.dnsmasq
The file itself is populated by your static DNS servers, the WAN DNS server, unless you enable ignore WAN DNS, and the OpenVPN client adds pushed DNS server on top of the list, unless you specify pull-filter ignore "dhcp-option DNS" in the OpenVPN Additional Config.
One thing I am not sure about is that in recent builds nameserver 192.168.1.1 is added, I checked with my router which has IP address of 192.168.4.1 and even on that router 192.168.1.1 is added on top which is simply a non existent router on my network, so there seems something wrong there _________________ Routers:Netgear R7000, R6400v1, R6400v2, EA6900 (XvortexCFE), E2000, E1200v1, WRT54GS v1.
Install guide R6400v2, R6700v3,XR300:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399 Install guide R7800/XR500:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320614 Forum Guide Lines (important read):https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087