MySQL Bugs: #2743: Problems with ssh tunneling

Bug #2743	Problems with ssh tunneling
Submitted:	12 Feb 2004 7:06	Modified:	13 Mar 2014 13:41
Reporter:	Tony Little	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	1.0.1a	OS:	Windows (Windows XP Client - Linux Server)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
I have mysql running under windows XP on my local workstation (a test server).  With Administrator I want to monitor a remote mysql server that is running on Slackware linux.  The connection to the remote server is done through an ssh tunnel (using puTTY) so the connection information entered into administrator is localhost:3316 (the tunnel is setup on port 3316 - the local mysql test server is running on 3306).  The problem is that some of the information shown after the connection is made is for the local server and some of it is for the remote server.  For instance all of the 'Health' information is for the remote server, but all of the 'Startup Variables' are for the local test server.  'Server Information' is all the remote server.  'Service Information' is all the local test server.  All server connections are for the remote server.  'User administration' is all the remote server.  'Server Logs', 'Backup', and 'Restore' don't seem to show any information so I am not sure where they are coming from.  'Catalogs' shows remote information.

How to repeat:
Run mysql server on local machine.  Connect to a remote mysql server through an ssh tunnel.

Suggested fix:
Only show information pertinent to the given connection.

Thanks for submitting the report.

The issue has been fixed. The fix will be available in the next release 1.0.2a.

After further testing we still found unsolved issues.

Therefor we have to defer the bug until we get the MySQL Instance Manager which will be able to tell us the _real_ networkname or IP of the host the server is running on.