Bug#680548: marked as done ("bind: Address already in use" error when using local forwarding)
Your message dated Sat, 07 Jul 2012 11:31:59 +0400
with message-id <4FF7E5EF.5080303@msgid.tls.msk.ru>
and subject line Re: Bug#680548: "bind: Address already in use" error when using local forwarding
has caused the Debian Bug report #680548,
regarding "bind: Address already in use" error when using local forwarding
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
680548: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680548
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
On 07.07.2012 07:36, Gary Dale wrote:
> Sorry, it appears it's a different package's problem - the SID version of the KVM packages have hijacked the ports I normally use.
>
> root@transponder:/home/garydale# netstat -nap | grep :5900
> tcp 0 0 0.0.0.0:5900 0.0.0.0:* LISTEN 4433/krfb
This is krfb process, which is, apparently, KDE desktop sharing
application. You're trying to redirect port 5900:
> ssh -L 5900:192.168.1.14:5900 dentaloffic
which is in use by krfb, which makes sense, since 5900 is first
VNC port.
> root@transponder:/home/garydale# netstat -nap | grep :5901
> tcp 0 0 127.0.0.1:5901 0.0.0.0:* LISTEN 1421/kvm
> tcp 0 0 127.0.0.1:50226 127.0.0.1:5901 ESTABLISHED 1349/python
> tcp 0 0 127.0.0.1:5901 127.0.0.1:50226 ESTABLISHED 1421/kvm
These are port 5901, which is second VNC port, which has nothing
to do with 5900 except that both are usually used by VNC.
I fail to see how a) it is a bug in openssh, no other application
can use a port which is already in use -- openssh merely reports
back what kernel reported, and kernel correctly reported the port
being busy, and b) how it is related to kvm which took -- according
to your own settings! -- another port.
I'm not an openssh maintainer, but I'm closing this bugreport
anyway, since this is definitely not a bug, it is intended
behavour.
Thanks,
/mjt
--- End Message ---
Reply to: