11–20 of 21 posts
An even simpler way of routing a certain container through wireguard, without needing to create a docker network and bind it to wg manually: https://github.com/pirate/wireguard-docs#example-client-cont...
I appreciate the write up, but you can't just put "simple" in a title to and expect it to be simple for everyone. It's simple for what audience? I know there are plenty of developers (especially Mac/Windows users) who would read this and be put off. Simple for me would be running one command like "docker-compose up" and be up and running.
Anyway, take a look at the "Instructions in Short" section (I just added a button at the article beginning to jump to that section). You only have to fill in a few blanks (probably just copying from a wg-quick file you already have), add a few lines to your docker-compose file and then run docker compose up.
I think that's somwhat simple enough for a non-trivial task. I might write a script to do that automatically in the future (somebody in the article's discussion asked for that, by the way).
> take a look at an OpenVPN config file and you will appreciate this shortness OpenVPN config files can be pretty small once you remove all the comments (my server is 22 lines) That being said, I like WireGuard. I've switched over a lot of stuff to it. It does have some issues though: * Road warrior configurations aren't easy. If you use a DNS name as an endpoint, and that DNS entry changes, you have to refresh it. T…
That particular jab was pretty strange.
The very first example in the OpenVPN documentation is of a server config:
dev tun
ifconfig 10.8.0.1 10.8.0.2
secret static.key
There are many applications with complex configuration formats, but OpenVPN is not it. It has both a simple format and good defaults. It should be an example to others!
> take a look at an OpenVPN config file and you will appreciate this shortness OpenVPN config files can be pretty small once you remove all the comments (my server is 22 lines) That being said, I like WireGuard. I've switched over a lot of stuff to it. It does have some issues though: * Road warrior configurations aren't easy. If you use a DNS name as an endpoint, and that DNS entry changes, you have to refresh it. T…
> If you use a DNS name as an endpoint, and that DNS entry changes, you have to refresh it. This is really frustrating for me. If you put a DNS name as a peer endpoint, wg-quick will resolve the name and then _replace the name with the ip address_. My IP address changes frequently and I have a script to update the A record when it does, but wireguard didn't have built in support for just keeping the domain name aroun…
Earlier quoted context omitted.
> If you use a DNS name as an endpoint, and that DNS entry changes, you have to refresh it. This is really frustrating for me. If you put a DNS name as a peer endpoint, wg-quick will resolve the name and then _replace the name with the ip address_. My IP address changes frequently and I have a script to update the A record when it does, but wireguard didn't have built in support for just keeping the domain name aroun…
What's the alternative? Allow the Wireguard user to specify an FQDN in the config file and require Wireguard to perform a DNS query on every outgoing packet to check if the data in the RR has changed?
> take a look at an OpenVPN config file and you will appreciate this shortness OpenVPN config files can be pretty small once you remove all the comments (my server is 22 lines) That being said, I like WireGuard. I've switched over a lot of stuff to it. It does have some issues though: * Road warrior configurations aren't easy. If you use a DNS name as an endpoint, and that DNS entry changes, you have to refresh it. T…
> take a look at an OpenVPN config file and you will appreciate this shortness OpenVPN config files can be pretty small once you remove all the comments (my server is 22 lines) That being said, I like WireGuard. I've switched over a lot of stuff to it. It does have some issues though: * Road warrior configurations aren't easy. If you use a DNS name as an endpoint, and that DNS entry changes, you have to refresh it. T…
Imo the free tier of tailscale is the best way to consume wireguard for me.
An even simpler way of routing a certain container through wireguard, without needing to create a docker network and bind it to wg manually: https://github.com/pirate/wireguard-docs#example-client-cont...
Note that when using docker-compose you don't need any manual docker network calls with my solution as well. The systemd-network and docker-compose files suffice.
imo the sidecar solution is hard to beat if you don't need the features that the separate network provides.
> take a look at an OpenVPN config file and you will appreciate this shortness OpenVPN config files can be pretty small once you remove all the comments (my server is 22 lines) That being said, I like WireGuard. I've switched over a lot of stuff to it. It does have some issues though: * Road warrior configurations aren't easy. If you use a DNS name as an endpoint, and that DNS entry changes, you have to refresh it. T…
>> take a look at an OpenVPN config file > OpenVPN config files can be pretty small That particular jab was pretty strange. The very first example in the OpenVPN documentation is of a server config: dev tun ifconfig 10.8.0.1 10.8.0.2 secret static.key That's three lines. The client needs a "remote" entry as well. How much more terse can it get? There are many applications with complex configuration formats, but OpenV…