nordvpn-linux VS spn

Hey, this might be relevant to you https://github.com/NordSecurity/nordvpn-linux/issues/7

https://github.com/NordSecurity/nordvpn-linux/tree/main/mesh...

The standard linux vpn clearly has some exitnode capabilities.

Yeah I think they removed it with this commit about a month ago. I don't think they're going to bring it back.

I think they removed the user/pass login with this commit two weeks ago:

This all sounds like a step forward for Nord apps and fingers crossed going open source will improve the overall quality of NordVPN service. Maybe someone in our community already checked the code [https://github.com/NordSecurity/nordvpn-linux])? Overall, what are your thoughts about this news? Do you find it useful or maybe you don’t care about it?

You could try creating an issue here https://github.com/NordSecurity/nordvpn-linux/issues

Port forwarding on router without the use of a VPN is not what I was talking about dude. Linux has always had the ability to route iptables and software like Portmaster SPN, have paced the way for granular control at the packet level. So before you respond, take a look at the protocol of Portmaster SPN and consider what I’m saying, I’m trying to help you bro, not fight. https://safing.io/spn/

Safing develops the privacy firewall „Portmaster“ and runs the „Safing Privacy Network“ (SPN) which joins features of Onion Routing and VPN. The company has a transparent business model and the code is open source. We are an official reseller of Portmaster Unlimited.

If you're up to trying something new, we've built a technology to replace consumer privacy VPNs: https://safing.io/spn/

Technical summary of the SPN (Safing Privacy Network):

- A Privacy Network aimed at use cases "between" VPN and Tor.

- Uses onion encryption over multiple hops just like Tor.

- Routes are chosen to cover most distance within the network to increase privacy.

- Exits are chosen near the destination server. This automatically geo-unblocks in many cases.

- Exclude apps and domains/entities from using SPN.

- Change routing algorithm and focus per app.

- Nodes are hosted by Safing (company behind Portmaster) and the community.

- Speeds are pretty decent (>100MBit/s).

I have been messing around trying to make a secure browsing instance that has a few browsers and some VPN clients like Proton VPN and and Portmaster by Safing and after going through a long path of errors and wrappers written in Python i think the issue stopping these tools from running properly is accessing the hosts network from the container. Looking at these stack overflow questions lead me to this conclusion: nmcli in a docker container Enabling network manager inside docker

but SPN is open source as well

There is really so much. Check their website. They do a better a jop at that : https://safing.io/spn/

I read their info and tutorials. Honestly I don't put completely my trust in the onion routing system. Does anyone use this software and can give a balanced opinion on speed, usage, problems, and overall quality of service? https://safing.io/spn/

There are 3 big parts:

- The firewall itself with rules, filter lists, and so on - https://safing.io/features/

- Secure DNS (DoT/DoH resolver) - https://safing.io/features/

- "SPN": Optional paid VPN alternative similar to Tor, our source of revenue - https://safing.io/spn/