Earlier quoted context omitted.
No degraded performance in my experience, at least not visibly. Only drawback is more battery consumption.
About how much more consumption?
Building a Simple VPN with WireGuard with a Raspberry Pi as Server
81–90 of 126 posts
Re: Building a Simple VPN with WireGuard with a Raspberry Pi as Server
#82Earlier quoted context omitted.
I set my Pi4 up with wireguard+pihole recently. I think pihole does nothing 99.99% of the time, so I can’t speak to how performance is in worst case scenarios, but wireguard seems fine. I get about 25 Mbps up/down (speedtest.net with a single client, so assume it’s 25 Mbps aggregate. Not a lot for hefty file transfers but comfy enough for VNC to multiple hosts. The big win is in decreased latency. I don’t have good q…
Is your no vpn sample still on the same home network? Or are you comparing your mobile data or another network to your home network (through vpn) If the former is true, that seems like quite a significant penalty to pay for using wg.
Re: Building a Simple VPN with WireGuard with a Raspberry Pi as Server
#83Earlier quoted context omitted.
Open source just means you have or can get access to the source. FOSS Free open source software also gives you the rights to use the source.
RMS wrote about free software and open source (which is different): https://www.gnu.org/philosophy/open-source-misses-the-point....
"Free software" is also an absolutely awful term because for 99.9% of the population "free" means it didn't cost them any money. This will never change no matter how hard RMS tries because its a very common and understood word.
Re: Building a Simple VPN with WireGuard with a Raspberry Pi as Server
#84I have been using ZeroTier( https://www.zerotier.com/ ) much simpler solution to setup.
Re: Building a Simple VPN with WireGuard with a Raspberry Pi as Server
#85Earlier quoted context omitted.
Open source just means you have or can get access to the source. FOSS Free open source software also gives you the rights to use the source.
FOSS implies restrictions on the developer in the service of end-user freedom, eg. copyleft and anti-tivoization. Open source implies nearly unlimited rights for the developer, like BSD, MIT, or Apache. With these idiosyncratic restrictions (noncommercial, research only, do no evil, etc) we typically say “disclosed source.”
No it doesn't. You're thinking of copyleft licenses. FOSS is not synonymous with copyleft; many FOSS licenses (recognized as such by RMS and the FSF) are not copyleft.
Re: Building a Simple VPN with WireGuard with a Raspberry Pi as Server
#86Earlier quoted context omitted.
You don't have to route all your traffic through the VPN (though it's unclear from the question whether or not that's the goal). If he only wants access to resources on his home network, it's entirely feasible to set that up while still routing other traffic out through the public internet via your ISP/carrier.
I should have mentioned above, but I want to use pihole as well so ideally I’d route almost all my traffic through my home vpn.
Re: Building a Simple VPN with WireGuard with a Raspberry Pi as Server
#87Earlier quoted context omitted.
Here is someone's benchmark from reddit: https://www.reddit.com/r/WireGuard/comments/eeafds/wireguard... (tl;dr "Avg: 829 Mbps")
That's for a Raspberry Pi 4, which should have a pretty drastic performance difference from the Raspberry Pi 3 mentioned in the article since only one of those has proper gigabit Ethernet. It does seem pretty good though. I'm having trouble getting past 25 Mb/s in, 100 Mb/s out on my Edgerouter X.
(The Pi 3 also is 4 years old now and you wouldn't want to buy it today)
Re: Building a Simple VPN with WireGuard with a Raspberry Pi as Server
#88I think there's some issues in the config. First of all, at least one of the CIDRs is wrong ("Address = 10.200.200.2/24"). Also by setting AllowedIPs to to 10.200.200.0/24 in the client , only traffic to that subnet will actually go through the VPN, not all traffic. Isn't there also some missing host/RPI system so that the 10.200.200.0/24 can route to the public internet? If someone has an example of a full VPN confi…
> First of all, at least one of the CIDRs is wrong ("Address = 10.200.200.2/24"). Also by setting AllowedIPs to to 10.200.200.0/24 in the client, only traffic to that subnet will actually go through the VPN, not all traffic. Not sure what your issue is with the address line. As for the AllowedIPs, that's intentional. From the first lines of the article: > An Linux Laptop that should use the VPN only accessing network…
Re: Building a Simple VPN with WireGuard with a Raspberry Pi as Server
#89Earlier quoted context omitted.
FOSS implies restrictions on the developer in the service of end-user freedom, eg. copyleft and anti-tivoization. Open source implies nearly unlimited rights for the developer, like BSD, MIT, or Apache. With these idiosyncratic restrictions (noncommercial, research only, do no evil, etc) we typically say “disclosed source.”
> FOSS implies restrictions on the developer in the service of end-user freedom No it doesn't. You're thinking of copyleft licenses. FOSS is not synonymous with copyleft; many FOSS licenses (recognized as such by RMS and the FSF) are not copyleft.
Re: Building a Simple VPN with WireGuard with a Raspberry Pi as Server
#90Earlier quoted context omitted.
I do this fairly often with an Algo vpn. Sometimes the initial connection setup suffers, but there can be a gain from adblocking if you use PiHole. I’ve had to turn it off a few times when some apps do geo-ip lookup and give me errors about not knowing whether I’m in the US. Otherwise the main drawback is battery usage.
Yeah I should have mentioned above but one of the reasons I want to do this is for pihole on the go. How much more battery usage would you estimate your setup causes?