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

    [NAT] reply-to on WAN rules not working after Update to 21.02_1

    Scheduled Pinned Locked Moved Routing and Multi WAN
    natreply-to error
    4 Posts 3 Posters 593 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.
    • S
      snits35m
      last edited by

      Hello,
      yesterday I updated pfSense to the new version "21.02_1", since then it seems as if "reply-to on WAN rules" no longer works, we have 2 WANs, most NAT requests come from the non-default WAN since the update the server's responses are no longer forwarded to the correct WAN.

      As a workaround I have currently changed the standard WAN, but this is NOT a definitive solution!

      Is the problem already known?

      S 1 Reply Last reply Reply Quote 1
      • S
        snits35m @snits35m
        last edited by

        @jimp: Since nothing was changed in the configuration and it worked perfectly before the update, I would guess the problem is related to the update ?!

        Nobody else has this problem???

        1 Reply Last reply Reply Quote 0
        • jimpJ
          jimp Rebel Alliance Developer Netgate
          last edited by

          https://redmine.pfsense.org/issues/11436#note-42

          Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

          Need help fast? Netgate Global Support!

          Do not Chat/PM for help!

          G 1 Reply Last reply Reply Quote 2
          • G
            ggoldfingerd @jimp
            last edited by

            @jimp Thanks for posting this. This is exactly my problem with my pfSense Plus. I have two WANs with my default one being GCNAT. My secondary WAN has a static IP which is used for inbound connections which need entry to my network.

            I didn't have any problems with 2.4.5p1. I can only make it work now if I change my default gateway to my static IP WAN. This connection is very slow compared to my other WAN. Hopefully they come up with a workaround soon.

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