Hi all
I've been doing a little reading on xinetd, and see that you can use it to
forward ports for services to other machines, just like you can with
ipmasqadm portfw.
Could anyone offer an opinion regarding which is the better way to do
this, and why?
Also, I just noticed the ipchains rpm on RH 7.0 comes with a
/etc/rc.d/init.d/ipchains script (it doesn't exist on my 6.1 box). With a
few minutes of playing I quickly found deficiencies in the ipchains-save
and ipchains-restore scripts that it uses to maintain a firewall. For
example, rules like /sbin/ipchains -M -S 7200 120 7200 used to change
timeout values get lost during a save. I tried adding it to the config
file, but it gets clobbered on the next save.
It's a nice idea, but is this the best redhat has to offer? I'm no expert
at this stuff, but on other boxes I have created my own rc.d script to
control my firewall, and used rules I have developed over time (and lots
from this list) that are a far better solution. I've tried things like
mason too, but despite being very powerful It gave me trouble (I'm not the
sharpest tool in the shed).
Sorry, this has turned into a little rant. I guess I just think by now,
Red Hat would have come up with a better solution to a critical issue.
charles
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
