Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Specify Ssh Connection Local Port?

forums › forums › SQLyog › Using SQLyog › Specify Ssh Connection Local Port?

  • This topic is empty.
Viewing 3 reply threads
  • Author
    Posts
    • May 19, 2011 at 3:39 pm #12337
      jamckinn
      Member

      There used to be a field to specify a local port on the ssh connection tab. Is it possible with the latest sqlyog version, how?

      Thanks,

      Jason

    • May 19, 2011 at 9:24 pm #32270
      peterlaursen
      Participant

      It is not required any more. We will now 'pick' a free/unused high-numbered port automatically. This ensures that multiple program instances using SSH tunnel will not conflict (use the same port) what could cause rather bad problems (including that SQLyog connected to another server than user wanted if SSH tunneling was used by more conections automatically – what could ultimately cause data loss actually). This was like this since version 8.21 (and you may check release notes for this one).

      We do not have a single complaint that there is any problem with that. Do you have a specific reason why you want to define the port yourself – such as firewall or proxy problems for instance?

    • May 20, 2011 at 3:23 pm #32271
      jamckinn
      Member

      No problems in SQLyog. I'm actually purposely wanting multiple program instances using SSH tunnel

      My local, development machine is running an application server that connects to a remote server database. When I was able to define the local ssh port the application server “shared” the connection sqlyog was using to the database instead of having to run an additional ssh tunnel. Made it very easy to switch between development, staging and production database servers by just connecting in SQLyog.

      Looks like a static local port isn't possible anymore?

    • May 20, 2011 at 8:51 pm #32272
      peterlaursen
      Participant

      The local port used by SSH tunnel will be picked automatically (from the pool of unused high-numbered ports). Windows will protect against the port being used by other programs.

      I don not understand your scenario (or reqeust if there is so). Before 8.21 a user could be connected to another server than what he thought (if he specified the same local port for more than one connection) wwiht multiple SQLyog instances or other programs using SSH. For those users that wer not aware of this and did not understand the internals of SSH it was very dangerous actually (you could perform actions on a master instead of a slave for instance).

      What is the problem with multiple tunnels?

  • Author
    Posts
Viewing 3 reply threads
  • You must be logged in to reply to this topic.