Frequently asked questions

Frequently asked Questions: FAQ

We have compiled a small list of frequently asked questions (FAQ) ranging from simple ones to those with full legal implications. In making this FAQ we tried to keep things easily searchable for people who need quick answers.

Frequently asked Questions:

1What does PF mean?
PF Stands for packet filter. It is the original full featured firewall created in OpenBSD. Later it was ported to FreeBSD. Since PF is one of the basics in our firewall, we are including this small reference back to its origin.
2Why virtualize a firewall?
For most companies who start with their own servers in a data center, space is key. Each extra piece of 1U hardware used in the system costs money, electricity and other expenditures. By virtualizing a firewall on multiple network nodes, companies are able save money, increase efficiency, and maximize the use of physical space.
3Why did you create this project?
We (Key4ce) needed a good firewall to put in our Hyper-V servers that has a proper interface and is clusterable. However, after researching for a long time we could not find any firewall that truly fits our needs. So we decided to make one for ourselves. True to the usual fashion of Key4ce, whatever we create with opensource software, we push back to the public for free.
4Can we cluster VirtualPF?
Yes you can. It was our main goal for this firewall. VirtualPF can be fully clustered using CARP. But we had to modify CARP extensively to make the new firewall work on any virtual platform. With this firewall, you can failover or loadbalance the WAN connecton, LAN gateway, etc.
5Is VirtualPF opensource?
Yes, VirtualPF is opensource and falls under Creative Commons "Share-alike license". For more legal information go to the legal section of the VirtualPF website. VirtualPF also uses a "Freeculture" license. For more information about free culture go to this website:
6Can i redistribute VirtualPF?
Yes you can. However, any software using our code or any distribution based on our code has to stay under "Share alike" license: