So after using Shorewall for years, I've been taking my first foray into
real router devices by playing with a MikroTik Routerboard 750. Nice
little unit, 400MHz Mips CPU, 32MB RAM, 64MB flash.
I'm trying to wrap my head around writing actual router/firewall rules
now, and it's quite interesti
that's an excellent idea if it's not already in, I throw in my hat for a
feature request.
Joshua J. Kugler wrote:
> So after using Shorewall for years, I've been taking my first foray into
> real router devices by playing with a MikroTik Routerboard 750. Nice
> little unit, 400MHz Mips CPU, 32
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joshua J. Kugler wrote:
>
> Which led me to wonder: Is the shorewall compiler output "pluggable," or
> at least self-contained as to be easily replaceable? I was thinking
> along the lines of the rules and config being parsed into a
> firewall-agn
On Monday 19 October 2009, Tom Eastep said something like:
> I have on my long-term list of goals to re-implement Shorewall along
> the lines that you suggest, but that won't happen until after I
> retire (currently planned for 2012). I'm also not convinced that the
> goal is reachable since the ex
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joshua J. Kugler wrote:
> Not sure exactly what you mean "shorewall externals." Shell? Perl?
> Network interfaces?
The "externals" of a software product are the aspects of the end-user
deals with.
a) The options in /etc/shorewall/interfaces are hi
