-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Guillaume,
No, you can tunnel already. I do it all the time to connect pgadmin to our production machines. Connect to the remote machine from your os, with the ssh command. You can use "-p 2222" to specify the non-standard port, and "-D 6432" to specify which port to tunnel, for the database traffic. I'll share the exact command I use on Monday, if you like, as it's on my work computer. Anyway, then you just connect pgadmin to a server on localhost, running on that tunneled port. Works great. :) (I'm assuming you're using a real OS. No idea how to do it in Windows, or if you can even do it.) - --- wad On 10/04/2014 06:44 AM, Guillaume Lelarge wrote: > Le 4 oct. 2014 13:42, "Stephen Cook" <scli...@gmail.com > <mailto:scli...@gmail.com>> a écrit : >> >> I need to tunnel through one server to my database server (which >> only > allows connections from that server), but SSH is on a non-standard > port. >> >> According to the internet, there is an update that would add a >> "Port" > field to the settings window for this use case, but apparently that > is not in a released version of pgAdmin yet. >> >> Any idea when this update will be included? >> > > It should be in the beta release already available > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlQv8FQACgkQD+WWuyKfye0mZACfXIg4hQpkliYQVyFYjrZYG9Ga seUAn1JgEYFdDBJ6tDoSpVtvAHx1+n+w =ellz -----END PGP SIGNATURE----- -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
