Has anyone noticed this message before in TailMon
# Health check:
# - Linux DNS config not ideal. /etc/resolv.conf overwritten. See https://tailscale.com/s/dns-fight
Literally only noticed it this morning and never seen previously.
I looked at the said /etc/resolv.conf and it contains my...
Just added something to my message above your last one @jksmurf
I didn't try running tailscale up in the command line itself, that worked regardless of the operating mode and tailmon reports it connected
Very odd, as previously the only difference between yours and mine is the Operating Mode, I had mine in Userspace
As a test, I just reverted my Custom additional command line, to remove --stateful-filtering and just advertise the route.
Saved, and as expected the connection failed to go up and...
Has anyone updated to the latest 1.66.4 version?
Not sure if this is normal, due to the new version but had the following symptoms:
- Update worked fine
- Service was showing as started
- Connection was showing as disconnected
Every time I tried to manually UP the connection, I only get a...
Good find indeed. Must admit have only configured I. userspace mode and my ask is similar to your own, and therefore I didn't recognise this failure
Good job on finding a solution
Hi @phneeley
Sounds like you had and now you have a similar setup to mine. I guess a couple of questions:
A) Did you approve the subnet routes within the tailscale console web page?
B) How are you trying to access your devices, via IP or hostnames or FQDN?
When I transferred from RPI only to...
Before this tailscale chat had started, I was actually already running tailscale on 1 of my 2 raspberry pi's.
Both pi's run my DHCP and run Pi-hole, and each of my internal devices have primary/secondary DNS pointing to the pi (along with the 86U DNS directory, ensuring all DNS goes via those...
This is a great idea for a project, but will you be collating and sharing a full step-by-step instruction set, by updating Post #1 (or automate it via a script and add to AMTM)?
Looks like last check was March 1st
Fri Mar 1 08:24:58 GMT 2024 Probing 'ext4' on device /dev/sda1
Running disk check with command 'e2fsck -p' on /dev/sda1
RagePro-USB: recovering journal
RagePro-USB: clean, 2482/15269888 files, 1797725/61049000 blocks
Fri Mar 1 08:24:58 GMT 2024 Disk...
Thanks @Viktor Jaep
I can SSH still
Plugging in the old USB and running Disk Check gives me a Remove or Add an exclusion, but it's not fundamentally detecting any device (old or new) but will try with a reboot again.
New device is SSD based with enclosure as you have mentioned.
Will try after...