On May 4, 2004 02:42 am, Mohamed Kerbachi wrote: > Hello, > > /sbin/chkconfig --level 2345 ipchains off > > RedHat 6.1 !!! you should upgrade your server !!! > > -----Message d'origine----- > De : Edward [mailto:edward@xxxxxxxxxxxxxxxxxxxx] > Envoyé : mardi 4 mai 2004 11:11 > À : General Red Hat Linux discussion list > Objet : Re: disable firewall > > pop wrote: > > how to disable firewall from prompt. > > red hat 6.1 > > Flush all chains (I'm assuming 6.1 used ipchains). > > 'man ipchains' > > Regards, > Ed. > > > > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list Hi, using chkconfig does not stop the firewall (or any service) but changes it's run level status which will go into effect next time that runlevel is entered. So the question is what is it that needs to be done? Stop the firewall or stop and disable the firewall. On a related note (I found interesting anyway), a while ago I checked some iptables rules for someone, and made some changes, loaded them up on my machine, got the expected errors (non valid interface etc) and then stopped the firewall using 'service iptables stop'. Shortly afterwards I experienced connectivity problems. The problem was that the rules were partial and no default policies were in place, so even though I stopped the iptables service (the user part), netfilter (the kernel part) lived on. I needed to set default rules and start/stop the fw in order to clear the test rules. It turns out "stop" means flush the existing rules and set the default policies (normally accept for all chains) -- Pete Nesbitt, rhce -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
