search for: websockify

Hi, we started using centos7 to run kvm+libvirt. For novnc to virtual machines I like to start websockify as a daemon by libvirt (as a hook) Under Debian I used the line: # start-stop-daemon --start --chuid $RUNUSER --make-pidfile --pidfile $PIDFILE --startas $PROGRAM -- $OPTIONS which creates a nice pidfile. In Centos I figured out, to include /etc/init.d/functions and I tried: # daemon --user $RU...

...uplex protocol layered on top of HTTP [a]. >>> Is there a WebSocket proxy that turns WS into plain TCP (a bit like >>> stunnel)? Google suggests [b]. >>> >>> [a] https://en.wikipedia.org/wiki/WebSocket#Protocol_handshake >>> [b] https://github.com/novnc/websockify >> >> qemu already knows how to connect as a client to websockets; Dan Berrange >> knows more about that setup. I suspect it would not be too difficult to >> teach the qemu NBD client code to use a WebSocket instead of a Unix or TCP >> socket as its data source. >...

...; > >>>Is there a WebSocket proxy that turns WS into plain TCP (a bit like > > >>>stunnel)? Google suggests [b]. > > >>> > > >>>[a] https://en.wikipedia.org/wiki/WebSocket#Protocol_handshake > > >>>[b] https://github.com/novnc/websockify > > >> > > >>qemu already knows how to connect as a client to websockets; Dan Berrange > > >>knows more about that setup. I suspect it would not be too difficult to > > >>teach the qemu NBD client code to use a WebSocket instead of a Unix or TCP >...

...d on top of HTTP [a]. > >>>Is there a WebSocket proxy that turns WS into plain TCP (a bit like > >>>stunnel)? Google suggests [b]. > >>> > >>>[a] https://en.wikipedia.org/wiki/WebSocket#Protocol_handshake > >>>[b] https://github.com/novnc/websockify > >> > >>qemu already knows how to connect as a client to websockets; Dan Berrange > >>knows more about that setup. I suspect it would not be too difficult to > >>teach the qemu NBD client code to use a WebSocket instead of a Unix or TCP > >>socket as i...

...t it > seems as if they are a full-duplex protocol layered on top of HTTP [a]. > Is there a WebSocket proxy that turns WS into plain TCP (a bit like > stunnel)? Google suggests [b]. > > [a] https://en.wikipedia.org/wiki/WebSocket#Protocol_handshake > [b] https://github.com/novnc/websockify qemu already knows how to connect as a client to websockets; Dan Berrange knows more about that setup. I suspect it would not be too difficult to teach the qemu NBD client code to use a WebSocket instead of a Unix or TCP socket as its data source. > > ... > >> When qemu is ru...

...-daemon > "Implementation of Linux Standard Base specification" > > Sebastian > On Tue, Jun 02, 2015 at 11:06:59AM +0200, skotthof wrote: >> Hi, >> >> we started using centos7 to run kvm+libvirt. >> For novnc to virtual machines I like to start >> websockify as a daemon by libvirt (as a hook) >> >> Under Debian I used the line: >> # start-stop-daemon --start --chuid $RUNUSER --make-pidfile --pidfile >> $PIDFILE --startas $PROGRAM -- $OPTIONS >> which creates a nice pidfile. >> >> In Centos I figured out, to in...

...s there a WebSocket proxy that turns WS into plain TCP (a bit like > > > >>>stunnel)? Google suggests [b]. > > > >>> > > > >>>[a] https://en.wikipedia.org/wiki/WebSocket#Protocol_handshake > > > >>>[b] https://github.com/novnc/websockify > > > >> > > > >>qemu already knows how to connect as a client to websockets; Dan Berrange > > > >>knows more about that setup. I suspect it would not be too difficult to > > > >>teach the qemu NBD client code to use a WebSocket instead o...

On Thu, 28 May 2020, Richard W.M. Jones wrote: > On Thu, May 28, 2020 at 12:24:22AM +0000, Eric Wheeler wrote: > > On Mon, 15 Oct 2018, Nir Soffer wrote: > > > On Sat, Oct 13, 2018 at 9:45 PM Eric Wheeler <nbd@lists.ewheeler.net> wrote: > > > Hello all, > > > > > > It might be neat to attach ISOs to KVM guests via websockets. 

...at-lsb package for start-stop-daemon "Implementation of Linux Standard Base specification" Thanks, Sebastian On Tue, Jun 02, 2015 at 11:06:59AM +0200, skotthof wrote: > Hi, > > we started using centos7 to run kvm+libvirt. > For novnc to virtual machines I like to start > websockify as a daemon by libvirt (as a hook) > > Under Debian I used the line: > # start-stop-daemon --start --chuid $RUNUSER --make-pidfile --pidfile $PIDFILE --startas $PROGRAM -- $OPTIONS > which creates a nice pidfile. > > In Centos I figured out, to include /etc/init.d/functions and...

....1.0-16.el6 to 1.1.0-18.el6, our VNC client kept getting killed after connecting for about 180s. We had to downgrade back to -16 to avoid this issue. We have a setup which allows users to log into our system via a web browser, with TigerVNC as the VNC server, noVNC as the client, and connecting via Websockify. With the update of TigerVNC, the VNC client kept getting killed 180s after logging in -- the user is returned to the login page. We are using CentOS 6.8. We can't figure out what the problem might be -- the update seem to be mostly changes related to x11-server - could this be somehow related...

...bout WebSockets until today but it seems as if they are a full-duplex protocol layered on top of HTTP [a]. Is there a WebSocket proxy that turns WS into plain TCP (a bit like stunnel)? Google suggests [b]. [a] https://en.wikipedia.org/wiki/WebSocket#Protocol_handshake [b] https://github.com/novnc/websockify ... > When qemu is running headless using a VNC or Spice display we can access > the display of https+websockets using things like noVNC---which is out of > scope to this converstation---but I'm just saying that such an existing > web front-end for the display could be extended...

...y are a full-duplex protocol layered on top of HTTP [a]. > > Is there a WebSocket proxy that turns WS into plain TCP (a bit like > > stunnel)? Google suggests [b]. > > > > [a] https://en.wikipedia.org/wiki/WebSocket#Protocol_handshake > > [b] https://github.com/novnc/websockify > > qemu already knows how to connect as a client to websockets; Dan Berrange > knows more about that setup. I suspect it would not be too difficult to > teach the qemu NBD client code to use a WebSocket instead of a Unix or TCP > socket as its data source. Actually the inverse. T...