<?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[Firewall ACLs don´t work]]></title><description><![CDATA[<p dir="auto">Hello Guys,</p>
<p dir="auto">i´ve got a problem. I have installed a pfSense on a esxi as a virtual machine. Internet connection, vpn and port forwarding works fine.<br />
I get the following message in the event log:</p>
<p dir="auto"><img src="https://mail.google.com/mail/u/0/?ui=2&amp;ik=167626110a&amp;view=att&amp;th=1417a93271106b65&amp;attid=0.1&amp;disp=inline&amp;realattid=f_hmaxijul0&amp;safe=1&amp;zw" alt="" class=" img-fluid img-markdown" /></p>
<p dir="auto">The source ip is my domain controller (192.168.200.2) and the destination is a client pc on a different subnet (192.168.1.53). These logs are produced by connecting this client to a exchange account. (exchange 2007, hosted by the domain controller). Routing working fine between these subnets, i can ping the DC, working over RDP on the DC and i can open network drives over smb from the client for example. Only connecting to exchange do not work.</p>
<p dir="auto">I´ve got the following ACLs on Firewall Rules configured:</p>
<p dir="auto"><img src="http://i.imagebanana.com/img/6v1ys4tu/Unbenannt.PNG" alt="" class=" img-fluid img-markdown" /></p>
<p dir="auto">But that doesn´t work. With creating a easy rule over the system log (see in first picture) it doesn´t work too.</p>
<p dir="auto">I also checked personal firewalls, that can not be the issue.</p>
<p dir="auto">Have you guys any idea ?</p>
<p dir="auto">thanks a lot</p>
<p dir="auto">cheers</p>
]]></description><link>https://forum.netgate.com/topic/61225/firewall-acls-don-t-work</link><generator>RSS for Node</generator><lastBuildDate>Sat, 05 Sep 2026 09:03:26 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/61225.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 02 Oct 2013 19:26:59 GMT</pubDate><ttl>60</ttl></channel></rss>