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

    NAT between lans

    Scheduled Pinned Locked Moved NAT
    3 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.
    • H
      hsoares
      last edited by

      Hello.

      Is it possible to NAT between lans in pfsense ? Here's the problem:

      PFS1 LAN 1: 192.168.11.0/24
      PFS1 LAN 2: 172.16.1.1/30

      PFS2 LAN 1: 192.168.16.1/28
      PFS2 LAN 2: 172.16.1.2/30
      PFS2 LAN 3: 172.16.1.5/30

      PFS3 LAN1: 192.168.12.0/24
      PFS3 LAN2: 172.16.1.6/30

      So I have 3 pfsense boxes serving clients on LAN1 subnets with back to back networks between them for routing, I want to NAT requests from PFS1 LAN1 subnet has they reach PFS2 and going to PFS3:

      192.168.11.1 accessing 192.168.12.1 routes trough 172.16.1.2, applies NAT has 182.168.16.2, routes trough 172.16.1.6 and reaches 192.168.12.1 has 192.168.16.2 so the packet has a route back, which can only be on 192.168.16.0/28.

      Is this possible ?

      I have all the routing taking place and connections from 192.168.11.0/24 reach PFS3 with destination 192.168.12.1, but the source IP is not being nated and appears has 192.168.11.1 instead of 192.168.16.2.

      On PFS2 box I have enabled advanced NAT and created a rule like this:

      Interface: LAN2
      Source: 192.168.11.0/24
      Destination: 192.168.12.0/24
      Nat Address: 192.168.16.2/32
      ANY dst and src port

      But the packets are still hitting destination with the original src address .

      Any way of making this work ?

      Thanks.

      1 Reply Last reply Reply Quote 0
      • D
        doktornotor Banned
        last edited by

        Huh… why'd you do any such thing?

        1 Reply Last reply Reply Quote 0
        • H
          hsoares
          last edited by

          Cause the costumer only routes 192.168.16.0/28, politics.

          Nervermind I get it. I was doing the NAT at the wrong interface, working now.

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