Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

DietPi-DDNS | Allow to update IPv4 as well as IPv6 #7309

Merged
merged 3 commits into from
Dec 15, 2024
Merged

DietPi-DDNS | Allow to update IPv4 as well as IPv6 #7309

merged 3 commits into from
Dec 15, 2024

Conversation

MichaIng
Copy link
Owner

No description provided.

@MichaIng MichaIng added this to the v9.9 milestone Dec 15, 2024
@MichaIng MichaIng linked an issue Dec 15, 2024 that may be closed by this pull request
- DietPi-DDNS | The "IPv6or4" option to update IPv6 only, if supported by server, network and provider, has been replaced with "IPv4and6". A server being reachable via IPv6 only is rarely wanted, as many networks do not support it. Instead, usually one will want to have it reachable via both, IPv4 as well as IPv6, which is now possible when using DietPi-DDNS, and the new default. When selected, the IPv4 update needs to succeed to proceed and install the cron job, while the IPv6 update is allowed to fail. In the logs, it will however produce a warning, so admins can check back and in case select IPv4 only, if IPv6 is not supported by server, network or provider. If, e.g. for security reason, IPv6 only is wanted, this option of course remains available, like before. Many thanks to @LOGIN-TB for doing this suggestion: #7278
- DietPi-DDNS | Lower severity of journal logs to "warning". In many cases, a server response is not an error, but a success confirmation. Also do not reverse the logs order in main menu, as we show 4 lines of logs now, to cover additional IPv6 requests as well.
@MichaIng MichaIng linked an issue Dec 15, 2024 that may be closed by this pull request
@MichaIng MichaIng force-pushed the ddns branch 2 times, most recently from 9c59a78 to 3bdf596 Compare December 15, 2024 15:53
- DietPi-DDNS | Do not overwrite CLI address family input with existing cron job. Fix cron job logs in main menu.
- DietPi-DDNS | The cron job does now log server response messages and connection errors separately with respective severities. Some DDNS providers do not return an HTTP error code, but an error text embadded into a regular HTTP 200 response. This, as well as success responses can now be seen via "journalctl -t dietpi-ddns".
@MichaIng MichaIng merged commit 370a261 into dev Dec 15, 2024
2 checks passed
@MichaIng MichaIng deleted the ddns branch December 15, 2024 16:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ddns with IPv4 and IPv6 dietpi-ddns/update.sh does not log message
1 participant