Skip site navigation (1) Skip section navigation (2)

Re: tunneling through ssh

From: David Bear <David(dot)Bear(at)asu(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Steve Crawford <scrawford(at)pinpointresearch(dot)com>,pgsql-admin(at)postgresql(dot)org
Subject: Re: tunneling through ssh
Date: 2004-08-19 23:26:10
Message-ID: 20040819232610.GF23172@asu.edu (view raw or flat)
Thread:
Lists: pgsql-admin
On Wed, Aug 18, 2004 at 09:21:54PM -0400, Tom Lane wrote:
> David Bear <David(dot)Bear(at)asu(dot)edu> writes:
> > and on the ssh'd terminal tunnel session:
> > --------
> > $ channel 3: open failed: administratively prohibited: open failed
> > -------
> 
> Perhaps a firewalling problem?  Look at your kernel packet filtering
> setup ... it's not uncommon for even local-loopback traffic to be
> aggressively filtered by default, and none of the people who set these
> things up think port 5432 is a standard service :-(
> 

thanks for all the suggestions.  The solution was to tunnel
'localhost' -- the key is knowing which localhost localhost is
referring too.. so, here's what I did.

ssh -L 4001:localhost:5432 iddwb(at)dbsrv1

This allows postgresql to listen on the 'localhost' interface..

thanks for all the replies.



-- 
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

pgsql-admin by date

Next:From: David BearDate: 2004-08-19 23:29:30
Subject: long term persistent tunnels
Previous:From: Joe ConwayDate: 2004-08-19 17:10:29
Subject: Re: [HACKERS] SRPM for 8.0.0 beta?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group