ports/186808: www/virutalbox-ose VNC option doesn't support port ranges for "Remote Desktop Server Port" in Display, Remote Display

[Derek Schrock]

>Number:         186808
>Category:       ports
>Synopsis:       www/virutalbox-ose VNC option doesn't support port ranges for "Remote Desktop Server Port" in Display, Remote Display
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Sun Feb 16 01:50:00 UTC 2014
>Closed-Date:
>Last-Modified:
>Originator:     Derek Schrock
>Release:        FreeBSD 10.0-RELEASE amd64
>Organization:
>Environment:
System: FreeBSD ircbsd 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 22:34:59 UTC 2014 root at snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
>Description:
Base off the documentation at http://www.virtualbox.org/manual/ch07.html
supported virtualbox platforms allow you to run RDP/VRDP on a port range
(search for "list of ports").  It would be nice if the www/virtualbox-ose VNC
extension would support a range of ports for the "Remote Desktop Server Port"
in Display, Remote Display. 

Currently if you try to use a range the inital number is used.  ex: two VM
configured with 5900-5999 range in "Remote Desktop Server Port" both still try
to start a VNC server on port 5900 (one fails to enable VNC)

>How-To-Repeat:
start two VMs with the a range instead of a single port number for "Remote 
Desktop Server Port"

>Fix:
Add support to the VNC extension to read the range and start VNC on the first
open VNC port.

5900-5999

If 5900 is in use 5901.
>Release-Note:
>Audit-Trail:
>Unformatted: