Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    OpenVPN with Torguard ignoring LAN rule to bypass VPN for specific hosts

    Scheduled Pinned Locked Moved OpenVPN
    3 Posts 2 Posters 747 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      paulduthie
      last edited by paulduthie

      I setup PFSense to use a Torguard VPN using this guide

      https://torguard.net/article/254/pfsense-openvpn.html

      It's all working, but Netflix thinks I am using a proxy - I assume because the IP I am coming from is marked as a known proxy/bypass IP. That's fine.

      I did some research about how to get certain hosts to bypass the VPN and go directly out via my normal gateway. I found several posts that outlined this procedure:

      1. Create an Alias for the hosts I want to bypass the VPN for - done

      2. Create a LAN firewall rule with the following settings:
        Interface - LAN - done
        Source - Single host or Alias, set to created Alias - done
        Set Advanced Option - Gateway to WAN Gateway - done

      I've done this, and traffic from the hosts I specified is still sent over the VPN.

      What am I missing - I've tried options from about 20 other hosts with no results.

      WIll keep looking into it, but does anyone have any suggestions?

      Edit: In the rules list, the created rule is not showing any traffic as having transited it, and yes it is the first rule in the list (below the Anti-Lockout rule)

      1 Reply Last reply Reply Quote 0
      • B
        bcruze
        last edited by

        I have this working with no issue with three other providers you probably better post some screenshots

        P 1 Reply Last reply Reply Quote 0
        • P
          paulduthie @bcruze
          last edited by paulduthie

          @bcruze
          Thanks for the reply.

          Lesson to myself. Don't add IP's to an alias list when it's late at night and you are tired..

          192.158.0.10 will not work for the desktop with the IP address 192.168.0.10 for some strange unknown reason...:)

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.