Bug 532972 - Xvnc server does not support IPv6
Summary: Xvnc server does not support IPv6
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: tigervnc
Version: 22
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jan Grulich
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: IPv6Blocker
TreeView+ depends on / blocked
 
Reported: 2009-11-04 14:49 UTC by Tore Anderson
Modified: 2016-05-16 11:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-16 11:24:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Debian BTS 550789 0 None None None Never

Description Tore Anderson 2009-11-04 14:49:17 UTC
Description of problem:

The Xvnc (possibly x0vncserver as well, haven't tested) is incapable of accepting incoming connections over IPv6.  (The vncviewer tool, on the other hand, appears to support IPv6, at least it attempts to connect to remote servers over IPv6, but without a server implementation I cannot verify that it actually works.)

Version-Release number of selected component (if applicable):

tigervnc-server-1.0.0-1.fc12.i686
Fedora 12 Beta

How reproducible:

100%

Steps to Reproduce:
1. Start an Xvnc server on a machine with IPv6
2. Attempt to connect to it using it's IPv6 address
3.
  
Actual results:

vncviewer fails with "Connection refused"

Expected results:

vncviewer succeeds in connecting to the VNC server, using IPv6

Additional info:

The problem is obvious when looking at common/network/TcpSocket.cxx lines 355-356:

  if ((fd = socket(AF_INET, SOCK_STREAM, 0)) < 0)
    throw SocketException("unable to create listening socket", errorNumber);

This hardcodes the use of an AF_INET (ie. IPv4) listening socket.

There's a bug report (with patches) in Debian's BTS, not sure if those will work with the TigerVNC code base though:  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550789

Tore

Comment 1 Tore Anderson 2009-11-09 12:21:05 UTC
In my original report I wrote:

The vncviewer tool, on the other hand, appears to support IPv6, at least it attempts to connect to remote servers over IPv6, but without a server implementation I cannot verify that it actually works.

I've verified that this works correctly now.  When using a SSH tunnel to connect to the remote server (e.g. "ssh -L 5900:127.0.0.1:5900 remote-server"), I can successfully connect to ::1 on the local host, and the remote desktop shows up just fine.  So the VNC protocol itself works beautifully over IPv6, only thing that's missing is for Xvnc to be able to open a listening IPv6 socket.

Tore

Comment 2 Adam Tkac 2009-11-09 13:10:03 UTC
Missing IPv6 support on server side is known problem. Upstream report: https://sourceforge.net/tracker/?func=detail&aid=2682797&group_id=254363&atid=1126849

Comment 3 Bug Zapper 2009-11-16 15:04:42 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Adam Tkac 2010-08-18 11:33:54 UTC
Moving to rawhide, this issue won't be addressed in Fedora 12/13/14.

Comment 6 Fedora Admin XMLRPC Client 2013-05-13 14:53:29 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 7 Tim Waugh 2015-04-28 10:21:01 UTC
Fixed upstream:
  https://github.com/TigerVNC/tigervnc/pull/150

Comment 8 Nikos Mavrogiannopoulos 2015-05-19 09:12:04 UTC
Will that be included in f22 or f23?

Comment 9 Tim Waugh 2015-05-19 10:12:45 UTC
There hasn't yet been an upstream release with this change included, but when 1.4.4 is out I'm sure we'll have a Fedora update soon after.

Comment 10 Nikos Mavrogiannopoulos 2015-07-15 07:24:50 UTC
There is already a release by upstream with IPv6.
https://github.com/TigerVNC/tigervnc/releases/tag/v1.5.0

Comment 11 Fedora Admin XMLRPC Client 2015-08-20 08:44:32 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 12 Mike McCune 2016-03-28 22:46:32 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions


Note You need to log in before you can comment on or make changes to this bug.