Teamviewer and Firewall-logs

[Niels Kobschätzki]

Hi,

I am new to Qubes and I need a working Teamviewer (best would be TV9). I installed TV9 in a Fedora23-AppVM and TV11 in a Debian8-AppVM. Teamviewer starts up fine but it cannot connect. I am using Linux for some time now and that's a problem I only had when the teamviewerd didn't run but from what I see, it runs.

a) Any ideas why it can't connect? The only thing I found is someone who couldn't make it run in a Linux-AppVM but a Windows-AppVM. I don't want to install Windows in Qubes just for TeamViewer

b) How do I do persistent "sudo systemctl enable teamviewerd.service". If I understood it correctly changes to the root-filesystem of an AppVM is wiped on reboot. So how would I do this?

c) Where can I find in a standard-Qubes-installation the firewall-logs? I'd like to know if maybe something gets denied when Teamviewer runs and that this is the reason for my problems.

Niels

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2016-05-24 21:02, Niels Kobschätzki wrote:
> Hi,
>
> I am new to Qubes and I need a working Teamviewer (best would be
> TV9). I installed TV9 in a Fedora23-AppVM and TV11 in a
> Debian8-AppVM. Teamviewer starts up fine but it cannot connect. I
> am using Linux for some time now and that's a problem I only had
> when the teamviewerd didn't run but from what I see, it runs.
>
> a) Any ideas why it can't connect? The only thing I found is
> someone who couldn't make it run in a Linux-AppVM but a
> Windows-AppVM. I don't want to install Windows in Qubes just for
> TeamViewer
>

I haven't had any problems with the Teamviewer web client in Google
Chrome in a Fedora-based AppVM, but it sounds like you want to install
the client (which I haven't tried).

If it requires allowing inbound network access, take a look here:

https://www.qubes-os.org/doc/qubes-firewall/#tocAnchor-1-1-5

> b) How do I do persistent "sudo systemctl enable
> teamviewerd.service". If I understood it correctly changes to the
> root-filesystem of an AppVM is wiped on reboot. So how would I do
> this?
>

Two options:

1. Add a line to /rw/config/rc.local and make it executable. All
commands will be executed as root each time the VM starts up.

2. Use a StandaloneVM.

https://www.qubes-os.org/doc/glossary/#tocAnchor-1-1-8
https://www.qubes-os.org/doc/software-update-vm/

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXRSnQAAoJENtN07w5UDAwWO4P/RXD9DizudPwth/KX9R7X4Xw
3OWmqabzIEBb/BMl9+VbgTKHa94mR+hpZ/ahMH+DrU/z0oOLBoZ/YfzQqhEtVeQE
P9zYekKA+FqPn4JrzZ/Whd4yR36MB4yvKaQqrd9j7ReKq5pbzjSexGqCDCGoukA3
AqssLcz6j7U2jn7Z5HdatFhIURNQ0b7ToZhN2Yl3/+OnI4YaEbmUlLFvRg5MgiGI
4MDrfN2spL7qoRpaNvoD51V4t2BNxlmgLicr2cjxe6p43YQpU+1/U5oAJz/PAUCL
do1wDJ2kMOnUVnNI4n3UGpV+I3sQE3O+kzv4LE6ILtRtL3AiN1e7B9Tqb4udbpdx
N28eofAcIb5hkG0AjxaQbEL96UbmYILxVPPICdEysMnhZ+Jf0HAdtJo6JEZM+AoZ
6QLe78P/XTYTYtQUSQHUUUfgjNOtsdLSQ7Yzn1OIxs2NNHWmLf0cualV7eIevfIF
8pn+W8nHrqXykLgeizxmp6B6x5e3H/l/S3JLndjRfN5rtNk/ovO0CA6/O3WzS0Iu
gXkpBnv/6JITfZhXQB9mHTEIyVWQ53CBe8NNJoMMpN7eufzvFXZfGBw5UnZ7logS
L1TJ2mTVao15sKpstNvAJ7qes054WYA1nhYGv73st5E6+ykYK9NQyPS0AEqJ+24j
0BOfBzzCIf9hmtodMW1+
=tjLd
-----END PGP SIGNATURE-----

[Alex]

