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

    Setting up OpenVPN for new remote office

    Scheduled Pinned Locked Moved OpenVPN
    25 Posts 5 Posters 2.9k 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.
    • DerelictD
      Derelict LAYER 8 Netgate
      last edited by

      Does the server side have a route back to 192.168.1.1?

      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)

      B 1 Reply Last reply Reply Quote 0
      • B
        BlazeStar @Derelict
        last edited by

        @Derelict on the server-side I can see this entry in my routing table:

        99b6e77f-6974-4b27-9161-e50e7cc70bd2-image.png

        So I would say yes there's a route back.

        Is that what you meant?

        B 1 Reply Last reply Reply Quote 0
        • B
          BlazeStar @BlazeStar
          last edited by

          And both side have this firewall rule in OpenVPN tab

          65efe20c-2bee-44de-86a0-82bbfa74a73f-image.png

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

            That doesn't look like a route back to me. How does the server side firewall know to route traffic back to 192.168.1.1 over the VPN?

            Add 192.168.1.0/24 to the remote networks in the OpenVPN instance on the server side.

            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
            • B
              BlazeStar
              last edited by

              Damn.

              So I made a typo in the IPv4 Remote network(s) on the server-side.

              Now everything works.

              Thank you so much for you help @Derelict

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