On Mon, Mar 9, 2015 at 7:08 AM, Espen Johansen wrote:
> All the other options are poor
> workarounds created when pfsense did not support true interface alias.
>
Nothing about any of them are "poor workarounds", there is a use for
every option that's there. The bullet list on this page describes
On Mar 9, 2015, at 8:08 AM, Espen Johansen wrote:
> Use IP alias if you are on 2.0+
> If you need redundancy (2xpfsense) use carp. All the other options are poor
> workarounds created when pfsense did not support true interface alias.
>
I usually use Proxy ARP for 1:1 NAT virtual IP aliases.
Use IP alias if you are on 2.0+
If you need redundancy (2xpfsense) use carp. All the other options are poor
workarounds created when pfsense did not support true interface alias.
Brgds, Espen
8. mars 2015 16:18 skrev "Tim Hogan" :
> I have seen that page and I don't know about "saying it all". I
I have seen that page and I don't know about "saying it all". I still
cannot figure out what the advantages and disadvantages are. All I want
is to be able to do a 1:1 NAT with some public IP addresses. These
addresses do not need to be used by the firewall directly. So in this
case it would
Says it all: https://doc.pfsense.org/index.php/What_are_Virtual_IP_Addresses
Which is better, that depends on what you need it to do.
Tim Hogan schreef op 8-3-2015 om 13:48:
I am setting up my firewall to do 1:1 NAT with a block of public IP
addresses. I have found several posts about setting u
