Recent submissions

Comment · 1 month ago
Or just wait until wireguard updates the default. That's the whole theory behind wireguard since it's release. That's my plan.
Comment · 2 months ago
sounds neat, would love to try it but I don't make accounts for websites anymore.
Comment · 3 months ago
Comment · 3 months ago
I like the idea. I would love to try it out but the documentation is not the easiest to follow. A simple step by step linux to linux tunnel would be appreciated using docker. There is no complete example anywhere that I could find so far. I am basing a compose file on the vyos documentation mostly. Maybe I'll write one if I have time to figure it out.
Comment · 6 months ago
I just love love love how easy the wireguard update process is on windows! So well executed from the start.
Comment · 7 months ago
I like firewall rules. That's always a good start. Could you add a few screenshots?
Comment · 8 months ago
ok, I compiled it but it doesn't do anything. It just repeats itself. The agent piece is not working at all for me. Not sure what the trick is.
Comment · 10 months ago
I'm gonna need an app for that . No, I just tried it. Works as advertised. Thank you for the dockerfile. Using putty, the formatting is messed up.on the banner/help. Must be some dynamic end of line thing. Still works so.
Comment · 11 months ago
If I were to run an yggmail server and configure delta-chat to talk to it, would I get a similar result?
Comment · 1 year ago
I believe WireGuard employs a strategy where it announces 0.0.0.0/1 and 128.0.0.0/1 instead of using a complete quad-zero. This allows your local default route to maintain a lower administrative distance. Interestingly, they implement it this way on Android, and it appears to work effectively for daily use.

I was just curious. It doesn't necessarily mean it has to be a supported use case.

Comment · 1 year ago
That sounds intriguing! I'm looking forward to giving it a try. I've checked out the example configurations, and while there’s definitely a learning curve, it seems manageable. I use Babel over WireGuard myself and appreciate the ability to redistribute interfaces through inclusion and exclusion.

I’m curious if Nylon offers similar functionality. Can it redistribute a dummy /32 or a local /24 into the network? Also, how does it handle default route advertising? Would there be a risk of looping, similar to what happens with IPsec tunnels?

I also think this could really benefit from a Docker image to streamline setup.

Comment · 1 year ago
Hi there. I think the container image is private at the moment. Trying to pull ghcr.io/g1ibby/auto-vpn is failing. Render.com says: No public image found. It looks like you may be using a private image. Thx!
Comment · 2 years ago
Very interesting. Now to find a problem to solve
Comment · 2 years ago
You are correct. Your traffic is routed peer to peer (There are relay nodes available in case your devices fail to find each other. You can disable these in the config if you wish to do so.). All tailscale provides is an api to let your nodes find each other. However, the concern of the community is that tailscale generates an knows all your wg keys. In theory they could look at your traffic. Personally, I use tailscale happily.
Comment · 3 years ago
I wish in the future pricing section they would be referencing a possible free tier.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton