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

    Haproxy-devel external address option (pfsense 2.2)

    Scheduled Pinned Locked Moved pfSense Packages
    3 Posts 2 Posters 1.0k 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.
    • N
      nikolaii
      last edited by

      Hello,

      I'm running haproxy-devel (1.5.9 pkg v 0.15) under pfsense 2.2 as a http (80) frontend for 2 http backend servers.

      I try to understand the difference between the following options:

      • listening to the WAN interface and adding a firewall rule to TCP/80 / Wan Interface
      • listening to the ANY interfaces and adding a firewall rule to TCP/80 / Wan interface
      • listening to the localhost interface and adding a NAT rule plus a firewall rule to 127.0.0.1 - TCP/80

      I think the first option is better (no NAT rule to add). But is there any recommendation on this?

      Thanks.
      Nicolas

      Nicolas

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

        First option is best. It's the most specific, doesn't bind where it doesn't need to, and doesn't involve NAT.

        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
        • N
          nikolaii
          last edited by

          Hi, thank you for your answer.

          Nicolas

          Nicolas

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