Re: Firewalls and Postgres

From: "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk>
To: Alan Carbutt <arcarbut(at)adams(dot)edu>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Firewalls and Postgres
Date: 2003-01-29 15:20:11
Message-ID: Pine.LNX.4.21.0301291510160.2839-100000@ponder.fairway2k.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 29 Jan 2003, Alan Carbutt wrote:

> Does anyone know if postgres uses any additional ports that might be
> blocked by a firewall? I'm setting up a data warehouse prototype using
> pgAccess as the front end and I'm not having too much success with
> firewalling. Any help is greatly appreciated.

Ok, rather vague question for something like this. Additional ports to the
5432, or whatever you've configured the server to listen on, I presume. I
therefore have to assume that you've opened tcp port 5432 (or whatever) and
you're seeing tcp traffic coming through and back out, in which case it's
working.

On the other hand it's not working so, have you open the firewall properly? Are
you using ident authentification? What about other
authentification/authorisation methods requiring access to external resources?

Basic network monitor should help you find out what traffic your server is
trying to send out, where it's getting to and what's happening to the reply
packets. Having said that it helps having another system to do the monitoring
with as the firewall rules can get in the way of seeing the packets you want to
see in order to see what firewall rule to create :)

--
Nigel Andrews

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Richard Huxton 2003-01-29 15:30:51 Re: ERROR: language "plpgsql" does not exist
Previous Message Francisco J Reyes 2003-01-29 15:20:07 Re: list server problems?