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

    1:1 NAT / Port forward not working since 23.01

    Scheduled Pinned Locked Moved NAT
    2 Posts 2 Posters 323 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.
    • R
      Robovic
      last edited by

      I'm experiencing an issue with our network setup using the Netgate 2100 v23.01 and 23.05. We have been using this setup for a year with various Netgates, but now I can't get it to work with the new version of pfSense. The LAN network has IPs in the range of 192.168.1.0/24, and I want to access it from a VPN using a different subnet to avoid IP conflicts.

      To achieve this, I have set up a routing rule: 10.0.0.0/24 --> LAN_GW, and then a 1:1 NAT on the LAN interface with an external IP of 10.0.0.0 and an internal IP of 192.168.1.0/24. This configuration was working fine with version 22.05 of pfSense. However, with the packet capture feature, I can see that the traffic is trying to reach 10.0.0.0/24 on the LAN instead of 192.168.1.0/24 (ARP, Request who-has 10.0.0.101 tell 192.168.1.1, length 28).

      The same issue occurs when I ping from the VPN or from the Netgate itself. It appears that the traffic originating from the Netgate is no longer being translated.

      Here are the configurations that were working on pfSense 22.05:

      System → Routing → Gateways: Added a gateway with IP 192.168.1.1 on the LAN interface.
      System → Routing → Static Routes: Added a route with network 10.0.0.0/24 and gateway 192.168.1.1.
      Firewall → NAT → 1:1: Added a mapping in the LAN interface with external IP 10.0.0.0 and internal IP LAN net.
      System → Advanced → Firewall & NAT :

      • NAT Reflection : Pure NAT
      • NAT Reflection for 1:1 NAT : Checked
      • Enable automatic outbound NAT for Reflection : Checked
      N 1 Reply Last reply Reply Quote 1
      • N
        necross @Robovic
        last edited by

        @Robovic I am having the same issue

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