Hello, all

I’m sorry if there is an FAQ somewhere. My VPN is about enter it’s yearly billing cycle and I thought I would come over here and see if anyone had a better suggestion. I’ve been using IPvanish for the last 10 years and have been pretty satisfied. I picked it by going into the darkweb and seeing what the criminals recommended to each other.

If anyone has other suggestions or tales before I renew, I would love to check it out.

  • opfar.v30
    3•2 days ago

    Njalla, hands down.

    Co-founded by Peter Sunde of The Pirate Bay fame. Run by a great little crew that cares about privacy. They do VPN, domains, and hosting.

    Wireguard and OpenVPN. Your external IP periodically rotates through the pool, but at least all ports are forwarded.

    Too bad almost nobody knows about them. They even have a Wiki page, ffs!

    • @[email protected]
      9•3 days ago

      OVPN is a 1-to-1 feature clone of mullvad (wireguard, multiple device keys, crypto payments/cash in the mail, no usernames/emails, etc.) AND has port forwarding. Switched to them when mullvad sadly closed their ports, no problems since. Can’t live without port forwarding.

      • SunRed
        3•3 days ago

        +1 for OVPN. I switched to them from Mullvad for the same reason. They are also one of the more trustworthy VPNs in my book ever since they actually won a court case proving that they actually practise what they advertise.

    • @[email protected]English
      11•4 days ago

      It’s what I use and it works well for me. It seemed like the best option when I was researching this recently. Plus the icon is cute.

      • sunzu2
        2•4 days ago

        It’s all around goat unless you torrent maniac… You can still torrent without port forwarding, just not at high speeds

    • Phoenixz
      1•2 days ago

      Mullvad apparently no longer supports port forwarding. This better in tailscale?

  • Matt
    2•2 days ago

    Don’t know if Tor proxy front ends like Orbot or Carburetor count as a VPNs. If so, I highly recommend them.

  • @[email protected]English
    26•4 days ago

    IVPN, Mullvad, or Proton. Criminals aren’t necessarily smart, I remember a ghost phone that criminals thought were secure and it was a honeypot. Shoulda used Graphene for free.

  • RiQuY
    8•3 days ago

    I love Mullvad but for some reason they refuse to add reverse split tunneling, so imo the only options are IVPN or Proton.

    Reverse split tunneling gives you the ability of using the VPN only in the apps/programs you select.

    • @[email protected]
      8•3 days ago

      You can set up split tunneling yourself if you run the wireguard/OpenVPN daemon manually and move the “mouth” of the tunnel to a separate Linux network namespace.

        • @[email protected]
          2•2 days ago

          The exact script would depend on the use case; you’d use commands something like this:

          mkdir -p /etc/netns/VPN
sh -c 'echo nameserver 1.1.1.1 > /etc/netns/VPN/resolv.conf'
ip netns add VPN
ip link add tun1 type wireguard
ip link set tun1 netns VPN

          Because the wireguard device was created in the default namespace, it will “magically” remember its birthplace, even after you move its mouth (the tun1 device) to a separate namespace. The envelope VPN packets will keep going in/out in the default namespace.

          ip netns exec VPN wg setconf tun1 /etc/wireguard/vpn.conf
ip netns exec VPN wg set tun1 private-key /etc/wireguard/vpn-key.private
ip -n VPN addr add 192.my.peer.ip/32 dev tun1

          Get the wireguard config file from the VPN website, both mullvad and OVPN have a wizard to generate them. Your assigned private network ip is in the config file. Also get and save your device key.

          ip -n VPN link set tun1 mtu 1420
ip -n VPN link set tun1 up
ip -n VPN route add default dev tun1
ip netns exec VPN su myuser -c 'firefox --no-remote'

          Now all firefox (and only that firefox) traffic will go through the tunnel. Firefox has its own DNS, if you run another app it will use 1.1.1.1.

          I actually do the reverse of this - I create a namespace ETH and move my eth0 device in there and attach dhcpcd to it. Then I create the wireguard tun1 device inside ETH namespace, and move tun1 to the default namespace. Then any software I run can only use the tunnel, because the ethernet device doesn’t even exist there. This keeps the routing table simple and avoids a whole class of issues and potential deanonymization exploits with the split routing table used in traditional single-namespace VPN configurations.