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

    FTP Traffic ignores Failover pool order

    Scheduled Pinned Locked Moved 1.2.3-PRERELEASE-TESTING snapshots - RETIRED
    5 Posts 3 Posters 2.9k 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.
    • A
      althornin
      last edited by

      Existing Setup:
      two WAN links - WAN is a T1, WAN2 is a 10Mb fiber connection.

      I want all traffic to prefer to use the WAN2 connection unless it is down.  This works perfectly for all HTTP/ HTTPS downloads, etc.
      However, for FTP downloads, the WAN connection is being used, which is much slower.
      The current rules on the LAN interface are:
      *  LAN net  *  WANsubnet  *  WANIP
      *  LAN net  *  WAN2subnet  *  WAN2IP
      *  LAN net  *  *                  *  WAN2FailToWAN

      Is there something obvious I am missing here?  Is there some hidden FTP helper option that is breaking stuff?

      1 Reply Last reply Reply Quote 0
      • D
        danswartz
        last edited by

        check and make sure all of the ftp userland helpers are disable.

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

          And where do I do that?

          Just an added note:  I'm on the latest snapshot:
          pfSense-1.2.3-2g-20091105-2039-nanobsd-upgrade.img
          is the last update I applied.

          1 Reply Last reply Reply Quote 0
          • dotdashD
            dotdash
            last edited by

            You disable the ftp helper on the interface. You'd want to check the LAN interface. If the ftp helper is active, all ftp traffic will use the helper and go out the WAN.

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

              Yeah, I just found it in the LAN interface, and yep, that was the problem.
              Thanks guys!

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