Based on that very high-level summary: -assuming the /28 isn't a true routed /28, -set pfSense's WAN IP to the first IP in the range (or reserve the first three if using CARP for HA) -set all remaining IPs as CARP-type aliases, and implement inbound NAT a necessary (maybe including 1:1 for the FTP server)
-Adam Ugo Bellavance <[email protected]> wrote: >Hi, > >I was re-reading a book to help my pfsense implementation and in the >section about VIPs, it says that some people rather use CARP VIPs >instead of proxy arp because of some reasons. > >Then, looking at >http://doc.pfsense.org/index.php/What_are_Virtual_IP_Addresses%3F > >I see that IP aliases are new in 2.0. > >Here is my desired setup: > >- Our ISP will provide a /28 (16 IP addresses) and we may need more in >the futre >- We plan to do NAT to expose our public servers (mostly port forward) >- We don't have an FTP server to expose, but it may be necessary in the >future. >- I'm planning on setting the pfSense on a VMWare infrastructure, but we >may eventually need to make a CARP setup in the future > >What should I use for my public IP addresses? > >Thanks, > >Ugo > >_______________________________________________ >List mailing list >[email protected] >http://lists.pfsense.org/mailman/listinfo/list > _______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
