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

    No Subnet to Subnet routing when Openvpn client is configured

    Scheduled Pinned Locked Moved OpenVPN
    3 Posts 2 Posters 969 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
      LordCadbury
      last edited by

      Hi

      I have the below configured on my pf box and routing between the subents was fine until I added an OpenVPN client…

      Em1 > WAN, 82.XX.XX.XX
      Em0 > LAN, 192.168.1.1
      Em0_vlan20, 192.168.20.1
      Em0_vlan30, 192.168.30.1

      I've followed the 'how to guides' to configure this for a single LAN and I can force all traffic from the VLAN 20 (192.168.20.X) out over the VPN. I changed the outbound NAT mappings but under the firewall rules section for VLAN 20, I had to modify the Default gateway setting under the firewall section to a gateway created for the VPN. Now I can't ping from the VLAN 20 subnet to the VLAN 30 subnet, the route goes out to the VPN, I can however ping from inside the VLAN 30 subnet to VLAN 20 sub.

      Does the above make sense?

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

        https://doc.pfsense.org/index.php/What_is_policy_routing

        And, in particular:

        https://doc.pfsense.org/index.php/Bypassing_Policy_Routing

        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
        • L
          LordCadbury
          last edited by

          @Derelict:

          https://doc.pfsense.org/index.php/What_is_policy_routing

          And, in particular:

          https://doc.pfsense.org/index.php/Bypassing_Policy_Routing

          I had made an attempt at this previously and failed, following the instructions I used an alias to include 192.168.0.0/16, 172.16.0.0/12 and 10.0.0.0/8 this is now working perfectly. Thanks Derelict!

          Would you be able to use this method to solve this, https://forum.pfsense.org/index.php?topic=104090.0, problem?

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