<![CDATA[Policy based routing with a custom IPv4 list: Create WAN_EGRESS alias]]>In creating my WAN_EGRESS alias, generating the list with Firewall > pfBlockerNG > IP > IPv4, I included ifconfig.co for testing, the pfBlockerNG > Logs shows,
Screenshot (3).png

but when I go to ifconfig.co I get this,
Screenshot (5).png

and in my firewall rule, I wanted it to be in the Unites States
Screenshot (4).png

when I check ntopng, I get this IP for ifconfig.co,
Screenshot (2).png

now I see why its hitting the last firewall rule because this IP is not in the alias list, in short, I'm using AirVPN and configured three gateway clients following "pfSense multi VPN WAN" successfully.

My ports for this rules are,
Screenshot (6).png

Can anyone tell me what I'm missing or what to check to correct this?

]]>https://forum.netgate.com/topic/185767/policy-based-routing-with-a-custom-ipv4-list-create-wan_egress-aliasRSS for NodeSun, 14 Jun 2026 10:13:38 GMTFri, 26 Jan 2024 04:15:24 GMT60<![CDATA[Reply to Policy based routing with a custom IPv4 list: Create WAN_EGRESS alias on Fri, 26 Jan 2024 05:11:44 GMT]]>Well, I did a reboot and it appears to be working when I added iplocation.net IP's to the list and these IP's are exiting through the AirVPN USA WAN gateway. But, I'm not getting any success with updating the ifconfig.co IP's even after doing a full update via pfBlockerNG.

Since I'm getting good IP's with iplocation.net, the firewall test working fine.

]]>https://forum.netgate.com/post/1149673https://forum.netgate.com/post/1149673Fri, 26 Jan 2024 05:11:44 GMT