On Wed, Aug 18, 2004 at 09:21:54PM -0400, Tom Lane wrote:
> David Bear <[EMAIL PROTECTED]> 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 p
David Bear <[EMAIL PROTECTED]> wrote:
>
> I'm attempting to run pgsql through a tunnel.
[snip]
Through an ssh tunnel, using port-forwarding, I'm guessing?
>
> Am I missing something obvious?
Can you "psql -p 5432" on the machine on which the server is running?
Here's what I just did successf
David Bear <[EMAIL PROTECTED]> 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 traf
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
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
> hostall all 127.0.0.1 255.255.