[vbox-dev] libvncserver IPv6 patch
Vitali.Pelenjow at oracle.com
Mon Aug 6 06:18:29 PDT 2012
the bind port is the port, which a client should use to connect to the
I guess that if the server uses both AF_INET and AF_INET6, then
it is better to bind to the same port number and report it.
Oliver Loch wrote:
> I'm working on it - which means - I'm watching too much of the olympic games.
> I'm trying to get everything patched into the 4.2 beta till the end of the week. so that you can merge it by friday.
> I've also rewritten the IPv4 function and have to clean it up and integrate it into socket.cpp.
> While working on it, one thing is still not clear to me:
> What do I report back as bind port? v4 port? v6 port?
> I'm talking about the callback at the end of VNCServerImpl::VRDEEnableConnections in VBoxVNC.cpp that sets the VRDE_SP_NETWORK_BIND_PORT.
> Am 06.08.2012 um 13:56 schrieb Klaus Espenlaub<klaus.espenlaub at oracle.com>:
>> On 16.07.2012 17:45, Oliver Loch wrote:
>>> please find attached a Q&D patch for the libVNCServer IPv6 issue.
>>> It's licensed under the MIT-license.
>> Applied to 4.1 branch (in a slightly modified way). Will show up
>> whenever we do the next maintenance release.
>> Do you have something we can apply to trunk/4.2? We're in BETA phase
>> now, so it'd be cool to have proper support in the VNC extension pack.
>> vbox-dev mailing list
>> vbox-dev at virtualbox.org
> vbox-dev mailing list
> vbox-dev at virtualbox.org
More information about the vbox-dev