Re: Port blocked by iptables firewall

From: "Greg Campbell" <greg(dot)campbell(at)us(dot)michelin(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: Port blocked by iptables firewall
Date: 2003-12-12 22:18:02
Message-ID: 3FDA3E9A.4553F710@us.michelin.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

I understand the locked down ports thing. I am now surprised that I
didn't have this problem in RH8.

For some reason when I installed PostgreSQL on my RH8 machines, using
the RPM I did not run into this particular problem as I recall. (This
time both RH9 and PostgreSQL were factory installed on a DELL server). I
don't remember changing/adjusting the Linux Security Levels. My RH8
doesn't seem to be using iptables, there is no /etc/sysconfig/iptables
file.

So I think use the System Tools ->Security Level administrator is doing
something different under the hood now. While my RH8 install has a
iptables executable, it seems to have nothing (empty files) to work
against. I believe it is managing the older ipchains security. For
curiosity sake, what did you do in RH8 to open up port 5432? Does lokkit
function against both systems?

Tom Lane wrote:
>
> "Greg Campbell" <greg(dot)campbell(at)us(dot)michelin(dot)com> writes:
> > [ Red Hat 9 blocks external port-5432 traffic by default ]
>
> Yeah. This was true in Red Hat 8 as well. I'm not sure whether other
> distros are equally paranoid, but Red Hat locks down most ports by
> default ...
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster

In response to

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message Ken Kazinski 2003-12-12 23:36:41 Unable To Connect
Previous Message Tom Lane 2003-12-12 21:19:00 Re: Port blocked by iptables firewall