forums › forums › SQLyog › Sync tools, Migration, Scheduled Backup and Notifications › Linux – Ssh Tunnelling
- This topic is empty.
-
AuthorPosts
-
-
October 19, 2005 at 10:32 pm #9307gberz3Member
Hi All,
I'm looking for some SSH tunnelling help. Currently I'm using Linux to synchronize two DBs on seperate systems. SJA will be running on one of the systems. I've tried getting SJA to work doing the following:
1) Create an SSH tunnel using port forwarding:
% ssh -C -L localport:remotelocalhost:remotemysqlport remotehost
2) Setting up the XML file to use the forwarded port to connect to the remote machine:
localhost root localport (from above)blah . . .yet, SJA wants to connect to localhost and not use the port I inserted. It simply acts as though no port was input and reconnects to the local DB and syncs it with itself. <_< Ideas?
-
October 20, 2005 at 1:22 am #19559RiteshMember
When you are using SSH Tunneling, you create a background tunnel process which listens on a local port and forwards all the details to the actual MySQL server. SJA connects to host and port provided in host and port element.
You can assign the local port for the SSH Tunneler in the “Port” element of the XML schema.
If you specify the same local port for the SSH Tunneling as your local MySQL port, the data are sent to the MySQL server rather then the SSH process. Thus instead of connecting to you remote server it connects to your local server.
Just assign port 3310 (provided its not used by any other application) for the local port and try the connection.
-
October 20, 2005 at 2:12 am #19560gberz3Member
Thanks, Ritesh. I don't know what was going on, but none of the other ports I used seemed to work. I tried ports like 5555, and 5551, etc. . .But apparently SJA saw that these were in use and went with default 3306? Either way, 3310 worked!
-
October 20, 2005 at 3:42 am #19561RiteshMember
This is very strange as we dont have any hardcoded port number programmed in SJA.
-
October 20, 2005 at 4:33 am #19562gberz3Member
*shrug* Maybe when you make your calls into MySQL to connect, etc. it defaults to 3306? Either way 3310 works. 😉
-
-
AuthorPosts
- You must be logged in to reply to this topic.