Re: tunneling through ssh

From: David Bear <David(dot)Bear(at)asu(dot)edu>
To: Steve Crawford <scrawford(at)pinpointresearch(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: tunneling through ssh
Date: 2004-08-19 00:58:11
Message-ID: 20040819005811.GC18227@asu.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Wed, Aug 18, 2004 at 04:21:24PM -0700, Steve Crawford wrote:
> On Wednesday 18 August 2004 4:13 pm, David Bear wrote:
> > I'm attempting to run pgsql through a tunnel. I'm using the default
> > pg_hba.conf file for now which has the relevant information:
> >
> > ------------
> > local all all
> > trust
> > host all all 127.0.0.1 255.255.255.255
> > trust
> > ------------
> >
> > I assume this means that the back end will bind to 127.0.0.1:5432
> > since that seems to be the default port number.
> >
> > Yet, when trying to come through the tunnel I get this in my logs
> > on the 'server' machine - the one running postgres backend.
> >
> > -----------
> > Aug 18 16:00:40 dbsrv1 sshd[41006]: error: connect_to ::1 port
> > 5432: Connection refused
> > Aug 18 16:00:40 dbsrv1 sshd[41006]: error: connect_to 127.0.0.1
> > port 5432: Connection refused
> > Aug 18 16:00:40 dbsrv1 sshd[41006]: error: connect_to localhost
> > port 5432: failed.
> > -----------
> >
> > Am I missing something obvious?
>
> Is PG set to accept tcp/ip connections? Check postgresql.conf for:
> tcpip_socket=true
>
> 127.0.0.1 is connecting through tcp/ip, not local domain sockets.

thanks for the info. I've check the postgresql.conf file and have the
following lines:
----------
tcpip_socket = true
max_connections = 40
port = 5432
virtual_host = '127.0.0.1' # what interface to listen on; defaults to any
----------

I assume I am binding to tcp socket 5432 as sockstat reveals:
----------
USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN
pgsql postgres 41229 3 tcp4 127.0.0.1:5432 *:*
----------

I still get the error:

---------
$>psql -h localhost -p 4001 test1
psql: could not receive server response to SSL negotiation packet: No
such file or directory
---------
and on the ssh'd terminal tunnel session:
--------
$ channel 3: open failed: administratively prohibited: open failed
-------

Any other suggestions?

>
> Cheers,
> Steve
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match

--
David Bear
phone: 480-965-8257
fax: 480-965-9189
College of Public Programs/ASU
Wilson Hall 232
Tempe, AZ 85287-0803
"Beware the IP portfolio, everyone will be suspect of trespassing"

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2004-08-19 01:21:54 Re: tunneling through ssh
Previous Message Steve Crawford 2004-08-18 23:21:24 Re: tunneling through ssh