Tailscale UI config Overwrites CLI config on Reboot
-
I did some further tests, and I suspect there’s a conflict between the configuration in the web UI and CLI. Here were my observations:
Advertise a route in the web UI.
Advertise an additional route in the CLI.
tailscale debug prefs displays both routes.
Reboot the machine.
tailscale debug prefs only displays the route configured in the web UI.
Basically, whatever configuration the web UI has, overwrites the CLI configuration on boot. -
You've discovered what pfSense is all about : a GUI driven system.
The GUI prepares config files, used by process to do tasks. The settings change (in the GUI) ? Then it recreates the config files, and if needed restarts the process.
Core OS things like 'routes' : it's the GUI that adds removes or changes them for you. Behind the curtains it will execute the same system (CLI ?) commands.
The GUI is not going to presume that item 1,2,3,4,8 and 9 are present and 7 has to be added.
It removes them all (clean known state) and then add 1,2,3,4,7, 8 and 9.
You've added 6 using the CLI ? It will be gone, as the GUI wasn't aware if it existence.Full control is possible. Install this and you are the CLI chef. No more GUI doing things behind your back.
-
Thanks for the reply! Thats what I was afraid of. We have 100s of pfsense/tailscale nodes that we don't have UI access to. We use Ansible to automatically configure them in a remote fashion, everything was fine until this routes issue. But I will check out the link.
Thanks again!