Speaking of RedHat (and possibly other nix's), the trouble with tcp wrappers, is that only services governed by xineted have tcp wrappers rules applied to them, whereas iptables rules apply to any daemon running on the box. Aaron -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Sanjay Chakraborty Sent: Monday, October 20, 2008 10:07 PM To: General Red Hat Linux discussion list Subject: Re: Restrict access to a particular server. Use tcpwrapper. Modify /etc/hosts.allow and /etc/hosts.deny. System checks first allow list. Put IP their. Restart xined service. Hope it will work for rhel 5 also. On Mon, Oct 20, 2008 at 3:09 AM, Rohit khaladkar <rohit.khaladkar@xxxxxxxxx> wrote: > Hi All,I have two machines with Red Hat linux 5.2 installed of which one is > a database server running Oracle 10.0.4 on it. I need a iptable rule which > would make sure that only the other machine would have access to it. > > For eg : If I have two macihnes, machine A and machine B, of which machine B > is a database server, can I setup a iptable rule on machine B , which would > allow access to the database only by machine A. > > Please help. > > Thanks! > Rohit Khaladkar > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list > -- Regards. Sanjay Chakraborty -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
