Re: Cannot Disable iptables on startup
From: Ivan Marsh (annoyed_at_you.now)
Date: 04/25/05
- Next message: Iraq4all: "Red Hat AS 3 & Load Balancing"
- Previous message: Spamless: "Re: RealPlayer 10 and mp3 ... no volume"
- In reply to: Paul D: "Re: Cannot Disable iptables on startup"
- Next in thread: Paul D: "Re: Cannot Disable iptables on startup"
- Reply: Paul D: "Re: Cannot Disable iptables on startup"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 25 Apr 2005 12:38:41 -0500
On Mon, 25 Apr 2005 13:44:02 +0100, Paul D wrote:
> I'm sorry, I may not have explained myself.
>
> Despite chkconfig --list | grep ip giving the results you describe
> below, service iptables status still gives the following:
>
> [root@myserver cups]# service iptables status #Table: filter
> Chain INPUT (policy ACCEPT)
> target prot opt source destination
>
> Chain FORWARD (policy ACCEPT)
> target prot opt source destination
>
> Chain OUTPUT (policy ACCEPT)
> target prot opt source destination
>
>
> Rather than:
>
> [root@myserver cups]# service iptables status Firewall is stopped.
iptables is part of the kernel... I think you're always going to see a
default accept policy even if the service isn't running.
-- Life is short, but wide. -KV
- Next message: Iraq4all: "Red Hat AS 3 & Load Balancing"
- Previous message: Spamless: "Re: RealPlayer 10 and mp3 ... no volume"
- In reply to: Paul D: "Re: Cannot Disable iptables on startup"
- Next in thread: Paul D: "Re: Cannot Disable iptables on startup"
- Reply: Paul D: "Re: Cannot Disable iptables on startup"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
