[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v3 0/8] Support multiple listening sockets per V
From: |
Daniel P. Berrange |
Subject: |
Re: [Qemu-devel] [PATCH v3 0/8] Support multiple listening sockets per VNC server |
Date: |
Fri, 3 Feb 2017 13:41:55 +0000 |
User-agent: |
Mutt/1.7.1 (2016-10-04) |
On Fri, Feb 03, 2017 at 04:29:43PM +0300, Michael Tokarev wrote:
> 03.02.2017 15:06, Daniel P. Berrange wrote:
>
> > - If a DNS name resolves to multiple distinct IP addresses,
> > the VNC server is now able to listen on all of them
> >
> > - The -vnc argument syntax is extended to allow the 'vnc'
> > and 'websocket' arguments to be listed multiple times.
> > This allows a single VNC server to listen on multiple
> > different names / addresses.
>
> Why it's needed? To me it looks like to much for a very rarely
> useful thing, no? (Just thinking out loud, nothing more)
It is very common to have virtualization hosts with multiple network
interfaces and multiple address protocols. Wanting to restrict VNC
to listen on a subset of interfaces/addresses is pretty reasonable
eg, consider a host with
eth0: 10.0.0.1
2001:beef:1
eth1: 192.168.0.1
feed:beef:1
And you want VNC to only listen on the IP addresses associated with
the public interface eth1. With current QEMU this is impossible.
Even if you setup DNS e.g.
internal.example.com A 10.0.0.1
AAAA 2001:beef:1
public.example.com A 192.168.0.1
AAAA feed:beef:1
and pass hostname public.example.com to QEMU -vnc, it'll only listen on
one of the two addresses the hostname resolves to. This series addresses
that flaw by making us open multiple listener sockets for all addresses
that are resolved.
Even with that flaw fixed, it is still unreasonable limited. There may
be multiple hostnames you wish VNC to listen on, or you may not have DNS
entries for the particular addresses you want VNC to listen on. Thus there
is need to allow for multiple addresses to be given to -vnc.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :|
- [Qemu-devel] [PATCH v3 0/8] Support multiple listening sockets per VNC server, Daniel P. Berrange, 2017/02/03
- [Qemu-devel] [PATCH v3 1/8] ui: fix regression handling bare 'websocket' option to -vnc, Daniel P. Berrange, 2017/02/03
- [Qemu-devel] [PATCH v3 2/8] ui: fix reporting of VNC auth in query-vnc-servers, Daniel P. Berrange, 2017/02/03
- [Qemu-devel] [PATCH v3 3/8] ui: refactor VncDisplay to allow multiple listening sockets, Daniel P. Berrange, 2017/02/03
- [Qemu-devel] [PATCH v3 5/8] ui: extract code to connect/listen from vnc_display_open, Daniel P. Berrange, 2017/02/03
- [Qemu-devel] [PATCH v3 4/8] ui: refactor code for populating SocketAddress from vnc_display_open, Daniel P. Berrange, 2017/02/03
- [Qemu-devel] [PATCH v3 7/8] util: add iterators for QemuOpts values, Daniel P. Berrange, 2017/02/03
- [Qemu-devel] [PATCH v3 8/8] ui: add ability to specify multiple VNC listen addresses, Daniel P. Berrange, 2017/02/03
- [Qemu-devel] [PATCH v3 6/8] ui: let VNC server listen on all resolved IP addresses, Daniel P. Berrange, 2017/02/03
- Re: [Qemu-devel] [PATCH v3 0/8] Support multiple listening sockets per VNC server, Michael Tokarev, 2017/02/03
- Re: [Qemu-devel] [PATCH v3 0/8] Support multiple listening sockets per VNC server,
Daniel P. Berrange <=
- Re: [Qemu-devel] [PATCH v3 0/8] Support multiple listening sockets per VNC server, Gerd Hoffmann, 2017/02/06