Bug 5501 - Xvnc isn't reusing ports properly
Summary: Xvnc isn't reusing ports properly
Status: CLOSED FIXED
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VNC (show other bugs)
Version: pre-1.0
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.4.0
Assignee: Pierre Ossman
URL:
Keywords: prosaic, samuel_tester
Depends on:
Blocks:
 
Reported: 2015-04-22 10:58 CEST by Pierre Ossman
Modified: 2015-04-30 11:09 CEST (History)
1 user (show)

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Pierre Ossman cendio 2015-04-22 10:58:12 CEST 
Regression from 4.3.0. It was probably caused by something unrelated we got during a vendor drop, so adding a new bug rather than reopening something random. My best guess is that it is then new IPv6 code.

What happens is that new sessions fail to start if that display number was recently used. We get this in xinit.log:

>  vncext:      vncExtInit: failed to bind socket: Address already in use (98)

Not sure why as we still set SO_REUSEADDR.
Comment 1 Pierre Ossman cendio 2015-04-22 14:48:06 CEST 
Found the issue. SO_REUSEADDR got moved to after bind() by mistake, which makes it rather pointless.

I have however discovered something else odd. For some reason sshd tunnels aren't leaving any TIME_WAIT around, but tlwebaccess is. I haven't been able to figure out why.
Comment 2 Pierre Ossman cendio 2015-04-23 11:49:08 CEST 
Fixed in r30260.
Comment 3 Samuel Mannehed cendio 2015-04-30 11:09:54 CEST 
Can not reproduce anymore, tried logging in right after a logout using the HTML5 client, no issues.
Note You need to log in before you can comment on or make changes to this bug.