Joined: 21 Nov 2013 Posts: 65 Location: Cathedral City, CA, USA
Posted: Thu Oct 27, 2022 0:09 Post subject:
Router/Version: Netgear R7800
File/Kernel: DD-WRT v3.0-r50671 std (10/26/22) / Linux 4.9.330 #1313 SMP Wed Oct 26 05:13:03 +07 2022 armv7l
Previous/Reset: r50551 std (10/19/22) / No
Everything seems to be working as normal but got this message (in PNG image file attached) after the flash but before reboot.
------------------------------
EDIT: On the DDNS tab, I use no-IP as my provider, the service when it starts after system boots (system time has not yet contacted NTP servers so Jan 1, 00:00:45) the message in the DDNS service status says "connecting" bottom of DDNS page. After router boots it stays like that until I hit apply button and then the box will say Success with syslog messages stating Update forced for alias XXX.com, new IP# XX.XX.XX.XX - Not sure if its logging into no-IP on initial boot. _________________ Router/Version: Netgear R7800
File/Kernel: DD-WRT v3.0-r50671 std (10/26/22), Linux 4.9.330 #1313 SMP Wed Oct 26 05:13:03 +07 2022 armv7l
Router/Version: R7800
File/Kernel: DD-WRT v3.0-r50671 std (10/26/22)
Kernel Version: Linux 4.9.330 #1313 SMP Wed Oct 26 05:13:03 +07 2022 armv7l
Previous/Reset: r49626 - Good Run / No
Mode/Status: GW / Working Well
Issues/Errors: none / none
Services Used: DHCP WAN,IPv6-6to4,NTP,WG Client,VLANx,BRx,SSH,Syslog,Cron,USB Storage,Entware DNSCrypt v2.1.1
Services Disabled: WiFi,QoS,ttraff,SFE,Telnet,NAS,Samba,YAMon3.4.6
Home Main AP Router
Router/Version: R7800
File/Kernel: DD-WRT v3.0-r50671 std (10/26/22)
Kernel Version: Linux 4.9.330 #1313 SMP Wed Oct 26 05:13:03 +07 2022 armv7l
Previous/Reset: r49626 - Good Run / No
Mode/Status: GW(double-nat) & AP / Working Well
Issues/Errors: none / none
Services Used: Static WAN,IPv6-6to4,WiFi Vannilla,NTP,2xWG Clients,VAPx,VLANx,BRx,SSH,Syslog,Cron,USB Storage,Entware DNSCrypt v2.1.1
Services Disabled: SPI,QoS,ttraff,SFE,Telnet,NAS,Samba
All running for over 2 hours.
Thank-you BrianSlyer for your Great Work and everyone else who makes DD-WRT Great on the Forum! _________________ Home Network on Telus 1Gb PureFibre - 10GbE Copper Backbone
2x R7800 - Gateway & WiFi & 3xWireGuard - DDWRT r53562 Std k4.9
Off Site 1
R7000 - Gateway & WiFi & WireGuard - DDWRT r54517 Std
E3000 - Station Bridge - DDWRT r49626 Mega K4.4
Off Site 2
R7000 - Gateway & WiFi - DDWRT r54517 Std
E2000 - Wired ISP IPTV PVR Blocker - DDWRT r35531
just now installed on the daughter's EA8500
installed over r49866 ...yea yall know what that means
required a reset & reconfig. Fairly simple but 3 yrold grandson sure
didn't like his Disney+ interuppted
tis all back good again now
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Thu Oct 27, 2022 19:20 Post subject:
ho1Aetoo wrote:
ho1Aetoo wrote:
Router/Version: R7800
File/Kernel: Linux 4.9.330 #1313 SMP Wed Oct 26 05:13:03 +07 2022 armv7l
Previous/Reset: r50593 / no
Mode/Status: Gateway / working
Services Used: PPPoE,DHCP,DHCP-Reservation,Dnsmasq + PiHole,DDNS,SSH,WiFi 2,4Ghz + 5Ghz AP's + VAP's Vanilla,USB,Port forwarding,QoS
Issues/Errors:my ddns is broken
Code:
Oct 26 14:21:47 DD-WRT user.err inadyn[4125]: Parse error in /tmp/ddns/inadyn.conf
Oct 26 14:21:47 DD-WRT user.err inadyn[4125]: Error code 74: Missing .conf file
BS fixed it and and "custom" works again.
The problems should be fixed in the next public build.
However, the GUI and variables have changed, so DDNS must be reconfigured.
its very broken, as of r50710 it doesnt work at all just seg faults, regardless what i put in the fields.. duck dns or custom, both broken.. (what is "path".? now that its changed all guides for duck dns are useless)
Code:
Oct 27 14:00:22 Haswell logger : [ddns] : successfully started
Oct 27 14:00:22 Haswell inadyn In-a-dyn version 2.9.1 -- Dynamic DNS update client.
Oct 27 14:00:22 Haswell inadyn Update forced for alias ****.duckdns.org, new IP# 104.246.129.146
Oct 27 14:00:23 Haswell inadyn Fatal error in DDNS server response:
Oct 27 14:00:23 Haswell inadyn [200 OK] KO
Oct 27 14:00:23 Haswell inadyn Error response from DDNS server, exiting!
Oct 27 14:00:23 Haswell inadyn Error code 48: DDNS server response not OK
Oct 27 14:00:23 Haswell kernel [ 1903.019295] inadyn[6697]: segfault at 7ff1ec9f20cc ip 00007ff1eccf6c28 sp 00007fff705b24a0 error 4 in libc.so[7ff1eccbe000+48000]
its very broken, as of r50710 it doesnt work at all just seg faults, regardless what i put in the fields.. duck dns or custom, both broken.. (what is "path".? now that its changed all guides for duck dns are useless)
Code:
Oct 27 14:00:22 Haswell logger : [ddns] : successfully started
Oct 27 14:00:22 Haswell inadyn In-a-dyn version 2.9.1 -- Dynamic DNS update client.
Oct 27 14:00:22 Haswell inadyn Update forced for alias ****.duckdns.org, new IP# 104.246.129.146
Oct 27 14:00:23 Haswell inadyn Fatal error in DDNS server response:
Oct 27 14:00:23 Haswell inadyn [200 OK] KO
Oct 27 14:00:23 Haswell inadyn Error response from DDNS server, exiting!
Oct 27 14:00:23 Haswell inadyn Error code 48: DDNS server response not OK
Oct 27 14:00:23 Haswell kernel [ 1903.019295] inadyn[6697]: segfault at 7ff1ec9f20cc ip 00007ff1eccf6c28 sp 00007fff705b24a0 error 4 in libc.so[7ff1eccbe000+48000]
Since I don't use duckdns I don't know the settings.
But something like this
DYNDNS Server = duckdns.org
Path = /update?domains=etc...
enable SSL if it is supported or needed (https)
The new version also supports DuckDNS as provider selection.
May not work because maybe not tested.
The problems should be fixed in the next public build.
However, the GUI and variables have changed, so DDNS must be reconfigured.
Just saying, what's the meaning of "fixed" if the previous config is still not compatible and users still need to reconfigure from scratch? There are more unexplained fields for "Custom" so probably picking the exact provider in the drop-down list (if available) is better than "Custom".
pandemonium420 wrote:
EDIT: On the DDNS tab, I use no-IP as my provider, the service when it starts after system boots (system time has not yet contacted NTP servers so Jan 1, 00:00:45) the message in the DDNS service status says "connecting" bottom of DDNS page. After router boots it stays like that until I hit apply button and then the box will say Success with syslog messages stating Update forced for alias XXX.com, new IP# XX.XX.XX.XX - Not sure if its logging into no-IP on initial boot.
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Sun Oct 30, 2022 6:51 Post subject:
@IONK the build thread announces DDNS/other upgrades.
Our old DDNS solution was from 2005 plus it was no longer developed since 2007 in addition several services that it supported had been out of service for years.
The current is a fork of such and currently developed and maintained much was refactored so breakages/incompatibilities are to be expected as new code is debugged.
Router/Version: Netgear R7800
File/Kernel: DD-WRT v3.0-r50671 std (10/26/22)
Previous/Reset: No
Mode/Status: Ok
Issues/Errors: Problem with hidden WiFi: network not working.
There are dozens of changes for each new build, and laymen as me have no way to understand what's the implication when looking at the source code.
My point is that, if the change is drastic and known to be incompatible with existing config, is there any way to have an explicit warning so that the users do not have unpleasant surprise? (for example: "old config is incompatible, need to do nvram erase after upgrading to the new build")
I remember there were similar announcements for VAP startup scripts/VLAN/swconfig/etc.
There have been many dyndns changes since build 50671:
For example, the "custom config" changes were added after build 50671.
I've posted it here so you'll know when the next public build comes out.
I will also post it again in the next build thread - if blkt doesn't do it.
Anyway, DYNDNS can be safely considered broken in build 50671 and users with problems should put their focus on the next public build.
unfortunately, tatsuya has not contacted me again, so I assume that it works.