On 05/25/2016 06:28 AM, Andrew David Wong wrote:
> On 2016-05-24 21:02, Niels Kobschätzki wrote:
>> Hi,
>
>> I am new to Qubes and I need a working Teamviewer (best would be
>> TV9). I installed TV9 in a Fedora23-AppVM and TV11 in a
>> Debian8-AppVM. Teamviewer starts up fine but it cannot connect. I
>> am using Linux for some time now and that's a problem I only had
>> when the teamviewerd didn't run but from what I see, it runs.
>
>> a) Any ideas why it can't connect? The only thing I found is
>> someone who couldn't make it run in a Linux-AppVM but a
>> Windows-AppVM. I don't want to install Windows in Qubes just for
>> TeamViewer
>
>
> I haven't had any problems with the Teamviewer web client in Google
> Chrome in a Fedora-based AppVM, but it sounds like you want to install
> the client (which I haven't tried).
>
> If it requires allowing inbound network access, take a look here:
>
> https://www.qubes-os.org/doc/qubes-firewall/#tocAnchor-1-1-5

I've been using the standalone TV client (which is just the standard
windows application packaged with a preconfigured Wine...) on a vanilla
fedora 23 appvm. Just downloaded the .tar.gz, uncompressed, and tried to
start from command line. There is no actual need to "install" that in
the form of service/systemd files.

Reading the documentation on the page for the linux packages (now the
link is "installation on unsupported distributions", but is just a
deeper description of the process), you'll find that there is a command
to check for missing libraries. Make sure everything TV needs is
installed. The application may/may not start anyway, but may not work if
everything it needs is not installed.

The command to check for libraries is

$ tv-setup checklibs

>
>> b) How do I do persistent "sudo systemctl enable
>> teamviewerd.service". If I understood it correctly changes to the
>> root-filesystem of an AppVM is wiped on reboot. So how would I do
>> this?

As I said, there is no actual need to install the service. If you want,
you can try Andrew's suggestions, but the question may be related to
another situation: what if you wanted to control the appVM with teamviewer?

Well, that's unsupported territory. I never tried, and AFAIR there is
something related to how Qubes composes windows from the various AppVMs
that makes it impossible to capture a "screen" of an AppVM. If you try,
please report your findings on the list.

--
Alex

[ni...@kobschaetzki.net]

First: thanks all, it works now. Not as I expected, but it works. Details follow beneath :)

> On May 25, 2016 at 7:25 AM Alex <alex...@gmx.com> wrote:
>
> On 05/25/2016 06:28 AM, Andrew David Wong wrote:
>
> > On 2016-05-24 21:02, Niels Kobschätzki wrote:
> >
> > > Hi,
> > >
> > > I am new to Qubes and I need a working Teamviewer (best would be
> > > TV9). I installed TV9 in a Fedora23-AppVM and TV11 in a
> > > Debian8-AppVM. Teamviewer starts up fine but it cannot connect. I
> > > am using Linux for some time now and that's a problem I only had
> > > when the teamviewerd didn't run but from what I see, it runs.

<snip>

> > https://www.qubes-os.org/doc/qubes-firewall/#tocAnchor-1-1-5
> > I've been using the standalone TV client (which is just the standard
> > windows application packaged with a preconfigured Wine...) on a vanilla
> > fedora 23 appvm. Just downloaded the .tar.gz, uncompressed, and tried to
> > start from command line. There is no actual need to "install" that in
> > the form of service/systemd files.

I used the deb in the Debian-AppVM and the rpm in the Fedora-AppVM. That didn't work. Apparently it is no problem with the firewall but something else. The teamviewer-log tells me something something .Xauthority.
Using the files from the .tar.gz works though. So I use that. Good enough for me.

<snip>

> > > b) How do I do persistent "sudo systemctl enable
> > > teamviewerd.service". If I understood it correctly changes to the
> > > root-filesystem of an AppVM is wiped on reboot. So how would I do
> > > this?
> > > As I said, there is no actual need to install the service. If you want,
> > > you can try Andrew's suggestions, but the question may be related to
> > > another situation: what if you wanted to control the appVM with teamviewer?
>
> Well, that's unsupported territory. I never tried, and AFAIR there is
> something related to how Qubes composes windows from the various AppVMs
> that makes it impossible to capture a "screen" of an AppVM. If you try,
> please report your findings on the list.

That's not in my use case. I just need the TV-client for supporting people. And since I need to use a license which is for TV9 to be able to connect to TV-hosts (and not full clients) in a corporate environment, I need to use the TV9-client.

One problem less to solve :)

Niels