Joined: 16 Nov 2015 Posts: 6447 Location: UK, London, just across the river..
Posted: Tue Jul 14, 2020 13:46 Post subject: New Build 07-14-2020-r43800
[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.20200623: 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.
Joined: 05 Oct 2008 Posts: 666 Location: Helsinki, Finland / nr. Alkmaar, Netherlands
Posted: Tue Jul 14, 2020 15:35 Post subject:
There's a small problem on the Administration page:
Dynamic Host Configuration Protocol
DHCP Status
DHCP Server
Enabled
Start IP Address
192.168.5.10
End IP Address
192.168.5.9,
Client Lease Expiration
1440 min
The end IP address should end in 29 in my case.
I don't know when this error came about. I haven't noticed DHCP to not work as intended. I have two devices which get their IP from the address space defined above.
The settings page has the correct values:
start IP 192.168.5.10 and 20 max users.
Router: Netgear R7800
Firmware: DD-WRT v3.0-r43800 std (07/14/20)
Kernel: Linux 4.9.230 #601 SMP Thu Jul 9 19:40:35 +03 2020 armv7l
Status: Working
Reset: No
Previous: 43720
Errors: No
Temperatures : CPU 55.113 °C / ath0 52 °C / ath1 52 °C
Working very well :
Router mode : DHCP
SFE Enable STP Disable
DNSMasq
Cache DNSSEC data
Validate DNS Replies (DNSSEC)
Check unsigned DNS replies
Local DNS
No DNS Rebind
ath0, ath1
Vpn (OpenVPN Client)
After that SMB seemed to work. I rebooted the PC, browsed to the share and clocked on the IP address part and got a new failure on Windows Explorer: "The array bounds are invalid"
Nothing on Syslog.
SMB seems to somewhat work even with the errors.
Joined: 05 Oct 2008 Posts: 666 Location: Helsinki, Finland / nr. Alkmaar, Netherlands
Posted: Tue Jul 14, 2020 16:45 Post subject:
There seems to be a new problem with DDNS:
Tue Jul 14 19:39:54 2020: I:INADYN: IP address for alias 'Axxxxx.no-ip.org' needs update to '82.xxx.xxx.xxx'
Tue Jul 14 19:39:59 2020: INADYN:IP: Error '0x16' resolving host name 'dynupdate.no-ip.com'
Tue Jul 14 19:39:59 2020: W:'RC_IP_INVALID_REMOTE_ADDR' (0x12) updating the IPs. (it 7)
I get these every 10 minutes now. The problem may have been present for a while, because my public IP doesn't change often (only when I change the router).
However, it used to work without errors before.
I have always had external IP check off. I'll try now with it enabled.
That didn't help:
Tue Jul 14 19:46:14 2020: INADYN: Started 'INADYN Advanced version 1.96-ADV' - dynamic DNS updater.
Tue Jul 14 19:46:14 2020: INADYN: IP read from cache file is '82.xxx.xxx.xxx'. No update required.
Tue Jul 14 19:46:20 2020: INADYN:IP: Error '0x16' resolving host name 'ip1.dynupdate.no-ip.com'
Tue Jul 14 19:46:20 2020: W: DYNDNS: Error 'RC_IP_INVALID_REMOTE_ADDR' (0x12) when talking to IP server
Tue Jul 14 19:46:20 2020: W:'RC_IP_INVALID_REMOTE_ADDR' (0x12) updating the IPs. (it 0)
It says no update required, but then it tries to update anyway ...
For good measure I have whitelisted dynupdate.no-ip.com, even though I haven't seen it getting blocked by PiHole.
In fact, I cannot even find dynupdate.no-ip.com in the query log. Odd.
After disabling the external check and applying settings I get this:
Tue Jul 14 19:51:16 2020: INADYN: Started 'INADYN Advanced version 1.96-ADV' - dynamic DNS updater.
Tue Jul 14 19:51:16 2020: INADYN: IP read from cache file is '82.xxx.xxx.xxx'. No update required.
Tue Jul 14 19:51:16 2020: I:INADYN: IP address for alias 'Axxxxxx.no-ip.org' needs update to '82.xxx.xxx.xxx'
Tue Jul 14 19:51:21 2020: INADYN:IP: Error '0x16' resolving host name 'dynupdate.no-ip.com'
Tue Jul 14 19:51:21 2020: W:'RC_IP_INVALID_REMOTE_ADDR' (0x12) updating the IPs. (it 0)
On my laptop, which is a client of the R7800 router, I get this:
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Tue Jul 14, 2020 17:21 Post subject:
A reset won't fix the status page. @ArjenR49: If the router is not resolving DNS, then there is a problem on the WAN side, unless you are forcing the router to use it's own resolver and then forwarding the queries upstream to OpenDNS, Cloudflare, Google, etc. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Joined: 06 Feb 2020 Posts: 167 Location: Maharashtra, India
Posted: Tue Jul 14, 2020 17:25 Post subject:
Router/Version: Netgear R7800
Firmware: DD-WRT v3.0-r43800 std (07/14/20)
Kernel: Linux 4.9.230 #601 SMP Thu Jul 9 19:40:35 +03 2020 armv7l
File/Upload: dd-wrt-webupgrade.bin / Upload using SSH
Mode: Gateway/AP
Reset: No
Previous: DD-WRT v3.0-r43762 std (07/12/20) - test build
Setup Using: 2.4 GHz, 5.0 GHz, IPv4, DNSMasq, USB, NTP TimeSync, wireguard
Status: Working Fine including smbd
Thank you BrainSlayer for Wonderful firmware.
Thanks kernel-panic & egc for your help in forums. and egc's wireguard setup guide is one to preserve for long, it helped me setup wireguard in minutes.
Joined: 05 Oct 2008 Posts: 666 Location: Helsinki, Finland / nr. Alkmaar, Netherlands
Posted: Tue Jul 14, 2020 19:50 Post subject:
kernel-panic69 wrote:
A reset won't fix the status page. @ArjenR49: If the router is not resolving DNS, then there is a problem on the WAN side, unless you are forcing the router to use it's own resolver and then forwarding the queries upstream to OpenDNS, Cloudflare, Google, etc.
It appears that this problem has been in existence in my setup for a number of weeks at least. I reverted to 43516 and a corresponding settings backup.
Still the same problem with dig dynupdate.no-ip.com. I mean, it's like you indicated, the router can't resolve this (ssh'd into router), but both PiHole server and laptop can.
Still, some time ago I also tested dig commands in all three devices, laptop, pihole server and router. They all resolved the domain in the dig command back then. Just the source:
;; Query time: 255 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Tue Jul 14 22:41:20 EEST 2020
;; MSG SIZE rcvd: 80
differed between these three devices. I was curious about that back then.
I have no idea yet what broke DNS resolving on the router alone. I'll try and restore older and olxer setting backups. They do not differ all that much and I can perhaps deduct what stopped the router from resolving a name. It is supposed to use the PiHole just as everything else.
