guacamole-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "brian mullan (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (GUACAMOLE-312) VNC over SSH
Date Wed, 16 Aug 2017 09:51:00 GMT

    [ https://issues.apache.org/jira/browse/GUACAMOLE-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16128568#comment-16128568
] 

brian mullan edited comment on GUACAMOLE-312 at 8/16/17 9:50 AM:
-----------------------------------------------------------------

I for one would agree with Nick's comment.

In my use-case...  for container desktop access & pulseaudio.

Pulseaudio supports network sound by loading Pulseaudio's TCP module.
 
example:
added line in the Host OS (host for the containers) ... /etc/pulse/default.pa -or- on linux
when using xrdp in ... /etc/xrdp/pulse/default.pa:

*load-module module-native-protocol-tcp auth-ip-acl=127.0.0.1;10.0.3.0/24*

the above tells the Host pulseaudio server to allow TCP connections from the Host itself (127.0.0.1)
but also from the container network (10.0.3.0/24).   Thus containers which have not sound
device themselves can redirect all sound/audio to the pulseaudio server of the Host OS .

If guacamole can pick that up then containers will be sound enabled.. which right now is a
problem without much added configuration ***for docker/lxc/lxd*** etc.

Being able to redirect pulseaudio's Port 4713 via SSH might be one way to accomodate this
for user sessions with contianers.?



was (Author: bmullan):
I for one would agree with Nick's comment.

In my use-case...  for container desktop access & pulseaudio.

Pulseaudio supports network sound by loading Pulseaudio's TCP module.
 
example:
added line in the Host OS (host for the containers) ... /etc/pulse/default.pa -or- on linux
when using xrdp in ... /etc/xrdp/pulse/default.pa:

*load-module module-native-protocol-tcp auth-ip-acl=127.0.0.1;10.0.3.0/24*

the above tells the Host pulseaudio server to allow TCP connections from the Host itself (127.0.0.1)
but also from the container network (10.0.3.0/24).   Thus containers which have not sound
device themselves can redirect all sound/audio to the pulseaudio server of the Host OS .

If guacamole can pick that up then containers will be sound enabled.. which right now is a
problem without much added configuration for docker/lxc/lxd etc.

Being able to redirect pulseaudio's Port 4713 via SSH might be one way to accomodate this
for user sessions with contianers.?


> VNC over SSH
> ------------
>
>                 Key: GUACAMOLE-312
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-312
>             Project: Guacamole
>          Issue Type: New Feature
>          Components: VNC
>            Reporter: Michael Jumper
>            Priority: Minor
>
> {panel:bgColor=#FFFFEE}
> *The description of this issue was copied from [GUAC-223|https://glyptodon.org/jira/browse/GUAC-223],
an issue in the JIRA instance used by the Guacamole project prior to its acceptance into the
Apache Incubator.*
> Comments, attachments, related issues, and history from prior to acceptance *have not
been copied* and can be found instead at the original issue.
> {panel}
> It would be useful to provide access to VNC over SSH as an option.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message