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

    Allow direct routing via openvpn for two lans

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    3 Posts 2 Posters 2.2k 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.
    • D
      datentod
      last edited by

      OpenVPN Pfsense Server (pfsense 2.0-RC3):
      Lan IPs: 192.168.0.0
      OpenVPN: 192.168.11.0
      Tunnel Network: 192.168.11.0/24
      Local Network:192.168.0.0/24

      In advanced section of configuration I added:
      route 192.168.0.0 255.255.255.0;
      route 192.168.2.0 255.255.255.0;
      push "route 192.168.0.0 255.255.255.0"
      push "route 192.168.2.0 255.255.255.0"

      OpenVPN Client (pfsense 2.0-RC3)::
      Lan IPS: 192.168.2.0
      Tunnel Network:192.168.11.0/24
      Remote Network: 192.168.0.0/24
      In advanced section of configuration I added:
      route 192.168.0.0 255.255.255.0;
      route 192.168.2.0 255.255.255.0;

      How can I allow direct communication between 192.168.0.0 & 192.168.2.0 networks through openvpn?
      OpenVPN is working fine though, I can ping/telnet between pfsense client/server without issues.

      1 Reply Last reply Reply Quote 0
      • D
        datentod
        last edited by

        Anyone :(

        I need to link these LANs & I am 300km away… Dont want to drive there:)

        1 Reply Last reply Reply Quote 0
        • N
          Nachtfalke
          last edited by

          Hi,

          take a look at this sticky post in the OpenVPN thread:
          http://forum.pfsense.org/index.php/topic,12888.0.html

          I didn't set this up before but as far as I know you need to use the "iroute" command in "Client Specific Override" for the networks behind the OpenVPN CLIENT.

          –-- EDIT ----
          the above wasn't correct at all. I corrected it a little bit. But please take a look at this thread. I think it explains it in detail.

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