Mysql Workbench Ssh Tunnel Dropping Wifi [Solved]

Feature	Common Cause	Primary Solution
Connection Stability	SSH Timeout settings	Enable ServerAliveInterval in SSH config
WiFi Interference	Network Adapter Power Management	Disable WiFi Power Saving mode
Workbench Behavior	Inactivity Disconnects	Increase DBMS Connection Read Timeout

Table of Contents

What is MySQL Workbench SSH Tunnel Dropping WiFi?

The “MySQL Workbench SSH tunnel dropping WiFi” issue occurs when an active encrypted connection to a remote database causes your local wireless network adapter to reset or disconnect. This is often perceived as a network crash, but it is usually a protocol conflict or a power management failure.

When MySQL Workbench initiates an SSH tunnel, it maintains a persistent socket. If the WiFi signal fluctuates even slightly, the SSH client may hang. On some operating systems, the network stack attempts to recover the driver, leading to a visible drop in WiFi connectivity.

This problem is particularly common on laptops where power-saving features are aggressive. The system may try to put the WiFi card into a low-power state while the SSH tunnel is technically “idle,” causing the tunnel to break and the network interface to restart.

Step-by-Step Solutions

1. Configure SSH KeepAlive Settings

One of the most effective ways to prevent the tunnel from timing out and crashing the WiFi interface is to send “keep-alive” packets. This ensures the connection stays active even when you aren’t running queries.

Edit your local SSH configuration file (usually located at `~/.ssh/config`):

Host *
    ServerAliveInterval 60
    ServerAliveCountMax 3

This configuration tells your client to ping the server every 60 seconds. If the server doesn’t respond after three tries, it closes the connection gracefully rather than letting the network driver hang.

2. Disable WiFi Power Management

On many Linux and Windows machines, the OS will turn off the WiFi radio to save power. When a persistent SSH tunnel is running, this causes an immediate disconnect.

For Linux users, you can disable power management using this command:

sudo iwconfig wlan0 power off

For Windows users, go to **Device Manager > Network Adapters**, right-click your WiFi card, select **Properties**, and under the **Power Management** tab, uncheck “Allow the computer to turn off this device to save power.”

3. Adjust MySQL Workbench Timeouts

MySQL Workbench has internal timeout settings that might be too aggressive for unstable WiFi connections. Increasing these values can help the application survive minor network blips.

Navigate to **Edit > Preferences > Others**. Locate the following fields and increase their values (e.g., to 600 seconds):

DBMS connection keep-alive interval
DBMS connection read timeout
SSH connection timeout

4. Use an External SSH Tunnel (Terminal)

If the built-in MySQL Workbench SSH handler continues to drop your WiFi, try creating the tunnel manually in your terminal. This is often more stable than the internal implementation.

Run this command in your terminal before opening Workbench:

ssh -L 3307:127.0.0.1:3306 username@remote_host -N

Then, in MySQL Workbench, create a “Standard TCP/IP” connection to `127.0.0.1` on port `3307`. This separates the tunnel management from the GUI application.