First: PMFirewall doesn't "run" There is no daemon for it. It simply sets the
ipchains rules as a script.
In terminal, type (su to root) ipchains -L
to see a list of the current rules set by pmfirewall. These will change over time as
the firewall DENIES things. But will NOT be maintain after a disconnet, or shutdown.
The standard rules will be re-established upon successful connection, and be added
dynamically from there.
Check the man page for ipchains for more information on how to see/set the rules.
--Greg
> On Mon, 24 Jul 2000, you wrote:
> > Hi again Greg,
> >
> > I added the line to start the firewall in the ip-up file and it's starting
> > fine now. I don't know why it wouldn't start with the line in
> > ip-up.local. the only thing I could come up with was that it wasn't
> > getting read by the shell script. maybe it wasn't being referenced
> > correctly...don't know for sure.
> >
> > thanks again for the help.
> >
> > --
> > Mark
>
> Heck I didn't even think of all this before, but in reading
> this thread I tried as 'ps ax' while connected and pmfirewall
> didn't show up.
> So I added the
> '/usr/local/pmfirewall/pmfirewall start' to ip-up (same as you
> there was already a sinilar statement in ip-up.local) and
> reconnected, ran 'ps ax' and it still doesn't show.
>
> What are you using to determine if pmfirewall's runnin Mark?
> --
> ~~ Tom Brinkman [EMAIL PROTECTED]
*********************************************
Want free email? Sign up at http://www.freeze.com !
