Re: Source ports for psql

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Matthew Smith <mps(at)utas(dot)edu(dot)au>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org
Subject: Re: Source ports for psql
Date: 2006-02-06 10:57:15
Message-ID: 20060206105715.GA9331@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Feb 06, 2006 at 04:35:33PM +1100, Matthew Smith wrote:
> Hello Tom,
>
> Thanks for the reply. So in other words, the postgres clients do not use a
> specific range for the source port (as a specific decision by the developers,
> or as written down in a given spec), but rather relies on the operating
> system's socket implementation to assign a source port?
>
> So in practice the source port can be any non-privileged port (from postgreses
> point of view)?

Any port at all. In Linux at least you can specify the range for port
selections made by the kernel, on my current machine it appears to be
1024 to 4999. PostgreSQL doesn't particularly care. Most programs don't
select a port for outgoing.

> I only ask this clarification to be sure to pass on the correct info on to the
> administrator of the firewall...

The suggested config for working though a firewall is to setup an ssh
tunnel and work through that.

Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Martijn van Oosterhout 2006-02-06 11:04:22 Re: old style outer joins
Previous Message James Harper 2006-02-06 10:42:22 old style outer joins