Bug 532972
| Summary: | Xvnc server does not support IPv6 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tore Anderson <tore> |
| Component: | tigervnc | Assignee: | Jan Grulich <jgrulich> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 22 | CC: | nmavrogi, ovasik |
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-05-16 11:24:19 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 195271 | ||
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 Missing IPv6 support on server side is known problem. Upstream report: https://sourceforge.net/tracker/?func=detail&aid=2682797&group_id=254363&atid=1126849 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 Moving to rawhide, this issue won't be addressed in Fedora 12/13/14. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Fixed upstream: https://github.com/TigerVNC/tigervnc/pull/150 Will that be included in f22 or f23? 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. There is already a release by upstream with IPv6. https://github.com/TigerVNC/tigervnc/releases/tag/v1.5.0 This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions |
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