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

    FTP Client Proxy Package bindings and config sync

    Scheduled Pinned Locked Moved pfSense Packages
    3 Posts 2 Posters 561 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.
    • C
      ChrisCCC
      last edited by

      I recently discovered the FTP client proxy package in this thread: https://forum.pfsense.org/index.php?topic=89841.0

      I have a couple of questions relating to this, unfortunately the original thread has been locked.

      I make extensive use of interface groups, but the package is only currently capable of binding to individual interfaces. This causes a duplication of effort. Is it possible to get the package to bind to an interface group?

      Additionally, is it likely that there's any way to make the package play ball with XMLRPC Sync? Currently, I have to update config for this on both Firewalls in my HA cluster, which, again, is a duplication of effort.

      Many Thanks.

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

        @ChrisCCC:

        Is it possible to get the package to bind to an interface group?

        No

        @ChrisCCC:

        Additionally, is it likely that there's any way to make the package play ball with XMLRPC Sync? Currently, I have to update config for this on both Firewalls in my HA cluster, which, again, is a duplication of effort.

        Not currently, but there are so few options that the effort would far exceed the benefit.

        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
        • C
          ChrisCCC
          last edited by

          Thanks for the reply Jimp. Sorry it's taken me so long to notice, I thought I'd turned on notifications for the thread, but clearly hadn't.

          Whilst I appreciate what you're saying regarding the number of options, I'm not sure I agree that it's a waste of time. Having a component like this not part of the config sync increases the opportunity for inconsistencies to appear between the two firewalls when a change is made on one, and forgotten about on the other. The bindings are my concern. Whilst your standard pfSense deployment probably only has a handful of interfaces, I currently have around 60 customer interfaces, and counting. I could easily see myself add a binding on one appliance and not notice it's not bound on the other.

          Anyway, I appreciate you no doubt have many better things to do than worry about a package for what is ultimately a defunct protocol. Ultimately, config sync, or no config sync, I appreciate you putting the time into making this package available in the first place.

          Thanks.

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