Re: Spice protocol behind a Firewall

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

 



On Tue, Feb 21, 2017 at 11:30:03AM +0100, Oscar Segarra wrote:
> Hi Christophe,
> 
> I have already read this document... and I'm not able to translate it to
> the scenario I've posted..
> 
> In this case I cannot see:
> 
> 1.- Where configure ports

Not familiar at all with squid, but I'd expect the simple config to
forward connection attempts to the same port that you specified that you
want to connect to.

> 2.- How squid redirects requests to the correct hypervisor (where VM is
> running)

Is this any different than if these were for example http servers
residing on the internal servers? Can't something like
SPICE_PROXY=external-host.example.com:8080 remote-viewer
spice://internal-host:5900
be managed by the squid proxy? The client can connect to the proxy using
the external address, tells it what it wants to connect to, and the
proxy forwards the connection.

> 3.- In my environment where I don't have oVirt... what to do with this
> command: engine-config -s SpiceProxyDefault=someProxy

Just ignore everything after the squid configuration.

Christophe

Attachment: signature.asc
Description: PGP signature

_______________________________________________
Spice-devel mailing list
Spice-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/spice-devel

[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]     [Monitors]