Router/Version: Netgear R9000
File/Kernel: Linux 4.9.331 #652 SMP Sat Oct 29 15:01:44 +07 2022 armv7l
Previous/Reset: - / No
Mode/Status: RIP2 router, 2.4Ghz/5.8Ghz radio's active
Issues/Errors: None _________________ Several NetGears with Broadcom and with Atheros
Mode: RIP2 Router, 2G/5G radios are active, Routed WiFi multiple SSID's/separated by IP subnets.
Remote Syslog, NTP, IPv6 management, WireGuard routed Site-2-Site VPNs
Router/Version: R9000
Mode/Status: WDS Master with 4 R7800 WDS stations and 1 R9000 WDS station (some with virtual APs)
Issues/Errors: None
Odd that the names of the client WDS stations are intermittent while all other clients (wifi PCs, wifi laptops, tablets, cellphones, and other devices) don't show a name on the Status->Wireless->Wireless Nodes->Access Point & Node - it has been this way a long time.
Joined: 06 Jun 2020 Posts: 22 Location: Oak Harbor, Washington, USA
Posted: Wed Nov 02, 2022 23:32 Post subject: DDNS, DynDNS, r50786: 400 Bad Request
I'm unsure if this DDNS issue is new, but since there's a lot of chatter about DDNS this week, I looked at Setup->DDNS, and in the Service Status section, I see "Your browser sent a request that this server could not understand". Looking up "400 Bad Request":
Quote:
400 Bad Request response status code indicates that the server cannot or will not process the request due to something that is perceived to be a client error (for example, malformed request syntax, invalid request message framing, or deceptive request routing)
Enable Service = DynDNS.org
Wildcard = [unchecked]
Use External IP Check = No
Use SSL = No
This DDNS config has been working for about two years. Should I be concerned, or is this cosmetic (or an old status)? _________________ Regards,
Al Savage
----------------
R7800 x2
Joined: 16 Mar 2019 Posts: 353 Location: Szczecin, Poland EU
Posted: Thu Nov 03, 2022 12:32 Post subject: New Build - 11/02/2022 - r50786
Router/Version: TP-Link TL-WDR3600 v1.5
Kernel: Linux 3.10.108-d11 #120442 Wed Nov 2 06:05:18 +07 2022 mips
Reset: No
Mode: Internet gateway, WIFI 5GHz, dnsmasq, firewall
Issues: some yellow marked events in logs
Status: Working
Uptime: more than 24h
Device working acceptable. I'm attach logs for fix possible issues.
Using the web UI, I am unable to save any change to Hostname field; I can edit it, but then selecting either Save or Apply Settings, the page refreshes to the previous values.
Per the dd-wrt wiki, I have been using the "-a" syntax to indicate multiple DDNS host names, and currently Hostname is set to:
Code:
site1.dyndns.org -a site2.dyndns.org -a site3.dyndns.org -a site4.dyndns.org -a site5.dyndns.org
I've confirmed that changes are not saved by using SSH and
Code:
root@R7800-1:~# cat /tmp/ddns/inadyn.conf
. . . which shows the old Hostname values, and confirms that the format stored in inadyn.conf appears to match that github example.
Are you advising that I abandon using the web UI to reconfigure DDNS (ie use vi or a local edit and SCP)?
Is there a way to trigger inadyn to attempt an update, so I can see fresher output from it (other than setting Force Update Interval to '1' and waiting a day)?
Finally, should I move this to a separate thread? _________________ Regards,
Al Savage
----------------
R7800 x2
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Fri Nov 04, 2022 9:25 Post subject:
Don't use save button on DDNS page unless you intend to click apply elsewhere or later in some other page (e.g. if youre doing multiple config change), after configuration, generally speaking any bugs not withstanding, inadyn needs to start/restart and that what the apply button does here.
Sadly there is no other way but to test all providers or follow bug reports to fix issues, but rest assured DDNS is a priority to get fixed.
I recommend you tail -f /var/log/messages in one terminal and then use another terminal to update the config file manually via CLI or FTP/SFTP/SSH/Telnet, until a new build is out that fixes the issue. then click apply (on web interface) for inadyn to use new config.
Not sure what is causing the issue but my R9000 has IPv6 enabled even shows an IPv6 address. But all my lan & wifi connections only show IPv4.
Do you have IPv6 enabled on your clients?
What about the IPv6 tab in DD-WRT? I am using this for my Xfinity connection and CloudFlare for my DNS. Also, is your cable/DSL/etc. connection set to Bridge Mode? You'll need that for IPv6 addresses. _________________ Netgear R9000
DD-WRT v3.0-r55819 std (04/17/24)
Linux 4.9.337 #722 SMP Wed Apr 17 04:16:49 +07 2024 armv7l
Gateway, AP, DNSMasq, Clock 2000MHz
VAP on wlan1 for internet devices
IPv4 & IPv6 (Prefix Delegation)
Static Leases & DHCP
CloudFlare, no SFE, SmartDNS, no QoS
2.4GHz: Vanilla, Airtime Fairness, NG-Mixed, ACK Timing 3150, WPA2 w/AES & WPA3
5GHz: Vanilla, Airtime Fairness, AC/N Mixed, ACK Timing 3150, WPA2 w/AES & WPA3
2 Netgear AX1800 WiFi Mesh Extenders
Xfinity 1.2Gbps/35Mbps
