onkelbeh/fwbuilder
1
0
Fork 0
mirror of https://github.com/fwbuilder/fwbuilder synced 2026-03-25 12:47:44 +01:00
Code Issues Releases Wiki Activity

changelog record

Browse Source
This commit is contained in:
Vadim Kurland 2008-12-16 05:30:56 +00:00
parent 742f0b6791
commit 636840f051
2 changed files with 17 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
build_num
View File

@ -1 +1 @@
#define BUILD_NUM 692
#define BUILD_NUM 694

17
doc/ChangeLog
View File

@ -2,7 +2,22 @@
* ipt.cpp, ipfw.cpp, pf.cpp, iosacl.cpp: changes for FR #2431602:
support for rulesets configured as "dual address family", that is,
rulesets that should be compiled for both ipv4 and ipv6.
rulesets that should be compiled for both ipv4 and ipv6. Compiler
processes rulesets like this twice, first for ipv4 and then for
ipv6. On each pass it will only use address and service objects
that match address family it uses for the ruleset. This also
applies to "compile-time" DNSName objects, that is, it will use
getaddrinfo() to get AF_INET address on ipv4 pass and AF_INET6 on
ipv6 pass.
Rules with "any" in rule elements in the "dual address family"
ruleset yield iptables commands for both families. This was the
reason I made setting exclusive in the first place. This means
that users who do not want fwbuilder to generate ipv6 policy for
them and want all ipv6 accepted, should not use "dual address
family" setting. If the do, the bottom catch-all rule will install
ip6tables command to block all ipv6 automatically even if all
rules have absolutely no ipv6 objects at all.
* RuleSetDialog.cpp (RuleSetDialog::applyChanges): implemented
feature request #2431602: "Feature request: Unified