Bug #13632
closed
tailscale does not survive reboot on pfsense with ram disk in use
Added by Bill Flood over 2 years ago.
Updated about 2 years ago.
Affected Architecture:
All
Description
pfSense-pkg-Tailscale 0.1.0_1pfSense package Tailscale 1.26.2
pfsense 2.6.0-RELEASE (amd64)
With a properly configured and connected Tailscale configuration setup the authentication with Tailscale fails after reboot when using a Ram disk on pfsense. Keys are set to not expire. When the Ram disk is disabled (assuming a new key is used after a failure) the connection succeeds after every reboot. Expectation is that a configuration can survive a reboot/crash as configuration and keys should be stored in non-volatile locations like any other service.
The status log on failure shows:
Error executing command (/usr/local/bin/tailscale status)
- Health check:
- - not logged in, last login error=invalid key: API key [key id shown here] not valid
Logged out.
Files
The ram disk is configured in pfsense->System->Advanced->Miscellaneous and backup parameters are populated.
- Status changed from New to In Progress
Looking at this.
First I need to expose the --statedir tailscaled option to the rc script (and upstream it). I'm testing a build now with this patch. Second, modify the PHP to set this new RC option to a non-volatile path.
This should be fixed soon.
- Status changed from In Progress to Feedback
v0.1.3 includes migration code that will move the state file from /var/db/tailscale/tailscale.state to a location that is guaranteed to be persistent /usr/local/pkg/tailscale/state. This is also configurable via the Settings page.
- Due date set to 04/18/2023
- Start date set to 04/18/2023
- % Done changed from 0 to 100
- Estimated time set to 3.00 h
- Affected Version deleted (
2.6.0)
The latest Tailscale version under available packages is 0.1.2.
v0.1.3 is not listed yet. Please check.
tailscale v0.1.3 on 23.05.a.20230421.0022 in the package's settings provides a configurable field for state directory which is pre-populated with a persistent directory with RAM disks previously enabled
Tested against:
23.05-BETA (amd64)
built on Wed May 03 06:05:00 UTC 2023
FreeBSD 14.0-CURRENT
Tailscale 0.1.3_1
It connected sucesefully after reboot with ram disk in use.
I am marking this ticket as resolved.
- Status changed from Feedback to Resolved
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by