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/
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/
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
⁂ Article
A Self-hosted, BSD-native Gemini Protocol Server Stack
For those who are adventurous enough to explore the non-http corners of the Internet, the Gemini protocol is a delightful experience to use. It has been around a number of years, making the biggest bang around the time when discontent with the web’s general demise started to reach current heights (so maybe around 2022).
My “capsule”, Vigilia, is self-hosted, and has been since its inception. It used to run on a disused Macbook Pro running Fedora Server, under our TV at home, but since […]
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
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
A space for Bonfire maintainers and contributors to communicate
