"WSL2 uses Hyper-V virtual networking and therein lies the problem"
Pretty much sums it up.
Linux under WSL2 can be leaking
111–120 of 194 posts
Re: Linux under WSL2 can be leaking
#112Earlier quoted context omitted.
Good question. OTOH, did anyone ever consider the average pollution of the banking system? 10.000th of banks, 200+ central banks, BIS, IMF, ECB, etc, etc. Millions of employees, millions of desktops & servers, day-in-day out. Anyone with a link to a guestimate?
The Bitcoin network allegedly uses the amount of energy as the whole country of Denmark. This includes heavy industries like aluminum smelting that more or less use as much power as they are allowed to. A Bitcoin transaction uses about 1,005 kWh, while 100,000 VISA transactions use 169 kWh, according to https://www.statista.com/statistics/881541/bitcoin-energy-co...
Unclear what goes into calculating the visa transactions. Is it just the literal cost of sending the bits over the wire? Does it include the cost of servers, man-power, real estate, etc?
Re: Linux under WSL2 can be leaking
#113A bit off topic, but this sort of transparency is why I don't mind paying $6 / mo for a vpn when mullvad's competitors are much cheaper. Their wireguard support is great, and their speeds are much faster than what I got through openVpn on pia.
I vehemently agree with your position. It's also worth mentioning (albeit anecdotal) their prompt and verbose support when/if necessary.
Re: Linux under WSL2 can be leaking
#114The title is wrong. The VPN traffic does NOT leak. What leaks is the traffic that the VPN software tries to block when the VPN connection is not active. Mullvad uses Windows Firewall to block all internet access if VPN is not active (if the user configured so) and WSL2 bypasses this by not going through Windows Firewall. When the VPN is active, WSL2 traffic IS tunneled through the VPN. UPD: The solution may be to hav…
A good reminder that you really want proxying done on a separate device (router, Raspberry Pi, etc) physically between the endpoint and the internet.
Does anyone have a raspberry pi hardened disk image for this? I just don't have time to troubleshoot all these things anymore
Re: Linux under WSL2 can be leaking
#115Earlier quoted context omitted.
Because in my opinion Windows is terrible :) For many reasons. Linux users don't use Nvidia if they are interested in the modern desktop use case. That's a well known factor. If someone migrates to Linux using Nvidia, chances are high they'll change it to AMD on the next GPU upgrade.
> Linux users don't use Nvidia if they are interested in the modern desktop use case. Which rules out anyone who wants to game or do CUDA stuff. Everyone is welcome to their own opinions and preferences, but if you ask me, if the response to a request to use the most powerful/performant graphics cards is to switch to AMD (and AMD has some good cards but Nvidia’s are better and OpenCL can’t compete with CUDA when it c…
I didn't see an answer that explains how WSL is better than Linux proper, at least not in case when you don't care about Windows itself.
AMD is fine for gaming, I'm using 5700XT on Linux for playing games. And AMD will match Nvidia higher end cards next month. So I don't see any reason to use Nvidia for that.
WSL offers nothing for gaming or similar use cases that regular Linux can't. If you need to use CUDA with Nvidia hardware, you can do it on Linux proper just fine, you don't need WSL for it - Nvidia provide support.
Re: Linux under WSL2 can be leaking
#116Earlier quoted context omitted.
>There's no way the banking and finance industry doesn't compete emissions wise with bitcoin not on a per transaction basis, which is the only relevant measure because the banking system supports a lot more people than bitcoin does. A single bitcoin transaction uses 610.20 kWh right now, which is comparable to the energy consumption of an average US household over 20 days.[1] Also for a comparison of scope, Tenpay, T…
Luckily there is a mechanism for resource allocation and it is called price. I pay for 1 MWh, you pay for 1MWh and it doesn't matter what we use the energy for. If you have an issue with how the energy is generated take it up with your local government.
Most Bitcoins are mined in places I do not live, since my electricity prices are nowhere near economical to mine in.
Re: Linux under WSL2 can be leaking
#117The title is wrong. The VPN traffic does NOT leak. What leaks is the traffic that the VPN software tries to block when the VPN connection is not active. Mullvad uses Windows Firewall to block all internet access if VPN is not active (if the user configured so) and WSL2 bypasses this by not going through Windows Firewall. When the VPN is active, WSL2 traffic IS tunneled through the VPN. UPD: The solution may be to hav…
A good reminder that you really want proxying done on a separate device (router, Raspberry Pi, etc) physically between the endpoint and the internet.
This sounds like working as designed and not a flaw. If your Linux box needs a firewall then put one on it. As the article says, the VM is using Hyper-V networking so it is likely that the connection is either bridged with a virty software switch or is NATted in some way but with a short cut through the host firewall. If the VM has an IP on your LAN it is bridged and if it doesn't and you don't have to fiddle with your internet router then NAT is in play.
Linux has lots of options for firewalling. For Windows sysadmins, firewalld with a GUI could be a reasonably familiar option. Failing that, ufw is quick and reasonably easy for simple use cases. If you are feeling macho, then roll your own with iptables or nftables. The last time I did that properly was with ipchains ...
Re: Linux under WSL2 can be leaking
#118Earlier quoted context omitted.
The title is correct. For example, a remote attacker could induce the transmission of unencrypted packets by taking the tunnel down by means of DoS attack. Basically, the tunnel doesn't leak under ideal conditions, with non-ideal conditions being trivial to induce. For example, StrongSwan (IPSec) talks about this in their best practices page here: https://wiki.strongswan.org/projects/strongswan/wiki/Securit... The St…
If you were to inspect the Mullvad client and how it works on Linux, you'd find that it uses nftables to ensure that traffic only flows through the tunnel. The issue here is that a similar OS provided construct doesn't do that on Windows.
[deleted]
Re: Linux under WSL2 can be leaking
#119Earlier quoted context omitted.
The Bitcoin network allegedly uses the amount of energy as the whole country of Denmark. This includes heavy industries like aluminum smelting that more or less use as much power as they are allowed to. A Bitcoin transaction uses about 1,005 kWh, while 100,000 VISA transactions use 169 kWh, according to https://www.statista.com/statistics/881541/bitcoin-energy-co...
Unclear what goes into calculating the visa transactions. Is it just the literal cost of sending the bits over the wire? Does it include the cost of servers, man-power, real estate, etc?
It's basically the cost of Visa running divided by the number of transactions they do. So yes it includes everything. You don't need to play silly tricks like that to make Bitcoin look bad. Bitcoin uses similar or more energy than the banking system while processing vastly fewer transactions. Somehow people can't comprehend how ridiculously inefficient bitcoin transactions are.
Re: Linux under WSL2 can be leaking
#120Earlier quoted context omitted.
Is Windows firewall supposed to apply to WSL? I never expected that! I'm serious - I run a different firewall on my onlinux. Can you confirm that WSL is supposed to be dealing with (the nightmare) of the windows firewall for internet access? How does fedora / ubuntu etc coordinate / know to do this?
It's somewhat unintuitive that a virtualized guest can circumvent the host's firewall/network stack when the guest doesn't have an explicitly bridged or passthrough'd physical adapter.
The host is the hypervisor though isn't it? Not the Windows inside it.