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

    [SOLVED] Routing from LAN to OpenVPN

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    4 Posts 2 Posters 1.4k 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.
    • B
      BlackJack01090
      last edited by

      Hello,

      I set up a OpenVPN Server and gives the client fixed IPs. On Firewall - LAN I have a rule that allows all Traffic to the VPN IPs. From VPN only Ping is allowed to one Client to test the connection. I can ping from VPN to this one client, but no client can ping the vpn client. From the Firewall it is possible to ping both sides. The local Network in the OpenVPN Server is the DMZ Range. Could this be the problem?

      Greetings

      BJ01090

      1 Reply Last reply Reply Quote 0
      • Cry HavokC
        Cry Havok
        last edited by

        Is the OpenVPN server also the default gateway for the network? If not did you push a static route to the LAN router?

        1 Reply Last reply Reply Quote 0
        • B
          BlackJack01090
          last edited by

          The Firewall is the default Gateway for the LAN and also the OpenVPN Server. The Firewall run on the latest pfSense 2. The lan has 192.168.1.0/24, The Firewall 192.168.1.10. The VPN Server has as net 192.168.250.0/24. Local Net is the DMZ with 172.31.31.0/24. In Firewall under LAN is a rule: Source LAN net, Destination 192.168.250.0/24, Protocol any.

          Under Routing I can only choose the Router as Gateway in a DropDown List, not the Firewall.

          1 Reply Last reply Reply Quote 0
          • B
            BlackJack01090
            last edited by

            Found the Problem :) In the OpenVPN Servers ettings under Advanced I added push "route 192.168.1.0 255.255.255.0". Now teh VPN Client can route correctly.

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