Hello Community,
i bought 2x AVM 4040 and flashed OpenWRT. VERSION .02 on both devices.
I can login, change settings.. all things seem to work.
I connect via PC, receive an IP. All good.
ddnss.de is resolved to IP on both devices.
Ping on ddnss.de only works on one device.
Other device got a timeout.
Factory Reset did not help.
Reflashed via sysupgrade to .01 and .02
Still no ping possible on both Versions.
Any hint ?
Greetings Michael
EDIT: forget everything below... why? Because I just tested myself and I also don't get replies. This means that the ddnss.de domain does not reply to pings. Some sites/services are configured not to reply to pings. Ping other things and it should work normally (like google.com or 8.8.8.8)
Please copy the output of the following commands and post it here using the "Preformatted text </> " button:
Remember to redact passwords, MAC addresses and any public IP addresses you may have:
cat /etc/config/network
cat /etc/config/dhcp
cat /etc/config/firewall
Hello psherman,
i tried with different boxes:
AVM 7530 + 7590 (AVM FW 7.39 and 7.29) and 2x OpenWRT 4040 FW 22.03.2
result:
C:\>ping ddnss.de
Ping wird ausgeführt für ddnss.de [85.114.136.161] mit 32 Bytes Daten:
Antwort von 85.114.136.161: Bytes=32 Zeit=20ms TTL=53
Antwort von 85.114.136.161: Bytes=32 Zeit=20ms TTL=53
Antwort von 85.114.136.161: Bytes=32 Zeit=21ms TTL=53
Antwort von 85.114.136.161: Bytes=32 Zeit=19ms TTL=53
just one AVM 4040 FW 22.03.02 does not get any answer from ddnss.de
i switched to another AVM 4040 FW 22.03.02 and my S2S AVM7530 7.39 <-> AVM 4040 OpenWRT works now.
reflashed the first AVM 4040 again but still ping not working.
i bought all 4x 4040 used.
first (defect) with FW 7.29 installed.
second i dont remember FW but on OpenWRT ping works
2 boxes with 7.14 preinstalled, OpenWRT ping works.
Perhaps something went wrong with 7.29 box ? old owner perhaps used OpenWRT and recover did not delete all settings ? is there another way to delete all settings ? recover to avm-fw again ? and flash openwrt again ?
greetings michael
You can certainly reset the router to defaults if you believe that a setting may have caused a problem here. But I am pretty sure that this is related to the way that ddnss.de is configured, not something on your local setup.
Interestingly, I have just tried pinging it again and it is working. My main router is a Unifi Security Gateway, and nothing changed on my side between the earlier attempt and now. Both attempts resolved to the same IP address.
I highly doubt anything is wrong with your hardware (at least not based on these ping tests)... as long as you can reach the services you need and can ping other properties on the internet (that do reliably return ping requests), it would indicate that nothing you've done on your side of the network is likely to be at issue.
Is there a specific reason you need to ping that address? Or put another way, if you cannot ping that address, what problems does it cause you? Can you just use another address instead?
Hello psherman,
i tried to establish a Wireguard S2S using 2 ddnss.de address.
my dynamic dns never got updated.
now i changed my 4040 and finally last update and next update is filled.
i already performed a reset, flashed 0.2 and 0.1, reset again. nothing worked.
three other 4040 worked out of the box.
michael
A Wireguard S2S setup shouldn't have any dependencies regarding directly pinging ddnss.de.
This would be an issue with the configuration of your ddns scripts or your account.
In fact, if you are trying to ping your actual WG endpoints, you should have a domain or subdomain that is actually yours (so for example: mysubdomain.ddnss.de, assuming that you can setup a subdomain against ddnss.de -- different services offer different domains and configuration options). Pinging "ddnss.de" is pinging their actual servers. Whereas if you have subdomain, that will actually resolve to your endpoints.
I'm not sure what 0.2 and 0.1 are here... can you be more specific/complete (so 22.03.2, for example, not just 0.2), or whatever you're using.
define "nothing worked" here -- the ping test, or literally no network functionality? There are lots of variables that could cause the latter -- have you accounted for all of those things in trying to make sure that the configuration matches your working devices?
It is possible you have a unit that had faulty hardware. But the ping test to ddnss.de alone is not sufficient to determine that situation.
Hello psherman,
just tested all 4/4 AVM 4040.
They are all flashed to 22.03.2.
All boxed reset to factory, one box configured and SW + config copied to all other boxes.
3/4 boxes can successfull ping every ip-adress i have tested.
Ping wird ausgeführt für ddnss.de [85.114.136.161] mit 32 Bytes Daten:
Antwort von 85.114.136.161: Bytes=32 Zeit=21ms TTL=53
Antwort von 85.114.136.161: Bytes=32 Zeit=21ms TTL=53
Antwort von 85.114.136.161: Bytes=32 Zeit=28ms TTL=53
Antwort von 85.114.136.161: Bytes=32 Zeit=26ms TTL=53
Ping-Statistik für 85.114.136.161:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 21ms, Maximum = 28ms, Mittelwert = 24ms
C:\Users\Dance>ping www.google.de
Ping wird ausgeführt für www.google.de [172.217.19.67] mit 32 Bytes Daten:
Antwort von 172.217.19.67: Bytes=32 Zeit=10ms TTL=111
Antwort von 172.217.19.67: Bytes=32 Zeit=10ms TTL=111
Antwort von 172.217.19.67: Bytes=32 Zeit=10ms TTL=111
Antwort von 172.217.19.67: Bytes=32 Zeit=9ms TTL=111
Even Dynamic DNS shows: Last & Next Update 2022-10-22 and time
1/4 boxes:
C:\Users\Dance>ping ddnss.de
Ping wird ausgeführt für ddnss.de [85.114.136.161] mit 32 Bytes Daten:
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Ping-Statistik für 85.114.136.161:
Pakete: Gesendet = 4, Empfangen = 0, Verloren = 4
(100% Verlust),
C:\Users\Dance>ping www.google.de
Ping wird ausgeführt für www.google.de [172.217.19.67] mit 32 Bytes Daten:
Antwort von 172.217.19.67: Bytes=32 Zeit=8ms TTL=111
Antwort von 172.217.19.67: Bytes=32 Zeit=9ms TTL=111
Antwort von 172.217.19.67: Bytes=32 Zeit=9ms TTL=111
Antwort von 172.217.19.67: Bytes=32 Zeit=10ms TTL=111
Dynamic DNS show on Last and Next Update = never.
I did not find any other fault on the faulty box. routing, internetgaming, pings to other sites.
everything works.
I will just stop using the faulty one. 
greetings michael
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.