Date: Fri, 11 Feb 2005 01:30:00 +0100 From: Max Laier <max@love2party.net> To: freebsd-pf@freebsd.org Subject: Re: IPFilter TO PF Message-ID: <200502110130.07341.max@love2party.net> In-Reply-To: <20050209054426.GE20131@ns2.wananchi.com> References: <20050209054426.GE20131@ns2.wananchi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Wednesday 09 February 2005 06:44, Odhiambo Washington wrote: > Hello users, > > I am a newbie to PF, but I have been using IPFilter for some > time. Please bear with my first silly question. > > For reasons that I would like to enter the era of bandwidth control, > and this is not available in IPFilter. I have a few boxes running > almost with similar rules and was wondering if there could be a tool > to convert ipf/ipnat rules into PF format/syntax or I just have to > sit down and start the conversion manually. > > Thanks for any insights. I am not aware of a tool like this. I also encourage to do manual conversion or (better even) start from scratch. The OpenBSD PF-FAQ is a good tutorial to start from. It makes a better ruleset if you write it with the PF "philosophy" in mind. I understand however, that it might be interesting to take over long lists of individual block/pass rules. This type of rule, however, is a prime example of how PF differs from the 3.x IPFilter since PF comes with tables you might want to rewrite your rules there. It is hard to do such things in an automated tool. Please let us know if you find something helpful on the net - I didn't yet. -- /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBCC/yPXyyEoT62BG0RAt5kAJ4k1aJGP3ncDq15ytxkG6EQiLU9xACfWlLC gLSIPhL0R1fCLBrBoBXXy8Y= =csD/ -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200502110130.07341.max>
