cvs commit: src/sbin Makefile src/sbin/ip6fw Makefile ip6fw.8
ip6fw.c sample.sh src/sys/conf files options src/sys/modules
Makefile src/sys/modules/ip6fw Makefile src/sys/net
net_osdep.h src/sys/netinet ip_fw2.c src/sys/netinet6
ip6_forward.c ip6_fw.c ...
cokane at cokane.org
Sun May 28 00:03:52 PDT 2006
On Fri, May 26, 2006 at 12:33:23PM -0700, Yu-Shun Wang wrote, and it was proclaimed:
> Max Laier wrote:
> >On Fri, May 12, 2006 11:38 pm, Bjoern A. Zeeb wrote:
> >>On Fri, 12 May 2006, Max Laier wrote:
> >>> Log:
> >>> Remove ip6fw. Since ipfw has full functional IPv6 support now and - in
> >>> contrast to ip6fw - is properly lockes, it is time to retire ip6fw.
> >>could you add an entry to UPDATING because of incompatible syntax etc.
> >>so people will be able to find out before updating that their ip6fw
> >>rc.firewall6 scripts no longer work...
> >Will post to UPDATING, bump __FreeBSD_version and update ObsoleteFiles in
> >a bit.
> I am probably missing something here. But both rc.firewall
> and rc.firewall6 flush all rules before adding their own.
> The result on my system is that v4 rules were wiped out.
> Any ways to resolve this? (I commented out the flush line
> in rc.firewall6 for now. But that's not good if you are
> v6 only.)
Now that the firewall code is combined, shouldn't the only
necessary script be rc.firewall for both inet6 and inet4?
More information about the cvs-src