The main network interface seems to be overlapped onto the same interface as windows, so for instance you can access the "other side" using localhost. But apparently, it can run wireguard if you build the module yourself, which is interesting. Was playing with WSL2 a bit - apparently this version runs a full VM, but it has a proprietary kernel and seemingly no modules loaded by default. I also followed my usual yabs standard practice of creating a new user just for that, but noticed that under WSL2, even if you su to a new user, you still have the windows permissions of the user that ran wsl, so it seems a bit dangerous still. I'm almost tempted to try it out on my work machine (Ryzen 7 5800X, 64GB RAM, 3080 12GB and 4x2TB Samsung 980 PRO, the newest 2 are striped in a RAID0), but I have a very strict rule about not installing anything not work related. Uztelecom | Tashkent, UZ (10G) | 235 Mbits/sec | 304 Mbits/sec |Ĭlouvider | NYC, NY, US (10G) | 324 Mbits/sec | 522 Mbits/sec |Ĭlouvider | Dallas, TX, US (10G) | 187 Mbits/sec | 476 Mbits/sec |Ĭlouvider | Los Angeles, CA, US (10G) | 195 Mbits/sec | 285 Mbits/sec | NovoServe | North Holland, NL (40G) | 527 Mbits/sec | 538 Mbits/sec | Scaleway | Paris, FR (10G) | 525 Mbits/sec | 526 Mbits/sec | Provider | Location (Link) | Send Speed | Recv Speed | PingĬlouvider | London, UK (10G) | 532 Mbits/sec | 526 Mbits/sec | Processor : Intel(R) Core(TM) i7-6700K CPU 4.00GHz I didn't even know this was a thing, so I just tried it out on my crappy old desktop: bash yabs.sh |tee yabs1.txt Said: decided to YABS my home pc via WSL2
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |