[GH-ISSUE #286] add speedport hybrid example configuration? #231

Closed
opened 2026-02-26 09:36:45 +03:00 by kerem · 19 comments
Owner

Originally created by @ThomasWaldmann on GitHub (Nov 21, 2016).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/286

Originally assigned to: @ThomasWaldmann on GitHub.

From my inbox:

Add under "Show Configuration" this example:

Speedport Hybrid configuration:
(Firmware 050124.03.00.012)
 
Domänenname: fkjdbnsfjsd.nerdpol.ovh
 
Benutzername: fkjdbnsfjsd.nerdpol.ovh
 
Kennwort: here you must enter the "Secret" you get under "Show Configuration"
 
Updateserver-Adresse: https://ipv4.nsupdate.info
Protokoll HTTPS
Port 443
Originally created by @ThomasWaldmann on GitHub (Nov 21, 2016). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/286 Originally assigned to: @ThomasWaldmann on GitHub. From my inbox: Add under "Show Configuration" this example: ``` Speedport Hybrid configuration: (Firmware 050124.03.00.012) Domänenname: fkjdbnsfjsd.nerdpol.ovh Benutzername: fkjdbnsfjsd.nerdpol.ovh Kennwort: here you must enter the "Secret" you get under "Show Configuration" Updateserver-Adresse: https://ipv4.nsupdate.info Protokoll HTTPS Port 443 ```
kerem closed this issue 2026-02-26 09:36:45 +03:00
Author
Owner

@ThomasWaldmann commented on GitHub (Nov 21, 2016):

Not sure how popular this kind of router is, can anybody comment?

<!-- gh-comment-id:261999638 --> @ThomasWaldmann commented on GitHub (Nov 21, 2016): Not sure how popular this kind of router is, can anybody comment?
Author
Owner

@elnappo commented on GitHub (Dec 27, 2016):

Would be interesting to know if this interface is the same on all speedport routers. These routers are mainly used by Deutsche Telekom (German Telecom).

<!-- gh-comment-id:269398173 --> @elnappo commented on GitHub (Dec 27, 2016): Would be interesting to know if this interface is the same on all speedport routers. These routers are mainly used by Deutsche Telekom (German Telecom).
Author
Owner

@maboxx commented on GitHub (Jan 16, 2018):

I recently use this router and will now test it as described above. If I have any problems with that, I will report here. What I notice in the first moment. I have entered and saved the data but in my nsupdate.info account there is currently no refresh of the IP4v address. I'm will watch if it work on the next ip switch.

<!-- gh-comment-id:358093742 --> @maboxx commented on GitHub (Jan 16, 2018): I recently use this router and will now test it as described above. If I have any problems with that, I will report here. What I notice in the first moment. I have entered and saved the data but in my nsupdate.info account there is currently no refresh of the IP4v address. I'm will watch if it work on the next ip switch.
Author
Owner

@maboxx commented on GitHub (Jan 23, 2018):

OK, the router IP address has change but but the nsupdate.info account do not received an update.

Domänenname = name.nsupdate.info
Benutzername = name.nsupdate.info
Kennwort = xxxxxxxx
Updateserver-Adresse = https://ipv4.nsupdate.info/nic/update
Protokoll = https
Port = 44

<!-- gh-comment-id:359831119 --> @maboxx commented on GitHub (Jan 23, 2018): OK, the router IP address has change but but the nsupdate.info account do not received an update. Domänenname = name.nsupdate.info Benutzername = name.nsupdate.info Kennwort = xxxxxxxx Updateserver-Adresse = https://ipv4.nsupdate.info/nic/update Protokoll = https Port = 44
Author
Owner

@ThomasWaldmann commented on GitHub (Jan 25, 2018):

There seems some duplication...

Port 443

If they ask for the protocol separately, it might be the case that they only want ipv4.nsupdate.info/nic/update (not https:// here) for the update server address.

<!-- gh-comment-id:360337485 --> @ThomasWaldmann commented on GitHub (Jan 25, 2018): There seems some duplication... Port 443 If they ask for the protocol separately, it might be the case that they only want ipv4.nsupdate.info/nic/update (not https:// here) for the update server address.
Author
Owner

@maboxx commented on GitHub (Jan 29, 2018):

OK I test it again and it didn't work, even without "https" it doesn't work (just with ipv4.nsupdate.info/nic/update)

<!-- gh-comment-id:361330286 --> @maboxx commented on GitHub (Jan 29, 2018): OK I test it again and it didn't work, even without "https" it doesn't work (just with ipv4.nsupdate.info/nic/update)
Author
Owner

@maboxx commented on GitHub (Feb 6, 2018):

In the event log of the speeport hyprid I can see the following entry:

(D001) Aktualisierung für Dynamic DNS war nicht erfolgreich. Der Update Server konnte nicht erreicht werden.

When I type the URL https://ipv4.nsupdate.info/nic/update into the browser and login I receive the following:

notfqdn

<!-- gh-comment-id:363513859 --> @maboxx commented on GitHub (Feb 6, 2018): In the event log of the speeport hyprid I can see the following entry: > (D001) Aktualisierung für Dynamic DNS war nicht erfolgreich. Der Update Server konnte nicht erreicht werden. When I type the URL https://ipv4.nsupdate.info/nic/update into the browser and login I receive the following: > notfqdn
Author
Owner

@ThomasWaldmann commented on GitHub (Feb 8, 2018):

notfqdn means that the hostname you gave is not a fully qualified domain name.

e.g. foo instead of foo.nsupdate.info

<!-- gh-comment-id:364254584 --> @ThomasWaldmann commented on GitHub (Feb 8, 2018): notfqdn means that the hostname you gave is not a fully qualified domain name. e.g. foo instead of foo.nsupdate.info
Author
Owner

@maboxx commented on GitHub (Feb 26, 2018):

Ok I give up.
It doesn`t work with a Hyprid Speedport. As you can see above my configuration:

Domänenname = name.nsupdate.info
Benutzername = name.nsupdate.info
Kennwort = xxxxxxxx
Updateserver-Adresse = https://ipv4.nsupdate.info/nic/update
Protokoll = https
Port = 443

I always receive the message:
(D001) Aktualisierung für Dynamic DNS war nicht erfolgreich. Der Update Server konnte nicht erreicht werden.
Even if I remove https at the server address.

<!-- gh-comment-id:368449538 --> @maboxx commented on GitHub (Feb 26, 2018): Ok I give up. It doesn`t work with a Hyprid Speedport. As you can see above my configuration: Domänenname = name.nsupdate.info Benutzername = name.nsupdate.info Kennwort = xxxxxxxx Updateserver-Adresse = https://ipv4.nsupdate.info/nic/update Protokoll = https Port = 443 I always receive the message: `(D001) Aktualisierung für Dynamic DNS war nicht erfolgreich. Der Update Server konnte nicht erreicht werden.` Even if I remove https at the server address.
Author
Owner

@ThomasWaldmann commented on GitHub (Feb 26, 2018):

Maybe they have bugs in processing these values (see my comment about duplication).

Ehrm, I just noticed there is no "path" in the URL in the top post. Can you try that?:

Updateserver-Adresse: https://ipv4.nsupdate.info

<!-- gh-comment-id:368465645 --> @ThomasWaldmann commented on GitHub (Feb 26, 2018): Maybe they have bugs in processing these values (see my comment about duplication). Ehrm, I just noticed there is no "path" in the URL in the top post. Can you try that?: Updateserver-Adresse: https://ipv4.nsupdate.info
Author
Owner

@maboxx commented on GitHub (Apr 6, 2018):

Hi Thomas,
I have now tested again. I am not longer recieving this "D001" error, see above in my post.
But I have new errors now, see below:

With this configuration:

  • Domänenname = name.nsupdate.info
  • Benutzername = name.nsupdate.info
  • Kennwort = xxxxxxxx
  • Updateserver-Adresse = https://ipv4.nsupdate.info
  • Protokoll = https
  • Port = 443

I recieve the following error:
(D002-1) Aktualisierung für Dynamic DNS war nicht erfolgreich. Der Dynamic DNS Anbieter meldet <Fehler bei der Authentifizierung (badauth)>

When I change the configuration in this:

  • Domänenname = name.nsupdate.info
  • Benutzername = name
  • Kennwort = xxxxxxxx
  • Updateserver-Adresse = https://ipv4.nsupdate.info
  • Protokoll = https
  • Port = 443

I recieve the following error:
(D002-3) Aktualisierung für Dynamic DNS war nicht erfolgreich. Der Dynamic DNS Anbieter meldet <Domain existiert nicht (notfqdn)>

Any idea what the problem could be?

<!-- gh-comment-id:379352109 --> @maboxx commented on GitHub (Apr 6, 2018): Hi Thomas, I have now tested again. I am not longer recieving this "D001" error, see above in my post. But I have new errors now, see below: With this configuration: - Domänenname = name.nsupdate.info - Benutzername = name.nsupdate.info - Kennwort = xxxxxxxx - Updateserver-Adresse = https://ipv4.nsupdate.info - Protokoll = https - Port = 443 I recieve the following error: `(D002-1) Aktualisierung für Dynamic DNS war nicht erfolgreich. Der Dynamic DNS Anbieter meldet <Fehler bei der Authentifizierung (badauth)>` When I change the configuration in this: - Domänenname = name.nsupdate.info - Benutzername = name - Kennwort = xxxxxxxx - Updateserver-Adresse = https://ipv4.nsupdate.info - Protokoll = https - Port = 443 I recieve the following error: `(D002-3) Aktualisierung für Dynamic DNS war nicht erfolgreich. Der Dynamic DNS Anbieter meldet <Domain existiert nicht (notfqdn)>` Any idea what the problem could be?
Author
Owner

@ThomasWaldmann commented on GitHub (Apr 6, 2018):

You used the secret for that host as "Kennwort"?

"Benutzername" must be the fqdn (name.nsupdate.info).

<!-- gh-comment-id:379383420 --> @ThomasWaldmann commented on GitHub (Apr 6, 2018): You used the secret for that host as "Kennwort"? "Benutzername" must be the fqdn (name.nsupdate.info).
Author
Owner

@maboxx commented on GitHub (Apr 7, 2018):

Great, it works like this:

  • Domänenname = name.nsupdate.info
  • Benutzername = name.nsupdate.info
  • Kennwort = secret for that host
  • Updateserver-Adresse = https://ipv4.nsupdate.info
  • Protokoll = https
  • Port = 443

The problem was the password. I used the password for the login on my account on nsupdate.info.
I probably should have read your first post better, sorry.

<!-- gh-comment-id:379435712 --> @maboxx commented on GitHub (Apr 7, 2018): Great, it works like this: - Domänenname = name.nsupdate.info - Benutzername = name.nsupdate.info - Kennwort = _secret for that host_ - Updateserver-Adresse = https://ipv4.nsupdate.info - Protokoll = https - Port = 443 The problem was the password. I used the password for the login on my account on nsupdate.info. I probably should have read your first post better, sorry.
Author
Owner

@ThomasWaldmann commented on GitHub (Apr 7, 2018):

@maboxx glad it worked now. Can you tell us the firmware version of your router?

<!-- gh-comment-id:379504905 --> @ThomasWaldmann commented on GitHub (Apr 7, 2018): @maboxx glad it worked now. Can you tell us the firmware version of your router?
Author
Owner

@maboxx commented on GitHub (Apr 8, 2018):

Router: Speedport Hybrid
Firmware version: 050124.03.07.001

Thank you so much for your great service on nusupdate.info

<!-- gh-comment-id:379521665 --> @maboxx commented on GitHub (Apr 8, 2018): Router: **Speedport Hybrid** Firmware version: **050124.03.07.001** Thank you so much for your great service on nusupdate.info
Author
Owner

@ThomasWaldmann commented on GitHub (Sep 30, 2018):

@maboxx Can you switch the Speedport UI to English and update your previous post so we can have the text for the new help entry in English (like everything else)?

<!-- gh-comment-id:425753376 --> @ThomasWaldmann commented on GitHub (Sep 30, 2018): @maboxx Can you switch the Speedport UI to English and update your previous post so we can have the text for the new help entry in English (like everything else)?
Author
Owner

@maboxx commented on GitHub (Oct 2, 2018):

Ok I switch the GUI to english, here is the post with text in english:
......
Great, it works like this:

Provider = other Provider
Domain name = name.nsupdate.info
User name = name.nsupdate.info
Password = secret for that host
Updateserver-Adresse = https://ipv4.nsupdate.info
Protokoll = https
Port = 443

The problem was the password. I used the password for the login on my account on nsupdate.info.
I probably should have read your first post better, sorry.

<!-- gh-comment-id:426250624 --> @maboxx commented on GitHub (Oct 2, 2018): Ok I switch the GUI to english, here is the post with text in english: ...... Great, it works like this: Provider = other Provider Domain name = name.nsupdate.info User name = name.nsupdate.info Password = secret for that host Updateserver-Adresse = https://ipv4.nsupdate.info Protokoll = https Port = 443 The problem was the password. I used the password for the login on my account on nsupdate.info. I probably should have read your first post better, sorry.
Author
Owner

@marcusgrtz commented on GitHub (Apr 4, 2022):

Does anyone know what the settings are for a Speedport Smart 4 router?

<!-- gh-comment-id:1087924412 --> @marcusgrtz commented on GitHub (Apr 4, 2022): Does anyone know what the settings are for a Speedport Smart 4 router?
Author
Owner

@strarsis commented on GitHub (Mar 29, 2024):

@marcusgrtz: When the Speedport Smart 4 router has an internet connection with an IPv6- and IPv4-address, it will send both IP addresses comma-separated for a single parameter. This is incompatible with most custom/free DynDNS-providers, except for IPv64.net.

You can use a HTTP request catcher as the updater URL (e.g. https://webhook.site/) to see what the Speedport actually sends (including HTTP auth and IP value).

<!-- gh-comment-id:2027609251 --> @strarsis commented on GitHub (Mar 29, 2024): @marcusgrtz: When the Speedport Smart 4 router has an internet connection with an IPv6- and IPv4-address, it will send both IP addresses comma-separated for a single parameter. This is incompatible with most custom/free DynDNS-providers, except for IPv64.net. You can use a HTTP request catcher as the updater URL (e.g. https://webhook.site/) to see what the Speedport actually sends (including HTTP auth and IP value).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nsupdate.info-nsupdate-info#231
No description provided.