If SOCKS works on the SSH client PC but not another LAN machine, inspect the local listening address. To bind one intended assigned interface:

ssh -N -D 192.0.2.10:1080 [email protected]

Replace the documentation IP with the SSH client's real interface. Other authorized peers use that address and 1080, not their own localhost.

ControlListener role
Client ssh_config GatewayPortsDefault bind behavior for local forwards
Remote sshd_config GatewayPortsRemote -R listeners

The server still needs to permit forwarding and the requested destinations. Changing its remote-listener control does not relocate this -D socket.

Check client firewall/listener reachability and verify access from intended and denied LAN peers. SSH authenticates the tunnel owner, not each later SOCKS caller with a separate password challenge.

འབྲེལ་བའི་རྩོམ་ཡིག