I stopped it, uninstalled it, and flushed all the ipchains rules. It /should/
be a clean setup again like I had before. But still it acts like I said
before: only icmp gets forwarded through it and data in general is extremely
slow.

<EOL>
Tib


On Wed, 3 Jan 2001, Mike MacCana wrote:

> You can stop pmfirewall when its installed by running
> 
> service pmfirewall stop
> 
> Which clears the rules and set them to deny. Did you read the 
> documentation fully? Its a neat utility, so don't give up on it yet.
> 
> If you must use ipchains directly, then...
> 
>      ipchains -F input
>      ipchains -F output
>      ipchains -F forward 
> 
> Wil do the trick...
> 
> Mike
> 
> ------------------------------------------
> Mike MacCana          Support Consultant  
>           C Y B E R S O U R C E
>    Level 9, 140 Queen St Melbourne 3000
> Ph : +61 3 9642 5997 Fax: +61 3 9642 5998
> 
> On Tue, 2 Jan 2001, Tib wrote:
> 
> > Ok! here's some fun that's been causing me to lose my hair in chunks because
> > I've been ripping it out. I checked out PMFirewall as someone mentioned, and
> > had initially set it up. Everything seemed fine. However, even though I ran
> > ipchains -L and it said there were no rules in place, it seems that NOTHING but
> > icmp packets are allowed through the network anymore. I've smashed my head
> > against my route table and other things but I just can't figure it out. Nothing
> > gets forwarded but icmp, everything else is no route to host (from the machines
> > inside the network that would use the address for eth0 as a gateway),
> > furthermore, it would seem that eth0's performance has been compromised as well
> > for some strange reason, data throughput of ANY kind is extremely slow even
> > though pingtimes are fantastic. I uninstalled pmfirewall and backed out every
> > other change I can think of, I've shut down and brought up the network,
> > re-added routes the way they were before, and overall exhausted my brain with
> > this problem, can someone help please???
> > 
> > <EOL>
> > Tib
> > 
> > 
> > 
> > 
> 


Reply via email to