pfSense

I am using the AMD64 builds of pfSense 2.0 RC3. I have the same build running on dedicated hardware and in a VM with CARP configured on both to fail-over to the other. The dedicated hardware was installed with a build of AMD64 RC2. When I setup CARP, I updated the dedicated hardware to the build used in the VM and installed the VM using pfSense-2.0-RC3-amd64-20110708-1843.iso. I have updated three times since the install. The current build on both is 2.0-RC3 Built On: Sun Jul 24 04:39:44 EDT 2011.

I have an alias type network(s) that also contains a hostname for a site that does not have a static IP. This works great which is surprising because I have been told by people that have many large pfSense setups that PF doers not deal with that well. However, they are running, 1.x builds and not the latest 1.x, so maybe this limitation was removed long ago.

Anyway, I created an alias type network(s) that contains the alias I described above and another alias and created a NAT rule with this new alias set as a filter for the source IPs. I could access the port defined in this NAT rule from any IP/Network in this new alias and the aliases it contained, but not from the hostname. If I changed the filter for the NAT rule to the alias that contained the hostname, everything worked as expected.