Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

"bad IP received" with Speedport Smart 4 #501

Open
vinjana opened this issue Nov 3, 2022 · 3 comments
Open

"bad IP received" with Speedport Smart 4 #501

vinjana opened this issue Nov 3, 2022 · 3 comments

Comments

@vinjana
Copy link

vinjana commented Nov 3, 2022

My router is configured as follows:

Provider: other
Host name: myHostName.nsupdate.info
User name: myHostName.nsupdate.info
Password: bliblablub
Updateserver address: ipv4.nsupdate.info
Protocol: https
Port: 443

I used the configuration of the "Speedport Hybrid" router from your website as template, but entered the value from "Domain name" there in "Host name" here.

API Authentication Result Message: 2022-11-03 12:58:30 api authentication success. [hostname: myHostName.nsupdate.info (given in basic auth)]
Client Result Message: 2022-11-03 12:58:30 myHostName.nsupdate.info - received bad ip address: '2003:e7:7ff:1b82:ca99:b2ff:fe09:860d,80.132.212.228'
Server Result Message: // = empty

So, it seems the authentication worked, but then the IP address information was not provided by the router in the format expected by nsupdate.info.

The router logs report

<Domain existiert nicht (notfqdn)>

i.e. the "domain does not exist". But if I enter something else (e.g. just "myHostName") in the "Host name" field, already after saving the configuration the router reports an authentication failure. So I think that using "myHostName.nsupdate.info" as "Host name" value is correct.

I do not know whether the format of the IPs ($ipv6Address,$ipv4Address) provided by the router is the problem (so the router firmware has a bug), or whether the expectation of nsupdate.info server is incorrect (so the server has a bug). If it is the router, please just indicate. I will then try to file a bug report with the router producer.

Note that the Speedport Smart 4 is one of the two systems that work with hybrid LTE for the German Telekom (T-Com), and the device maybe (?) also used in othere countries. My guess is that others have the same problem and that this is rather an important router model.

@ThomasWaldmann
Copy link
Member

I do not know whether the format of the IPs ($ipv6Address,$ipv4Address) provided by the router
is the problem (so the router firmware has a bug)...

Well, that would be my first guess. The original dyndns standard only addressed giving a single IPv4 address.

The nsupdate.info service extends that to giving a single IPv6 address in the same way.

But I did not yet hear about a "standard" giving a comma separated list of ipv4,ipv6, so maybe ask them by which formal or real-world standard they expect that to be working.

@vinjana
Copy link
Author

vinjana commented Nov 3, 2022

O.k. Thanks for the info. I'm going to address this with the router producer (if I can somehow reach them).

@strarsis
Copy link

strarsis commented Oct 17, 2023

+1, when the Speedport Smart 4 has an IPv6 and IPv4 address, it will use them both comma-separated as value in myip.
Most dynamic DNS services do not support this format – or ignore the IPv6 part.
It would be great if nsupdate.info also supported this format!

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants