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

    OpenVPN on PFSense behind NAT tunel communication problem

    Scheduled Pinned Locked Moved OpenVPN
    4 Posts 2 Posters 745 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.
    • E
      eragons
      last edited by

      Hi,
      I have two networks

      First is 10.20.11.0/24, there is Unifi Security gateway.
      Installed PFsense (10.20.11.41) as virtual machine, behind NAT, firewall is disabled.
      On Unifi Security gateway there is static route that routes traffic to 10.20.12.0/24 over 10.20.11.41
      There is OpenVPN server Peer to Peer.
      Tunnel network is 10.30.10.0/24

      Second, 10.20.12.0/24, there is VMWare Edge Gateway, some virtual machines...
      Installed PFsense (10.20.12.20) as virtual machine, behind NAT, firewall is disabled.
      On Edge Gateway, static route that routes traffic to 10.20.11.0/24 over 10.20.12.20 (PFSense)
      There is OpenVPN client configured and active.

      I need machines in both networks to communicate to each other.
      I can ping every device in 10.20.11.0/24 from side with Edge Gateway.
      But from USG side, I can ping only Edge Gateway and PFSense, but can't ping other devices.

      Can you help me please?

      1 Reply Last reply Reply Quote 0
      • johnpozJ
        johnpoz LAYER 8 Global Moderator
        last edited by johnpoz

        Simple drawing showing your network makes it 1000x easier to assess..

        Without drawing this out, It seems you prob have asymmetrical issues. This 10.20.11 is your transit network between your usg and pfsense. And you have hosts on this network? Without host routing, and or natting, and port forwarding you will have asymmetrical routing problems.

        behind NAT, firewall is disabled.

        How exactly did you accomplish that on pfsense?

        firewall.png

        Even with firewall rules that allow all traffic, you can still run into out of state traffic being blocked.

        If you want to remove asymmetrical issues and allow networks to talk to each other without problems. Routers, be it they firewall or not need to be connected via transit networks (a network with no hosts/clients on it)..

        Talking to and from clients that are on a transit network (network between routers) is always going to be problematic because of asymmetrical traffic flow. Unless these hosts on the transit have routes on them saying which router to talk to to get to what networks.

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 24.11 | Lab VMs 2.8, 24.11

        1 Reply Last reply Reply Quote 0
        • E
          eragons
          last edited by eragons

          Sorry, here is my diagram.

          Firewall is "disabled" by adding allow rule everything to everyhing on both PFSense.
          Disable all packet filtering is unticked.

          In digram: VM1 can't access VM2 on other side but VM2 can access VM1.
          Tracert from VM1 to VM2 ends on 10.30.10.2, which is OpenVPN client address

          Untitled Diagram.jpg

          1 Reply Last reply Reply Quote 0
          • johnpozJ
            johnpoz LAYER 8 Global Moderator
            last edited by johnpoz

            That is asymmetrical mess

            assmess.png

            If you want to use pfsense as downstream routers from your USGs then connect them with transit networks..

            2 transits.png

            You could also just solve this with just a transit between your 2 USGs.. 1 pfsense between the 2 of them with leg connected to each USG which would be the transit network connected to each USG.

            You could also use port forwarding and source natting to solve the problem on every host in your different 20.11 and 20.12 networks. Or host routing so your flow would look like this.

            nat-port.png

            An intelligent man is sometimes forced to be drunk to spend time with his fools
            If you get confused: Listen to the Music Play
            Please don't Chat/PM me for help, unless mod related
            SG-4860 24.11 | Lab VMs 2.8, 24.11

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