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

    Peplink / NAT Pfsense

    Scheduled Pinned Locked Moved NAT
    3 Posts 3 Posters 1.3k 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.
    • P
      Phoenix85
      last edited by

      Hi All ,

      I am hoping someone can assist me with setting up double nat between a Peplink dual wan router and our Pfsense Box

      Peplink has 2 wan links from 2 diffrent ISP with 5 Static IP's on each

      Peplink Lan IP 172.16.1.1
      Single lan cable from Peplink lan port to Wan Interface on PFsense
      Wan Interface has 172.16.1.2 assigned as IP
      Lan Interface has 10.0.1.0/20 going to our Netgear switch.

      I have setup the peplink to forward all ports to the 172.16.1.2 Interface on the Pfsense
      I can open the Webinteface off the peplink from external network's .

      Now trying to fwd ports on the pfsense to rdp to server on local lan that has a 10.0.1.xxx address does not work

      I understand that double NAT has some extra work to do and I am not to clued up on that so your help would be appreciated
      Any info needed can be supplied

      Regards

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

        If the Peplink port forwards are working then the pfSense WAN will be receiving packets with destination pfSense WAN IP 172.16.1.2 - you can check that with packet capture.
        Then it should just be a port forward from pfSense WAN IP 172.16.1.2 to the inside server 10.0.1.xxx - I don't think there are any special tricks with that.
        But make sure not to have "Block private networks" checked on the WAN interface.

        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
        • A
          ali.amer
          last edited by

          @phil.davis:

          If the Peplink port forwards are working then the pfSense WAN will be receiving packets with destination pfSense WAN IP 172.16.1.2 - you can check that with packet capture.
          Then it should just be a port forward from pfSense WAN IP 172.16.1.2 to the inside server 10.0.1.xxx - I don't think there are any special tricks with that.
          But make sure not to have "Block private networks" checked on the WAN interface.

          I am going to implement the same idea with Pfsense and Peplink 710.

          I will let you know what the result is.

          If already have the solution, please post it.

          Thanks.

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