Date: Fri, 12 May 2006 23:27:33 +0200 (CEST) From: "Max Laier" <max@love2party.net> To: freebsd-current@freebsd.org Cc: freebsd-ipfw@freebsd.org Subject: HEADSUP: IP6FW removed Message-ID: <54963.192.168.4.1.1147469253.squirrel@mail.abi01.homeunix.org>
next in thread | raw e-mail | index | archive | help
Hi,
FYI:
mlaier 2006-05-12 20:39:23 UTC
FreeBSD src repository
Modified files:
sbin Makefile
sys/conf files options
sys/modules Makefile
sys/net net_osdep.h
sys/netinet ip_fw2.c
sys/netinet6 ip6_forward.c ip6_input.c ip6_output.c
Removed files:
sbin/ip6fw Makefile ip6fw.8 ip6fw.c sample.sh
sys/modules/ip6fw Makefile
sys/netinet6 ip6_fw.c ip6_fw.h
Log:
Remove ip6fw. Since ipfw has full functional IPv6 support now and - in
contrast to ip6fw - is properly locked, it is time to retire ip6fw.
Known issues:
- ipfw2 is *not* a perfect in-place replacement for ip6fw. Rules might
need slight rewriting to work. You can use the changes in rc.firewall6
as a reference. Now that IPv4 and v6 are integrated one should be able
to write much more elegant rulesets to manage both IPv4 and v6.
- rc.firewall6 will flush rules from rc.firewall. I am still looking for
a clever way how to integrate rc.firewall and rc.firewall6 - patches
welcome!
If there are still missing/broken things in ipfw2's IPv6 support, please
let me know.
--
/"\ Best regards, | mlaier@freebsd.org
\ / Max Laier | ICQ #67774661
X http://pf4freebsd.love2party.net/ | mlaier@EFnet
/ \ ASCII Ribbon Campaign | Against HTML Mail and News
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54963.192.168.4.1.1147469253.squirrel>