* build_mac.sh OSX build script
* Read doc/README.osx for instructions
* Updated fwbuilder.nsi.in, and qmake.inc.in for Windows
* Read doc/README.windows for instructions
parent bridge interface. This allows us to correctly match which
bridge the packet comes through in configurations using wildcard
bridge port interfaces. For example, when br0 and br1 have "vnet+"
bridge port interface, iptables can still correctly match which bridge
the packet went through using "-o br0" or "-o br1" clause. This can be
useful in installations with many bridged interfaces that get created
and destroyed dynamically, e.g. with virtual machines. Note that the
"-i br0" / "-o br0" clause is only added when there is more than one
bridge interface and bridge port name ends with a wild card symbol "+"
for PF and iptables should include not only cluster interfaces, but
also interfaces of all members. This way, we can make compiler
generate configuration
"pass in quick on em0 route-to { ( em0 10.1.1.2 ) } ... "
for a rule of a PF cluster. Here "em0" is an interface of a member,
not the cluster.
dialog where user enters their password. Now user can start in a
non-batch install mode but continue in batch install mode at any time
if all their firewalls authenticate with the same user name and
password.
macro "ESP" that happened during build on OpenSolaris
fixed unit test (ObjectMatcher matches ipv6 only when internal flag is
set accordingly)
set version to 5.0.1
of the GUI was too complicated since user can both act on objects
directly and navigate backwards and forwards to the objects found in
their browsing history. Navigation using browsing history was broken
when quick filter was in use, too. All in all, it feels the value of
"back" and "forward" buttons was relatively low.
New build 3568
