Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 946669FB8B4 for ; Tue, 6 Mar 2007 04:49:44 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 07557-01 for ; Tue, 6 Mar 2007 04:49:37 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.190]) by postgresql.org (Postfix) with ESMTP id 5D20B9FB427 for ; Tue, 6 Mar 2007 04:49:39 -0400 (AST) Received: by nf-out-0910.google.com with SMTP id x4so2416223nfb for ; Tue, 06 Mar 2007 00:49:38 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=googlemail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=GHOMQzMIQ2gMIrsynMAb15qzQvG13//E0abDs2jB85fO/sedHT6DJP6HKywgK2mlLluITyHfAVC8XM1VZmIFaeOxIwvNDfvYvbuvNfxXLKCRW9QcAIVtd5IdjM71upqhmI5Jrf+X2b+nAwt0pLb2CN/rr7v2x0A6hhBvDHr90+4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=nDGibEoIPiTrrEY6PMWMM6dajRL/DYbeHUjq2zQABOcftDVdo7vxCKPLf+Y9Iz/CIf/y4P04DlasRv3GW8MiUc3YE8uLwjA3SeTync0D7GpupW6eZXynK7t8513+CoFIqIVuDAc7zxmCWLx1GQhxFsqSlcMAWTGvvsbBKb4dSYs= Received: by 10.78.170.17 with SMTP id s17mr751707hue.1173170975866; Tue, 06 Mar 2007 00:49:35 -0800 (PST) Received: by 10.78.13.11 with HTTP; Tue, 6 Mar 2007 00:49:35 -0800 (PST) Message-ID: Date: Tue, 6 Mar 2007 09:49:35 +0100 From: "Moritz Bayer" To: "Phillip Smith" Subject: Re: pg_hba.conf & putty Cc: pgsql-admin@postgresql.org In-Reply-To: <00a901c75f84$d7b9fa80$9b0014ac@wbaus090> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_114105_20964184.1173170975771" References: <00a901c75f84$d7b9fa80$9b0014ac@wbaus090> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/20 X-Sequence-Number: 24844 ------=_Part_114105_20964184.1173170975771 Content-Type: text/plain; charset=WINDOWS-1252; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Thanks a lot, the change of the tunnels IP address to 127.0.0.1 made it! :-) Great! 2007/3/6, Phillip Smith : > > I know your problem (I think) > > > > Your SSH forward you said is defined as: > > Lserver.ip.address:5432 > > > > So the requests will be coming from your server's IP address via the eth0 > interface=85 You need to change this to 127.0.0.1 to make it use the lo > interface, and then the requests will come from 127.0.0.1 to match your > pg_hba.conf > > > > Cheers, > > ~p > > > > > > -----Original Message----- > *From:* pgsql-admin-owner@postgresql.org [mailto: > pgsql-admin-owner@postgresql.org] *On Behalf Of *Moritz Bayer > *Sent:* Tuesday, 6 March 2007 10:58 > *To:* Phillip Smith > *Cc:* pgsql-admin@postgresql.org > *Subject:* Re: [ADMIN] pg_hba.conf & putty > > > > hello phillip, > > yes, the connection i defined in pgadmin uses localhost:5432. > > Still, no success :( > > > > > 2007/3/6, Phillip Smith < phillip.smith@weatherbeeta.com.au>: > > What address are you connecting to on your desktop computer? You should b= e > using localhost:5432 which putty will redirect to the server via the SSH > tunnel and the server will connect to PostgreSQL on your behalf. > > > > ~p > > > > -----Original Message----- > *From:* pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgr= esql.org] > *On Behalf Of *Moritz Bayer > *Sent:* Tuesday, 6 March 2007 10:31 > *To:* pgsql-admin@postgresql.org > *Subject:* [ADMIN] pg_hba.conf & putty > > > > dear list, > > I know there are already hunderts of posts about pg_hba.conf, but still > after reading a few of them I still got troubles with this topic. > > I've got a vpn server with a ststic ip address, java apps are supposed t= o > run there receiving data from a postgresql database. > The database is running, but for changes on it I want to open a putty > connection while using pgAdmin. > In putty, I define a tunnel to port 5432, its displayed like this: > Lserver.ip.address:5432 > > Thought this entries in my pg_hba.conf would do it: > > # "local" is for Unix domain socket connections only > local all all md5 > > # IPv4 local connections: > host all all 127.0.0.1/32 md5 > > # IPv6 local connections: > host all all ::1/128 md5 > > well, it doesn't. When i run pgAdmin with an open putty connection, it > still says: error connecting to server. > > Any hints how I can find out whats still wrong? > > Thanks in advance, > Mo > > > > ********************Confidentiality and Privilege > Notice******************** > > The material contained in this message is privileged and confidential to > the addressee. If you are not the addressee indicated in this message or > responsible for delivery of the message to such person, you may not copy = or > deliver this message to anyone, and you should destroy it and kindly noti= fy > the sender by reply email. > > Information in this message that does not relate to the official business > of Weatherbeeta must be treated as neither given nor endorsed by > Weatherbeeta. Weatherbeeta, its employees, contractors or associates shal= l > not be liable for direct, indirect or consequential loss arising from > transmission of this message or any attachments > > > > ********************Confidentiality and Privilege > Notice******************** > > The material contained in this message is privileged and confidential to > the addressee. If you are not the addressee indicated in this message or > responsible for delivery of the message to such person, you may not copy = or > deliver this message to anyone, and you should destroy it and kindly noti= fy > the sender by reply email. > > Information in this message that does not relate to the official business > of Weatherbeeta must be treated as neither given nor endorsed by > Weatherbeeta. Weatherbeeta, its employees, contractors or associates shal= l > not be liable for direct, indirect or consequential loss arising from > transmission of this message or any attachments > > ------=_Part_114105_20964184.1173170975771 Content-Type: text/html; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Thanks a lot,
the change of the tunnels IP address to 127.0.0.1 made it!

