Re: tunneling through ssh

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"