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

    OpenVPN client (to ExpressVPN) kills IPv4 access to the internet

    Scheduled Pinned Locked Moved OpenVPN
    5 Posts 2 Posters 786 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.
    • A
      adeydas21
      last edited by

      Hi

      I am new to pfSense and am trying to setup an OpenVPN gateway using ExpressVPN for 1 VLAN, aka, any devices on that VLAN would route traffic through ExpressVPN.

      Following the instructions on the ExpressVPN website, I was able to get the tunnel up. However, as soon as the tunnel was up, none of the devices in an VLAN or LAN could access the internet. Since I also have ipv6, I could check that it was still routing on an ipv6 address but there was no ipv4 address.

      I am at wits end on what do here, would appreciate your help.

      Thanks!

      V 1 Reply Last reply Reply Quote 0
      • V
        viragomann @adeydas21
        last edited by

        @adeydas21
        I assume, you didn't follow the instructions exactly. Which one?

        A 1 Reply Last reply Reply Quote 0
        • A
          adeydas21 @viragomann
          last edited by

          @viragomann the forum spam filter wont let me post a link but its the first link on google if you search with "How to set up ExpressVPN on pfSense (OpenVPN)" (with quotes).

          V 1 Reply Last reply Reply Quote 0
          • V
            viragomann @adeydas21
            last edited by

            @adeydas21
            Seems all fine in that guidance.

            Did you assign the interface (chap. 3) and configure the outbound NAT properly?

            A 1 Reply Last reply Reply Quote 0
            • A
              adeydas21 @viragomann
              last edited by

              @viragomann yah, figured out what the issue was. seems like because the routing policy was set to *, it was messing up where to send the traffic. Once I explicitly set the gateways for each of the VLAN's, it worked.

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