From: Fabrice Rouillier <fabrice@rouillier.fr>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: galene@lists.galene.org
Subject: [Galene] Re: Installation Script
Date: Mon, 12 Apr 2021 16:40:13 +0200 [thread overview]
Message-ID: <9A33A220-E732-4284-9159-34391BDD78A6@rouillier.fr> (raw)
In-Reply-To: <87im4rrb84.wl-jch@irif.fr>
[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]
Hi Juliusz
> 1. I could easily add an option to Galène to restrict the range of
> ephemeral ports used — for example, you could set the range of ports to
> 50000-60000, and only these ports would need to be forwarded. Let me
> know if you think this is useful.
>
It might be useful to make possible the use of 2 distincts coturn servers
In my case I would like one for nextcloud and one for Galène.
Nextcloud uses the use-auth-secret
Authentification and it turns out that I was unable to use it with Galene, event setting "credentialType": "hmac-sha1 » as described in your README file.
I can easily modify the script adding the two ports.
> 2. If you're using the built-in TURN server behind NAT (not recommended),
> you need to set up hairpinning in your NAT. I don't see any good way
> around it. Please mention it in the README.
>
The installation script do not the use the built-in turn but install and configure coturn. Galene is launched with the « -turn auto » option.
Would you like me to add this information ?
> Thanks again,
>
I am very pleased to contribute to the collective effort.
Fabrice.
[-- Attachment #2: Type: text/html, Size: 2410 bytes --]
next prev parent reply other threads:[~2021-04-12 14:40 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 14:37 [Galene] Galene Turn Fabrice Rouillier
2021-04-09 15:12 ` [Galene] " Alexandre IOOSS
2021-04-09 15:32 ` Fabrice Rouillier
2021-04-09 15:37 ` Fabrice Rouillier
2021-04-09 17:07 ` Alexandre IOOSS
2021-04-09 17:36 ` Fabrice Rouillier
2021-04-09 18:17 ` Fabrice Rouillier
2021-04-10 14:19 ` Juliusz Chroboczek
2021-04-10 14:41 ` Fabrice Rouillier
2021-04-12 7:10 ` [Galene] Installation Script Fabrice Rouillier
2021-04-12 7:56 ` [Galene] " Rémy Dernat
2021-04-12 8:07 ` Antonin Décimo
2021-04-12 8:47 ` Rémy Dernat
2021-04-12 11:31 ` Juliusz Chroboczek
2021-04-12 12:25 ` Dernat Rémy
2021-04-12 14:42 ` [Galene] Statistics [was: Installation Script] Juliusz Chroboczek
2021-04-12 15:38 ` [Galene] " Dernat Rémy
2021-04-12 16:07 ` Juliusz Chroboczek
2021-04-12 15:45 ` [Galene] Re: Statistics Michael Ströder
2021-04-12 16:10 ` Juliusz Chroboczek
2021-04-12 16:19 ` Michael Ströder
2021-04-12 16:44 ` [Galene] Re: Statistics [was: Installation Script] Alexandre IOOSS
2021-04-13 7:16 ` Dernat Rémy
2021-04-13 10:20 ` Juliusz Chroboczek
2021-04-13 12:02 ` Dernat Rémy
2021-04-13 12:11 ` Juliusz Chroboczek
2021-04-13 12:38 ` Dernat Rémy
2021-04-13 12:58 ` Michael Ströder
2021-04-12 9:49 ` [Galene] Re: Installation Script Fabrice Rouillier
2021-04-12 11:30 ` Juliusz Chroboczek
2021-04-12 14:40 ` Fabrice Rouillier [this message]
2021-04-12 14:44 ` Juliusz Chroboczek
2021-04-12 15:01 ` Toke Høiland-Jørgensen
2021-04-12 15:11 ` Michael Ströder
2021-04-12 15:17 ` Fabrice Rouillier
2021-04-12 15:14 ` [Galene] ephemeral port range config Michael Ströder
2021-04-13 7:09 ` [Galene] Re: Installation Script Fabrice Rouillier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9A33A220-E732-4284-9159-34391BDD78A6@rouillier.fr \
--to=fabrice@rouillier.fr \
--cc=galene@lists.galene.org \
--cc=jch@irif.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox