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

    Bypass VPN by port, not IP

    Scheduled Pinned Locked Moved OpenVPN
    5 Posts 3 Posters 861 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.
    • RyanMR
      RyanM
      last edited by

      My pfSense appliance is configured with a VPN client to route the majority of my traffic over it.

      I bypass the VPN for AWS, Netflix, and Plex, but I do this using IP/Hostname. I would like to specify traffic to bypass the VPN by port. Is this possible?

      I tried to configure the firewall rules for the LAN interface to do this:
      0_1531349754333_Screen Shot 2018-07-11 at 4.53.57 PM.png

      But it does not seem to be working. Is there something else I might be missing?

      1 Reply Last reply Reply Quote 0
      • jahonixJ
        jahonix
        last edited by

        Move that rule on top of the greyed-out rules below the anti-lockout.
        There's probably another rule catching the traffic already.

        1 Reply Last reply Reply Quote 0
        • DerelictD
          Derelict LAYER 8 Netgate
          last edited by

          And you almost never need to set a source port. It is almost always a mistake.

          Chattanooga, Tennessee, USA
          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
          Do Not Chat For Help! NO_WAN_EGRESS(TM)

          RyanMR 1 Reply Last reply Reply Quote 1
          • RyanMR
            RyanM @Derelict
            last edited by

            @derelict said in Bypass VPN by port, not IP:

            And you almost never need to set a source port. It is almost always a mistake.

            I think this is a good call. I am going to try removing the source port and see if it makes a difference. If it still doesn't then I will move it above the other rules, but that shouldn't be the problem since the other rules are for AWS/Netflix and my Plex server.

            1 Reply Last reply Reply Quote 0
            • DerelictD
              Derelict LAYER 8 Netgate
              last edited by

              The most-specific rules should generally be at the top to prevent something more general from matching first.

              Chattanooga, Tennessee, USA
              A comprehensive network diagram is worth 10,000 words and 15 conference calls.
              DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
              Do Not Chat For Help! NO_WAN_EGRESS(TM)

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