:-)
Great!



2007/3/6, Phillip Smith < phillip.smith@weatherbeeta.com.au>:

I know your problem (I think)

 

Your SSH forward you said is defin= ed as:

Lserv= er.ip.address:5432

 

So the requests will be coming fro= m your server's IP address via the eth0 interface=85 You need to change this to 127.0.0.1 to make it use the lo interface, and then the requests will come from 127.0.0.1 to match your pg_hba.conf

 

Cheers,

~p

 

 

-----Original Message-----
From: pgsql-admin-owner@postg= resql.org [mailto: pgsql-admin-owner@postgresql.org] On Behalf Of Moritz Bayer

Sent: Tuesday, 6 March 200= 7 10:58
To: Phillip Smith
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] pg_hb= a.conf & putty

<= span style=3D"font-size: 12pt;"> 

hel= lo phillip,
 
yes, the connection i defined in pgadmin uses localhost:5432.

Still, no success :(




2007/3/6, Phillip Smith < phillip.smith@weatherbeeta.com.au>:

What = address are you connecting to on your desktop computer? You should be using localhost:5432 which putty will redirect to the server via the SSH tunnel and the server w= ill connect to PostgreSQL on your behalf.

 = ;

~p

 = ;

-----Original Me= ssage-----
From: pgsql-admin-owner@postgresql.org [mailto: pgsql-admin-owner@postgresql.org] On Behalf Of Moritz Bayer
Sent:
Tuesday, 6 March 2007 10:31
To: pgsql-admin@postgresql.org
Subject: [ADMIN] pg_hba.co= nf & putty

<= span style=3D"font-size: 12pt;"> 

<= span style=3D"font-size: 12pt;">dear list,

I know there are already hunderts of posts about pg_hba.conf, but still aft= er reading a few of them I still got troubles with this topic.

I've got a vpn server  with a ststic ip address, java apps are sup= posed to run there receiving data from a postgresql database.
The database is running, but for changes on it I want to open a putty connection while using pgAdmin.
In putty, I define a tunnel to port 5432, its displayed like this: Lserver.ip.address:5432

Thought this entries in my pg_hba.conf would do it:

# "local" is for Unix domain socket connections only
local   all         all            =             &nb= sp;      md5

# IPv4 local connections:
host    all         all         127.0.0.1/32        &n= bsp; md5

# IPv6 local connections:
host    all         all         ::1/128           &n= bsp;   md5

well, it doesn't. When i run  pgAdmin with an open  putty con= nection, it still says: error connecting to server.

Any hints how I can find out whats still wrong?

Thanks in advance,
Mo

<= span style=3D"font-size: 12pt;"> 

*******************Co= nfidentiality and Privilege Notice*******************

<= span style=3D"font-size: 12pt;">The material contained in this message is p= rivileged and confidential to the addressee. If you are not the addressee indicated i= n this message or responsible for delivery of the message to such person, you= may not copy or deliver this message to anyone, and you should destroy it and kindly notify the sender by reply email.

<= span style=3D"font-size: 12pt;">Information in this message that does not r= elate to the official business of Weatherbeeta must be treated as neither given nor endorsed by Weatherbeeta. Weatherbeeta, its employees, contractors or associates shall not be liable for direct, indirect or consequential loss arising from transmission of this message or any attachments =

<= span style=3D"font-size: 12pt;"> 


*******************Confidentiality and Privilege Notice*****************= **

The material contained in this message is privileged and confidential to the addressee. If you are not the addressee indicated in this message or responsible for delivery of the message to such person, you may not copy or deliver this message to anyone, and you should destroy it and kindly notify the sender by reply email.

Information in this message that does not relate to the official business of Weatherbeeta must be treated as neither given nor endorsed by Weatherbee= ta. Weatherbeeta, its employees, contractors or associates shall not be liable for direct, indirect or consequential loss arising from transmission of thi= s message or any attachments


------=_Part_114105_20964184.1173170975771--