Live data from Hacker News

WireGuard is in net-next

git.kernel.org

191–200 of 208 posts

Re: WireGuard is in net-next

#191
post #111

Earlier quoted context omitted.

On iOS it's still a userspace client, as I understand it, and the additional battery drain was very noticeable for me.

I noticed a HUGE battery drain with other VPN clients like PIA's app or just OpenTunnel, but either my 3 year old iPhone X has a great battery, or the battery drain from WireGuard has been unnoticeable for me.

1 year old iphone 8 here and Wireguard was noticeable (vs no VPN). I did not try other VPNs.

Re: WireGuard is in net-next

#192

Sorry for off topic, but is there any way, how to setup wireguard (or any VPN) to be used for just single app (lets say Firefox) and not system wide on macOS? Something similar to https://github.com/darkk/redsocks with ssh and setting up proxy in Firefox?

Looks like this might help you: https://superuser.com/a/241200

Redsocks is a transparent proxy, though. That'll redirect system-wide. I think you're thinking of your basic socks proxy - `ssh -D`.

Re: WireGuard is in net-next

#193

Earlier quoted context omitted.

I use ansible and salt to provision servers. It works great. It has limited to no use to manage users and their passwords or authorizations, their control over machines, remote access to a share and zillons other usages you need specialized software for. AD has it all natively.

People with large environments that needs to be managed homogenously would beg to differ. How else would people manage these things large scale? It's exactly the kind of functionality that this software provides. Expressing rules in code might be radically different to someone used to a product like AD, but the learning curve is pretty quick and it is inherently more powerful.

I do not know about products for large environments. Our is arguably medium (around 10,000 servers) and we use solutions where each does its thing, without any reasonable cooperation between the solutions:

- users management? NIS

- configuration management? ansible / salt

- machines management? none (we use a homebrew system based off salt)

- shared storage? NFS

- policies? salt or ansible if they are common to groups of machines, or NIS if for people

etc.

I would love to have a unified tool (similar to what Zen was trying to do 20 years ago) but I do not know any. What AD does for Windows is nice (though I do not use Windows servers but I see their management from the side), Linux was intended to be standalone and this is what there are so many specialized, but disconnected management systems.

Re: WireGuard is in net-next

#194
post #124

Earlier quoted context omitted.

pfSense is a FreeBSD downstream, right? First you'd have to port Wireguard to FreeBSD. Or you could run the userspace server, but expect poor performance.

Exactly. Netgate has long said that they won't touch it until it's production-ready; they keep pointing to the warning messages in WireGuard saying that it's beta and when the time is right, they'll consider it. I'm happy they're being cautious. The inclusion in the Linux kernel is perhaps (to Netgate) a sign that things are headed in the right direction. As far as FreeBSD, all that exists today is a userspace packag…

Netgate here, we’re already working on a kernel-resident version for FreeBSD (and thus, pfsense.)

Re: WireGuard is in net-next

#195
post #122

Earlier quoted context omitted.

On Android this can be easily achieved by Tasker. Personally I have the luxury of running the VPN server at home, so I can just always leave it on.

Why does this allow you to allows leave it on?

Well since I connect to my home network anyway I can just leave it on at home and there's no difference in performance.

Re: WireGuard is in net-next

#196

If anyone wants some more docs and examples for Wireguard usage, I made some here: https://github.com/pirate/wireguard-docs - how it works internally - how the routing works in different topologies - a few complex and simple example setups - performance expectations - security model, key & config distribution - setting up wireguard for, or inside of docker - GUI tools and other wireguard-related software - links to o…

this is a really nice resource, thanks a lot!

Re: WireGuard is in net-next

#197

Earlier quoted context omitted.

People with large environments that needs to be managed homogenously would beg to differ. How else would people manage these things large scale? It's exactly the kind of functionality that this software provides. Expressing rules in code might be radically different to someone used to a product like AD, but the learning curve is pretty quick and it is inherently more powerful.

I do not know about products for large environments. Our is arguably medium (around 10,000 servers) and we use solutions where each does its thing, without any reasonable cooperation between the solutions: - users management? NIS - configuration management? ansible / salt - machines management? none (we use a homebrew system based off salt) - shared storage? NFS - policies? salt or ansible if they are common to group…

Right, but NIS and NFS are just protocols. You might as well have said DNS and IMAP. There are also services behind those protocols that needs to be managed. This is what Puppet(/Chef/Salt) does.

Take NFS as an example. Let's say all your users with meets certain criteria needs an NFS share named after their user and with an ACL that gives some running software access to drop files there. Maybe this share should be mounted on every machine where this software is present, regardless of who own it or where it runs. You write this rule in Puppet code and then it is guaranteed to be true for everyone forever.

Note that we didn't even need to feed Puppet any new information to do this. All the data required to implement the change was already in the configuration database. (Which is not even a real database but only the result of existing rules.)

Compare with a product such as AD. It doesn't really do the management for you. You can store the data there, but then you need to write a script to implement this change across your server farm. This need to be maintained, and regularly checked re-run to check for changes. Someone has to schedule this. When conditions change, the software which got access changes id, or is installed in another way, the script needs to be maintained accordingly.

Having this version controlled adds another aspect to this. Since everything is text, if you find this rule you can follow the commits and see exactly who brought this into production and when.

It's interesting that you refer to Linux as a standalone system. Linux and other unices have their roots not in single instance "personal computers" but in multi user environments. This is why to this day Linux admins treat everything as text and work mostly by text commands. Others may find this archaic but without this and without version control we could never maintain large homogenous environments. You might say that automation is built into the very way we use these systems.

Re: WireGuard is in net-next

#199
post #156

Earlier quoted context omitted.

> WireGuard is much faster than OpenVPN Not relevant for most home internet connections > much simpler to set up than OpenVPN +1 > and it's much, much more secure than OpenVPN. That’s uselessly vague. Do you mean the protocol, the implementation approach, the underlying crypto, or what?

>> WireGuard is much faster than OpenVPN > Not relevant for most home internet connections Why it is not relevant?

Openvpn in UDP mode running on an rpi can saturate a home connection and provide low enough latency for voice.

Re: WireGuard is in net-next

#200

If anyone wants some more docs and examples for Wireguard usage, I made some here: https://github.com/pirate/wireguard-docs - how it works internally - how the routing works in different topologies - a few complex and simple example setups - performance expectations - security model, key & config distribution - setting up wireguard for, or inside of docker - GUI tools and other wireguard-related software - links to o…

> (they do have docs, they're just hidden away in the manpages) I feel old and obsolete.

For most users, if it's not Google-able and in nice HTML format it doesn't exist ;)
Post reply on HN