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

    NAT not working in Multi-WAN environment

    Scheduled Pinned Locked Moved 2.4 Development Snapshots
    17 Posts 8 Posters 3.2k 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.
    • M
      maverick_slo
      last edited by

      Oh uh…
      Is this my problem too?
      https://forum.pfsense.org/index.php?topic=123370.0

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

        Most likely.

        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!

        1 Reply Last reply Reply Quote 0
        • Raul RamosR
          Raul Ramos
          last edited by

          I'm waiting for this fix to…so i will test this problem.

          pfSense:
          ASRock -> Wolfdale1333-D667 (2GB TeamElite Ram)
          Marvell 88SA8040 Sata to CF(Sandisk 4GB) Controller
          NIC's: RTL8100E (Internal ) and Intel® PRO/1000 PT Dual (Intel 82571GB)

          1 Reply Last reply Reply Quote 0
          • M
            maverick_slo
            last edited by

            One more thing…
            I really dont know it its connected but still...

            See attached image.
            I start to download some file hosted behind pfsense with 2 wans (download is happening only on DHCP).
            It starts sloppy and interrupting as hell, slow dl speeds lots of retransmissions in packet capture.
            But when I hit disconnect on pppoe, it starts to fly as expected...

            Can this 2 things somehow be connected?

            wans.png
            wans.png_thumb

            1 Reply Last reply Reply Quote 0
            • M
              maverick_slo
              last edited by

              Forgot to mention that pppoe has ipv6 and client that downloads has ipv6 too. Webserver has also ipv6.
              Maybe this is client problem and tries to download with ipv4 and ipv6 together?

              1 Reply Last reply Reply Quote 0
              • M
                maverick_slo
                last edited by

                @maverick_slo:

                Forgot to mention that pppoe has ipv6 and client that downloads has ipv6 too. Webserver has also ipv6.
                Maybe this is client problem and tries to download with ipv4 and ipv6 together?

                This is confirmed.
                When I disable pppoe ipv4 gateway transfers are OK.
                This also happens on 2.3.3

                So 2 IPv4 gateways are causing major problems, at least for me.

                1 Reply Last reply Reply Quote 0
                • A
                  athurdent
                  last edited by

                  Seems to be resolved now: https://redmine.pfsense.org/issues/6986
                  Don't know if the latest snapshots already have the fix, though.

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

                    The latest snapshots have the fix (for almost a day now)

                    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!

                    1 Reply Last reply Reply Quote 0
                    • T
                      techy82
                      last edited by

                      works great now :-)

                      1 Reply Last reply Reply Quote 0
                      • M
                        megapearl
                        last edited by

                        Just upgraded from 2.3.3 to 2.4.0, bug is fixed, Problem solved! :D

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