Hi all,
I am using pmfirewall for a firewall, masq, and forwarding. I know it uses
ipchains. Now my question is:
If I setup chose portsentry's kill_route to be /sbin/ipchains, will
pmfirewall implement it? Or do I need to edit the config file to point to
/usr/local/pmfirewall/pmfirewall?
of Linux can be greatly enhanced. Thanks for your comments.
Dan LaBine
Registered Linux User #190712
- Original Message -
From: "Peter Smith" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, March 17, 2001 7:19 PM
Subject: Re: [newbie] PMFirewall and IPchains
---
To all!
As a followup to my previous post to the mandrake group, I did some
snooping around, and found something VERY interesting! Check out this
web-site for something you might find useful - http:/www.securepoint.cc .
They have a complete firewall kit which includes Linux and Windows
Peter,
Sounds like a very well informed opinion formed by someone who has done
their homework and put in the time.
Mark
Peter Smith wrote:
--- Dan LaBine [EMAIL PROTECTED] wrote:
snip!
Why are many Linux-based programs so complicated to
set up?? Here we are,
snip!
I'm no expert but
Mark; Thank-you for not
overstating the obvious! However, as I had mentionedin my initial post, it
was my opinion, not the opinion of all users ofPMFirewall. That having been
repeated now, I'd like to point out thatipchains takes only 3 lines of text
( at least for the networks that
Dan...In some ways we're saying similar things, except as to the point
of "what" Pmfirewall is. And it is definately "not" a firewall, rather
it is merely a means to get the ipchains firewall rule-set configured to
a point to where it's functional. Notice I didn't say ready for prime
time, but
Getting back to PMfirewall leaving some ports open: I've got a
complete mental block when it comes to comprehending the ipchains rules.
I'm at even more of a total loss with the new iptables in 2.4.x kernels.
I have found that I can completely secure my box, all ports, using a
Tom,
That's how I've got my system running and I've found the combination to
a very good one. As for wrapping your brain around the IPchains rules
and such. I can appreciate how you're feeling having been there myself.
It took a little while of looking at the man pages and then reading and
PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Tom Brinkman
Sent: Saturday, 17 March 2001 11:29 PM
To: [EMAIL PROTECTED]
Subject: Re: [newbie] PMFirewall and IPchains
Getting back to PMfirewall leaving some ports open: I've got a
complete mental block when it comes to comprehending
Mark, Tom, and anyone else who can shed a little light on the subject;
Mark, Thanks for your response. And your support. I was about to "Light one
Up" when I received your email. I owe you one. And now for a question that's
probably going to open a "Can Of Worms". I will start by apologising up
Ok, so what are some good ways to convert PMFirewall rules to IPChains?
I'm running IPChains now, witht the rules set up by PMFirewall (added
a rule to close port 1024 which PMFirewall left open). But how do I
make it close (as opposed to filter) ports. ALso, any specific
unnecessary
On Saturday 17 March 2001 05:49 pm, Paul R wrote:
Ok, so what are some good ways to convert PMFirewall rules to IPChains?
PMfirewall is nothing more than a script you run, answer some
straightforward questions, and then it writes ipchains rules according to
the answers you give. .or
--- Dan LaBine [EMAIL PROTECTED] wrote:
snip!
Why are many Linux-based programs so complicated to
set up?? Here we are,
snip!
I'm no expert but I've got a few theories for you.
Theory 1:
Hacking code is fun. Writing a polished interface
isn't so much fun. Since most of what you use under
13 matches
Mail list logo
