Bug#680548: "bind: Address already in use" error when using local forwarding
Package: openssh-client
Version: 1:6.0p1-2
Severity: important
Dear Maintainer,
* What led up to the situation?
example: ssh -L 5900:192.168.1.14:5900 dentaloffice -- will get the
bind: address error
* What exactly did you do (or not do) that was effective (or
ineffective)?
Tried this against three different ssh servers with the same results.
All the servers are
running Debian/Squeeze - one 32bit and the other two 64bit.
* What was the outcome of this action?
I get the "bind: address already in use" error message and can't connect
to remote vnc servers.
* What outcome did you expect instead?
no error message and ability to connect to remote VNC servers. This used
to work, although it's been a couple of weeks since I last needed to
connect.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages openssh-client depends on:
ii adduser 3.113+nmu3
ii debconf [debconf-2.0] 1.5.44
ii dpkg 1.16.4.3
ii libc6 2.13-33
ii libedit2 2.11-20080614-5
ii libgssapi-krb5-2 1.10.1+dfsg-1
ii libselinux1 2.1.9-5
ii libssl1.0.0 1.0.1c-3
ii passwd 1:4.1.5.1-1
ii zlib1g 1:1.2.7.dfsg-13
Versions of packages openssh-client recommends:
ii openssh-blacklist 0.4.1
ii openssh-blacklist-extra 0.4.1
ii xauth 1:1.0.7-1
Versions of packages openssh-client suggests:
pn keychain <none>
pn libpam-ssh <none>
pn monkeysphere <none>
pn ssh-askpass <none>
-- no debconf information
Reply to: