Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#30358 - [libvncserver] PLEASE ENTER SUMMARY

Attached to Project: Arch Linux
Opened by Oliver L. (Grimeton) - Tuesday, 19 June 2012, 12:31 GMT
Last edited by Andrea Scarpino (BaSh) - Friday, 06 July 2012, 13:37 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Hi,

when using libvncserver together with VirtualBox, the system listens for an incoming VNC connection on IPv4 and on IPv6.

With version 0.9.8.2-1 everything works as expected, but with the latest version, libvncserver always tries to use port 5900 on IPv6 independent on what you hand VBoxHeadless on the command line.

If one VBoxHeadless process is running and you want to start another one on port 5901, then the IPv4 listener is set up correctly, but the IPv6 one tries to use 5900.

If one downgrades back to 0.9.8.2-1 everything is working fine, so expect this to be an libvncserver error instead of a VirtualBox one.

Steps to reproduce:

- Install Virtualbox (OSE)
- Create two VMs
- Start the first VM and watch the output: VBoxHeadless -s vm1 -n -m 5900
19/06/2012 14:30:02 Listening for VNC connections on TCP port 5900
19/06/2012 14:30:02 Listening for VNC connections on TCP6 port 5900

- Start the second VM and watch the output: VBoxHeadless -s vm2 -n -m 5901
19/06/2012 14:31:02 Listening for VNC connections on TCP port 5901
19/06/2012 14:31:02 rfbListenOnTCP6Port: error in bind IPv6 socket: Address already in use

If you have further questions feel free to contact me.

KR,

Grimeton
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Friday, 06 July 2012, 13:37 GMT
Reason for closing:  Not a bug
Additional comments about closing:  see Jan's reply
Comment by Andrea Scarpino (BaSh) - Tuesday, 19 June 2012, 15:47 GMT
Please report this upstream. I only added openssl support in the 0.9.9 update.

https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/libvncserver&id=f00654b23bce64eaec022f9e6187b78517f19a4e
Comment by Jan de Groot (JGC) - Friday, 06 July 2012, 12:31 GMT
0.9.9 gained full ipv6 support. Looking at changes in the code, the default ports for ipv4 and ipv6 are maintained in two different variables, so if the application using this library changes the ipv4 port but doesn't set the ipv6 port, you'll run into this issue.
Comment by Oliver L. (Grimeton) - Friday, 06 July 2012, 12:32 GMT
Those problem will be solved with VirtualBox Version 4.2

I'm already working on this and it will be part of the main source tree of 4.2.

KR,

Oliver

Loading...