Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Adramyttium

#1
I just did some checking and can confirm that my pre-authorized key used by opnsense was no longer found in tailscale. Recreating it solved the issue.

I think this has to do with the expiration of a node-key, which is different from the expiration of the pre-auth key used by Opnsense. Here is the tailscale documentation:

"If an auth key expires, any device authorized by it remains authorized until its node key expires. Each device generates a node key when you log in to Tailscale and uses it to identify itself to the tailnet. **By default, node keys automatically expire every 180 days.** You can change the default node key expiry from the Key Expiry section of the Device management page of the admin console."

[See: https://tailscale.com/kb/1085/auth-keys?q=auth]

From what I can tell, the node key expiry cannot be overridden. What may have happened is that those of us who started using the new tailscale plugin were using node keys that finally expired, which might explain why the reports in the forum are spread out over several days. It seems that reauthentication is necessary at some point, even if you have chosen "Expiry disabled" for the machine in question. I think.
#2
23.7 Legacy Series / Re: ddclient issues with noip
January 16, 2024, 03:30:28 PM
Quote from: banym on January 09, 2024, 06:19:39 PM
Hi from Bavaria, too  ;D

I can second this. After one of the last updates my ddns with no-ip stopped working, too.
After reconfiguration to custom mode it worked again with no-ip.

Reviewed the settings from the module but could not find the difference.

Here my custom settings that worked:

I had to set it back to "Custom" as well, but in my case it still doesn't update no-ip. I tested it by first logging into no-ip and changing the domain manually to 1.1.1.1. See the attached screenshot for a record of what happened when ddclient attempted the update.

It seems that all ddclient did was check the WAN interface IP, noted it was the same as it thought it was, and then fails to update no-ip. It's like ddclient never attempted to "see" the 1.1.1.1 address on file at no-ip.

no-ip has been a struggle ever sense dyndns was removed from the repository. Frustrating.
#3
General Discussion / Re: ddclient with no-ip.com
April 20, 2023, 09:02:05 PM
Quote from: tekkyguy on February 01, 2023, 03:22:06 AM
Yes, I am able to see it in the log file.... but why it is not displayed in the web console section Dynamic DNS =>  under "accounts" ??

The info is empty... "Current IP" and "Updated" are staying empty ???

You're not alone. Mine updated as well but doesn't show on the opnsense console.
#4
I'm having the same issue. Will try the server config changes here and will report back.