pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: David Bear <David.Bear@asu.edu>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Steve Crawford <scrawford@pinpointresearch.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: tunneling through ssh
Date: Thu, 19 Aug 2004 16:26:10 -0700
Message-ID: <20040819232610.GF23172@asu.edu> (raw)
In-Reply-To: <6619.1092878514@sss.pgh.pa.us>
References: <20040818231312.GA18227@asu.edu>
	<200408181621.24097.scrawford@pinpointresearch.com>
	<20040819005811.GC18227@asu.edu>
	<6619.1092878514@sss.pgh.pa.us>

On Wed, Aug 18, 2004 at 09:21:54PM -0400, Tom Lane wrote:
> David Bear <David.Bear@asu.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@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"



view thread (6+ messages)

Message-ID: <20040819232610.GF23172@asu.edu>
Permalink:  ../20040819232610.GF23172@asu.edu/
Also on:    postgresql.org/message-id/20040819232610.GF23172@asu.edu

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: David.Bear@asu.edu, tgl@sss.pgh.pa.us, scrawford@pinpointresearch.com
  Subject: Re: tunneling through ssh
  In-Reply-To: <20040819232610.GF23172@asu.edu>
  References: <20040818231312.GA18227@asu.edu> <200408181621.24097.scrawford@pinpointresearch.com> <20040819005811.GC18227@asu.edu> <6619.1092878514@sss.pgh.pa.us> <20040819232610.GF23172@asu.edu>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox