2/3 Topics #EU_OS needs help with:

1) What is the best way to backup user data for Linux EU OS users? https://gitlab.com/eu-os/eu-os.gitlab.io/-/issues/46 #borgbackup #btrfsbk #btrfs#nextcloud

2) How can unattended deployment with #foreman look like during pilot stage (thus without reconfiguring the network/DHCP yet)? https://gitlab.com/eu-os/eu-os.gitlab.io/-/issues/39 #foreman

3) How can a modern VPN provide extra security for people in home offices or on business trips? https://gitlab.com/eu-os/eu-os.gitlab.io/-/issues/47 #tailscale #headscale #rosenpass #wireguard #openvpn

Blog post: Progress report for #Dropserver for June and July.

I talk about how UI improvements came about for the #Tailscale node connection interface, and where things might go next now that Tailscale integration is done (or done enough for now at least).

https://olivierforget.net/blog/2025/dropserver-progress-june-july-2025.md/

#opensource #selfhosting

Blog post: Progress report for #Dropserver for June and July.

I talk about how UI improvements came about for the #Tailscale node connection interface, and where things might go next now that Tailscale integration is done (or done enough for now at least).

https://olivierforget.net/blog/2025/dropserver-progress-june-july-2025.md/

#opensource #selfhosting

I have a very weird issue with my #tailscale + #mumble server setup:

I have a murmur (mumble) server that binds to the tailscale interface on my server.

I have shared that endpoint with a friend and we're both connecting via tailscale to that mumble server to talk.

Every few minutes (3, 5, something like that), one of us gets reconnected. Mumble (client) says "Server failed to respond to TCP ping". On the server it says (murmur log): "Connection closed: The remote host closed the connection".

The tailscale log on the server says something like "adding connection to derp-* for ..." at that very moment of reconnecting.

How to debug this issue? I don't even know where to start. It looks like (to me, as a networking noob) that tailscale reconfigures connections and breaks the mumble connection.

#followerpower #linuxadmin #NetworkEngineering #networking #sysadmin

CC @tailscale

Please boost

I have a very weird issue with my #tailscale + #mumble server setup:

I have a murmur (mumble) server that binds to the tailscale interface on my server.

I have shared that endpoint with a friend and we're both connecting via tailscale to that mumble server to talk.

Every few minutes (3, 5, something like that), one of us gets reconnected. Mumble (client) says "Server failed to respond to TCP ping". On the server it says (murmur log): "Connection closed: The remote host closed the connection".

The tailscale log on the server says something like "adding connection to derp-* for ..." at that very moment of reconnecting.

How to debug this issue? I don't even know where to start. It looks like (to me, as a networking noob) that tailscale reconfigures connections and breaks the mumble connection.

#followerpower #linuxadmin #NetworkEngineering #networking #sysadmin

CC @tailscale

Please boost

New #blog post: Configuring #pihole to do split horizon #dns for my #tailscale clients

I've been running a tailnet for quite some time but hadn't got around to setting split DNS up properly. This post corrects that

https://www.bentasker.co.uk/posts/blog/general/configuring-pihole-to-serve-different-records-to-different-clients.html

New #blog post: Configuring #pihole to do split horizon #dns for my #tailscale clients

I've been running a tailnet for quite some time but hadn't got around to setting split DNS up properly. This post corrects that

https://www.bentasker.co.uk/posts/blog/general/configuring-pihole-to-serve-different-records-to-different-clients.html