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

    PIA UP but unable to route to it

    Scheduled Pinned Locked Moved OpenVPN
    3 Posts 2 Posters 583 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.
    • L
      litlelee9
      last edited by litlelee9

      Greetings all, I am having troubles routing particular traffic to my PIA Gateway. The OpenVPN, Interface, Gateway are all showing enabled and up however when I put a rule in to route a particular host to it, it does not seem to be working - all traffic continues to route out to my WAN. I have followed the guides, and pretty sure I have it setup properly. I used to do this via ExpressVPN but just made the switch over to PIA, and cannot for the life of me figure out where I am going wrong. I have the FW rules configured along with the outbound NAT...the major difference I see between ExpressVPN and PIA, is that I appear to be getting an internal virtual IP address which I did not get with ExpressVPN. If I run a ping test to the virtualIP via the PIA openVPN interface, that passes. Anything beyond that (1.1.1.1, 8.8.8.8, etc) fails. And of course when I do an IP lookup, it comes back as my WAN IP and not my PIA VPN IP. Any thoughts?

      2022-08-21 07_59_29-pfSense-router.lee.local - Status_ Interfaces - Brave.png

      2022-08-21 08_00_01-pfSense-router.lee.local - Status_ Gateways - Brave.png

      2022-08-21 08_00_31-pfSense-router.lee.local - Status_ OpenVPN - Brave.png

      2022-08-21 08_00_50-.png

      2022-08-21 08_01_17-pfSense-router.lee.local - Firewall_ Rules_ LAN - Brave.png

      2022-08-21 08_01_50-pfSense-router.lee.local - Interfaces_ PIA_Amsterdam (ovpnc1) - Brave.png

      2022-08-21 08_02_27-pfSense-router.lee.local - Diagnostics_ Ping - Brave.png

      2022-08-21 08_02_54-pfSense-router.lee.local - Diagnostics_ Ping - Brave.png

      L 1 Reply Last reply Reply Quote 0
      • L
        litlelee9 @litlelee9
        last edited by

        @litlelee9 Update - I tore down the PIA config and started from scratch - originally I re-purposed my old expressVPN config and was wondering if something was stale (even after reboot). I am now able to ping out from the VPN interface, however my FW rules that are configured to route particular hosts through the new PIA gateway don't seem to be taking effect as I am still showing my public ISP address rather than my PIA public IP address. I'll take the small victories...but not sure why my policy based routes aren't working...

        O 1 Reply Last reply Reply Quote 0
        • O
          Owen82 @litlelee9
          last edited by

          @litlelee9 Your first ping test seemed to be pinging itself - is that why it seemed to work but actually wasn't?

          If you are policy routing and the FW rules are still using the old gateway can you just go change it? You should see in the gateway column on the LAN etc interface which rules have a GW defined. Sorry if that's stating the obvious.

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