<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[HAProxy Custom ACL with Firewall Alias now working]]></title><description><![CDATA[<p dir="auto">I am trying to use a rule to whitelist ips for a specific backend in my frontend.</p>
<p dir="auto">Basically use the X backend, if the host matches xxx.com and ip is whitelisted in a pfsense defined ip alias list.</p>
<p dir="auto">The problem is I am using the Cloudflare proxy and need to inspect the CF-Connecting-IP.</p>
<p dir="auto">And to do that I am using Custom ACL like this</p>
<pre><code>req.hdr(CF-Connecting-IP) -f /var/etc/haproxy/ipalias_Allowed_IPs.lst
</code></pre>
<p dir="auto">The Alias is defined in the firewall named Allowed_IPs.</p>
<p dir="auto">But this list does not get created unless I use something standard like "Source IP matches IP or IP Alias". Is there another way to refer to the created Aliases so that they are created properly?</p>
<p dir="auto">The workaround for this is to create a dummy acl with "Source IP matches IP or IP Alias" that does nothing but it is not a good solution.</p>
<p dir="auto">Edit: One more thing, I noticed is, when the alias list is updated, this does not get reflected to the HAProxy lists in /var/etc/haproxy/ until HAProxy is restarted.</p>
]]></description><link>https://forum.netgate.com/topic/197945/haproxy-custom-acl-with-firewall-alias-now-working</link><generator>RSS for Node</generator><lastBuildDate>Tue, 10 Mar 2026 09:44:43 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/197945.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 24 Jun 2025 16:31:02 GMT</pubDate><ttl>60</ttl></channel></rss>