teleclimber, 27 days ago to Discord

I want to ask a question to the #Headscale community which is on #Discord, and it's asking me to "verify my identity via my phone" before I can even post once? What the heck is this? I've used Discord before and have never been asked this. Is this a "server" setting or a new Discord thing?

In any case it makes really not want to participate there. Please #FOSS people, what the heck, why this love of Discord?

Ironically I got less pushback signing up for a functional @tailscale account 🤦‍♂️

galileo, 1 month ago to random German

Nutzt hier jemand #headscale anstatt #tailscale VPN?
Oder gibt es eine andere freie Alternative?
Headscale scheint leider so ein bisschen "tot" zu sein..?

mark22k, 5 months ago to random German

I have compared several self-meshing VPN solutions - especially in the context of a VIXP in dn42.

https://mk16.de/blog/comparison-of-self-meshing-vpns/

TLDR: The one VPN solution that meets all my criteria is the pre-release version of Tinc.

#VPN #Networking #dn42 #Tinc #n2n #Tailscale #Headscale #Zerotier #Nebula

ljrk, 9 months ago to random

Thinking about my (still WIP) #PiHole setup. AFAICT, the guide for #DoH with #cloudflared at https://docs.pi-hole.net/guides/dns/cloudflared/ only coveres using DoH between the PiHole and the upstream DNS provider (e.g., Cloudflare, Google, etc.). But if I want to use DoH between my browser and my PiHole, I seem to need another DoH Proxy, which makes request flow like this:

1. incoming on dns.ljrk.org:443 (traefik reverse proxy)
2. forwarded to 127.0.0.1:80 (DoH Proxy #1)
3. upstream classic DNS resolver on 127.0.0.1:53 (PiHole)
4. forwards any non-blocked requests to 127.0.0.1:5053 (DoH Proxy #2)
5. upstream DoH DNS resolver such as 1.1.1.1:443/dns-request

Of course, most PiHole setups are local and I'll probably end up opening dns.ljrk.org only through a #TailScale/#HeadScale #VPN, but my browser may still prefer to speak DoH instead of RFC1035. I'm also not sure how #DNSSEC plays into this...

sophie, 10 months ago to random

For some reason, #zerotier has stopped working for me entirely a few days ago. No hosts in my zerotier network could reach each other anymore. They all display as online and the controller sees them but no actual traffic is being sent or received.

Well, yesterday I decided to finally switch to #tailscale using #headscale as control server. Took about half an hour to set up and works like a charm!

gbraad, 10 months ago to random

Also made a basic #Headscale application for #Cockpit. Headscale is a #Tailscale compatible coordination server. At the moment, it just shows a basic nodes list with online state and the first IP address.

https://github.com/spotsnel/cockpit-headscale

This is in a very pre-alpha state.

gbraad, 10 months ago (edited 10 months ago) to random

Set up a test #Headscale server so I can start working on the Cockpit application for it.

This is using two containers on my laptop and a server in the US which hosts the coordination server.

I know it is not recommended, but running it from a container: https://github.com/spotsnel/headscale-systemd which also hosts a tailscale process to my current networks.

https://github.com/spotsnel/headscale-systemd
https://github.com/spotsnel/cockpit-headscale

#tailscale