I've been running only Linux for 25 years. Any software you think you need that you only can get on Windows you don't. Drop windows, say goodbye to your apps, and explore the alternatives. Try to have fun. A growth mindset helps

That would also print the colon

Edit: missed the separator token. Sorry guys

Here's my testing recommendations

Testing methodology

To get consistant results, use a consistent method of test. If you're downloading a large file, always test by downloading that same file from that same source. If you're using a speed test service, use the same speed test service with the same server. If you're using a tool like iperf3, always use the same tool against the same iperf server.

Potential issues

Networks can fail from hardware issues, software issues and infrastructure issues. Since you don't control 99.9% of the infrastructure if the internet is involved, lets leave that for the last option.

Hardware Issues

The hardware involved you control are mostly your NIC, and your Remote Connection. For wired ethernet at home, this is likely a physical ethernet port on your computer on one end, and another physical ethernet port on a switch/router/ap provided by your ISP.

Testing Wired Hardware Issues

• Using the same switch and cable, run a speed test on another computer. If the issue persists, the problem is not with your computer, if it resolves, its related to your computer.
• Using the same computer and cable, run a speed test on another switch. If the issue persists, its not the switch or cable, its your computer, if it resolves, its not your computer.
• Using the same computer and switch, use a different cable. If the issue persists, it's not the cable and its either your computer or switch, if it resolves, its the cable.

With these three you can figure out what device is causing the problem.

Testing Wireless Hardware Issues

The hardware involved is the wireless NIC in your computer, the environment your wifi signal is in, and the wifi AP. The steps are much the same as testing for a wired issue

• Using the same AP and physical location, run a speed test on another computer. If the issue persists, the problem is with the AP or location, if it doesn't it may be your computer
• Using the same computer and physical location, run a speed test on another AP. if the issue persists, the problem is with your computer or location, if it resolves, it may be the AP
• Using the same computer and AP, run a speed test in another physical location. If the issue persists, the problem is with the computer or AP, if it resolves it may be the environment

Software Issues

The issue could be software related. Something like the drivers running on your laptop or connection point.

Testing Computer Drivers

You've already done this for your computer by dual booting. This proves the issue is not driver related, since the problem persists with two different sets of drivers.

Testing Connection Point Drivers

• You have less control over the drivers on your switch/router/ap. If the hardware tests resolve when using a different AP, then you can attempt a firmware upgrade/downgrade before replacing the physical device. This isn't usually worth the hassle since ISPs are quick to replace them with a service call.

Testing Computer Configuration

Your network settings could be misconfigured.

• If you are using DHCP, turn it off, and enforce a speed negotiation, IP address, subnet mask, and DNS server and try again. If the issue persists, then it's likely not related to your configuration. If it resolves it probably is.
• If you are using a static configuration, turn it off and use DHCP. If the issue persists, it's likely not related to your configuration, if it resolves, it probably is

Infrastructure Issues

If your home network is more sophisticated then an ISP provded router/switch/ap combo connected to everything over wifi and ethernet, theres more devices to troubleshoot. But if you have something like this, you probably already know what you're doing a little bit and wouldn't be making this post. But who knows! Re-run the process isolating each device and replacing it with something known good to identify whats causing the problem.

As for the internet, it's not a stable and safe place. Speeds vary drastically day to day. Internet weather happens and partial outages occur regularly. Don't forget that the service your using to speed test could be the issue itself. It's another component to isolate and test.

Process

Use the above steps to identify what device is causing the problem, and if its a hardware or software issue. Hardware issues are mostly resolved by replacing devices, while software issues are resolved with software updates and configuration changes.

Good luck and god speed!

Routing takes place on layer 3 (ip) so destinations are ip networks and hosts.

Each packet you create has a destination IP. Your computer looks at your route table to see where it goes by matching the destination ip with each network. It will be sent to the most specific match first and your default gateway last.

If you're default gateway is you're vpn server via your vpn interface then you just need to add more specific route for destinations of interest through a different gateway (you're router) via the physical interface

Raw disk access is a privilege in Linux, usually reserved for root.

You could have root change the permissions on the directory to allow another user or group write access.

goes to Google, on the raw network, and on the VPN.

You can't "go" to a destination on two networks in a single request. It's all packets on a wire, if it comes from two sources, it was two requests.

Unless you mean two different requests. As in while on the VPN everything is tunneled, and while not on the VPN it's not, but this is the opposite of what the OP was asking for. He wants the VPN on for some use cases, and off for others. That's split tunneling.

He'll likely wind up with difficulties around trying to figure out which destinations he doesn't want routed through the VPN, because there's no way to do it by protocol, since routing happens on layer 3, not 4 or 7. He'll likely need to know those address in advance.

Interesting. There's no difference in my dialect.

One NIC is fine

Told my wife and kids they can run whatever they want if they don't involve me. If you want me to help with computer issues then I'm installing Linux.

If you don't want that, you better learn how to computer because you're on your own

Canadian with a shitty mobile keyboard, that's all.

Swipe keyboard. It picks random yours, and I'm exhausted from flying all day so I didn't proof read.

Yes that's called routing.

You don't bind it to a NIC, you specify the destinations you want forwarded to each interface. Your VPN connection is just another interface.

If you're looking for good docs, you may want to Google split tunnel vpn, and also bone up on your networking.

A few static routes should get you what you need