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

    NEED Help Site-Site VPN

    Scheduled Pinned Locked Moved OpenVPN
    5 Posts 3 Posters 1.5k 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.
    • N
      Nazilus
      last edited by

      Hi everyone, my name is Naz
      I been studying this PFsense for a while now and i Stoned with this coming Issue
      my set up was

      A Site: VPN: 10.10.1.1, Internal IP: 192.168.5.1/24
      B Site: VPN: 10.10.1.2, Internal IP: 192.168.7.1/24

      It been set up using Sharekey simple Site to Site config, The A site Acting as a VPN Server, i now can Ping and access from every Computer from the A site to B Site, But i cant get any ping from B Site to A Site. i dont have any els setting like Route Push or IRoute.

      is anything els i should be mention here? Please be advice…

      Thank you for your time.. (Sry for my Bad English.)

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

        Every computer from site B all can access to PFsense box at 192.168.5.1 also… but to other Client computer like 192.168.5.10... i Wont be able to Ping or access...

        1 Reply Last reply Reply Quote 0
        • P
          phil.davis
          last edited by

          Make sure:

          1. Local and Remote Network are specified on your server settings - then both ends should have a route to the other LAN - use Diagnostics->Routes to see what the routing table ends up with.
          2. Add a firewall rule on OpenVPN at both ends - easiest to allow all traffic in the rule for testing, then you can make the rule tighter (e.g. allow all IPv4 from LAN Subnet to the remote LAN subnet).
          3. The clients at both ends are using the pfSense router as their default gateway (if pfSense is not the only router on your LAN, then you might have to do some extra tweaking so that the clients know how to route back to subnets acroos the VPN).

          As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
          If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

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

            @phil.davis:

            Make sure:

            1. Local and Remote Network are specified on your server settings - then both ends should have a route to the other LAN - use Diagnostics->Routes to see what the routing table ends up with.
            2. Add a firewall rule on OpenVPN at both ends - easiest to allow all traffic in the rule for testing, then you can make the rule tighter (e.g. allow all IPv4 from LAN Subnet to the remote LAN subnet).
            3. The clients at both ends are using the pfSense router as their default gateway (if pfSense is not the only router on your LAN, then you might have to do some extra tweaking so that the clients know how to route back to subnets acroos the VPN).

            Both A and B Site got the IP of each
            Firewall rule all open on VPN tap
            Both Client use PFsensebox at GW

            T T Still the same

            1 Reply Last reply Reply Quote 0
            • M
              marvosa
              last edited by

              Need more specifics to troubleshoot.

              Which guide did you follow to set up the tunnel?
              Post your Server openvpn config
              Post your client openvpn config (site b)
              And I have to ask… but is there a PFsense box on both ends?
              Post screen shots of firewall rules on both ends on the openvpn tab

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