qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [Bug 1388735] Re: QEMU no longer allows to use full TCP por


From: Sergey
Subject: [Qemu-devel] [Bug 1388735] Re: QEMU no longer allows to use full TCP port range for VNC
Date: Mon, 03 Nov 2014 11:00:03 -0000

Unfortunately, standard (eirther RFB Protocl V 3.X or RFC 6143) doesn't define 
bahavior with ports different from 5900:
   Note that the only port number assigned by IANA for RFB is port 5900,
   so RFB clients and servers should avoid using other port numbers
   unless they are communicating with servers or clients known to use
   the non-standard ports.

So it is absolutely dependant on implementation, how to handle non-standard 
port numbers.
Both implementations from RealNetworks (authors of original VNC) and all other 
implementations (Tight, and numberous java applets) are allowing negative 
display numbers with one of two options:
* negative port number accepted, like :-5457 (like QEMU allowed to do before),
* ::<port number> allowed for direct port number instead of display number, 
like ::443.

It will be best for me, to allow behavior of QEMU before 2.1 (with negative 
display numbers).
But notation of ::<tcp portnumber> would also solve my problem.

Use for this is very simple - in hosting environment, I am not able to
adjust firewall to allow inbound connections for not privileged ports.

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1388735

Title:
  QEMU no longer allows to use full TCP port range for VNC

Status in QEMU:
  New

Bug description:
  After upgrade to QEMU version 2.1.0 (Debian 2.1+dfsg-4ubuntu6), I am no 
longer able to use any TCP port for VNC display.
  For example, if I need to assign VNC server a TCP port 443, I used to run:
  # qemu-system-x86_64 -vnc :-5457
  qemu-system-x86_64: Failed to start VNC server on `:-1000': can't convert to 
a number:-5457
  expected behavior: as any VNC software, take port base of 5900, substract 
5457 display number, and use TCP port 443

  I ask to change vnc port conversion routine to allow input values in
  range of all TCP ports, from 1 to 65535.

  I really depend on ability to use full TCP range for VNC port numbers,
  and inablity to do so in new version of QEMU is very disappointing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1388735/+subscriptions



reply via email to

[Prev in Thread] Current Thread [Next in Thread]