On Sat, Sep 15, 2007 at 01:10:04PM -0700, Tom Eastep wrote: > > iptables is iptables; ip6tables is ip6tables. The rulesets created using > these two utilities are totally independent. So there is no reason to > have a single product that produces both configuration. > I was not aware of the separation.
> Furthermore, the differences between the two protocols and the > differences in capabilities of iptables and ip6tables means that a > single compiler would be riddled with separate IPv4/IPv6 logic (as would > the documentation). > > Nevertheless, I've experimented over the last couple of weeks with > hacking up the Shorewall-perl compiler so that it could produce both > configurations in a single compilation. From these experiments, I've > determined that I really don't want to try to do that. > Makes sense. > So my plan at the moment is to add two new packages: Shorewall6 and > Shorewall6-lite. Both will have their own command-line tool (shorewall6 > and shorewall6-lite). > > It is unlikely that Shorewall6 will ever support traffic shaping or > multi-ISP. I'm reluctant to repeat either of those mistakes. > I see. Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com
signature.asc
Description: Digital signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ Shorewall-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-devel
