From: Fabrice Rouillier <fabrice@rouillier.fr>
To: galene@lists.galene.org
Subject: [Galene] Galene + Firefox & Nat
Date: Sat, 1 May 2021 09:49:34 +0200 [thread overview]
Message-ID: <9A91101D-D607-45A0-846D-6CC9A58DE525@rouillier.fr> (raw)
In-Reply-To: <87h7jpdngw.wl-jch@irif.fr>
[-- Attachment #1: Type: text/plain, Size: 2279 bytes --]
Hi all,
Something I can not explain or that might have a simple solution I didn’t find.
I have installed Galène on a raspberry behind a NAT (Freebox) using a reverse proxy and the built-in turn in the following way :
- Virtual machine M1 with a reverse proxy (Traefik)
- Raspberry M2 with Galene using the built-in turn server on port 1194 and the insecure option, precisely galene -insecure -turn <EXTERNAL IP>:1194
The nat (Freebox) : ports 80 and 443 are forwarded to M1, port 1194 to M2
This configuration works perfectly (Safari, Chrome, Brave clients) except with firefox clients
It seems that problems occur also for Jitsi : https://github.com/jitsi/jitsi-meet/issues/4758 <https://github.com/jitsi/jitsi-meet/issues/4758>
Cheers,
Fabrice.
-------------------------
Fabrice Rouillier
fabrice@rouillier.fr
Bureau virtuel : https://www.rouillier <https://www.rouillier/>.fr/visio/fabrice
> Le 29 avr. 2021 à 19:12, Juliusz Chroboczek <jch@irif.fr> a écrit :
>
> I'm preparing Galène for simulcast, and that has caused some changes to
> the protocol. In short, tracks are no longer labelled, we're labelling
> streams, and we now use the track.kind and track.rid fields to
> disambiguate.
>
> This has some consquences both on the protocol and the protocol.js
> interface. At the protocol.js level:
>
> * there is no longer a c.labels dictionary;
> * there is a new c.label field;
> * there is no longer a c.kind field, since c.label subsumes it;
> * the syntax of the sc.request method has changed.
>
> I've added a new sc.users dictionary, that contains some information about
> all the users in the group:
>
> - username;
> - permissions (op, etc.);
> - status (raised hand, etc.);
> - published streams.
>
> Alain is planning to use this information in order to make the users' list
> more informative.
>
> I've also switched to a more recent API (addTransceiver instead of
> addTrack); however, this should not break anything on reasonably recent
> browsers.
>
> -- Juliusz
>
>
>
>
>
>
> _______________________________________________
> Galene mailing list -- galene@lists.galene.org
> To unsubscribe send an email to galene-leave@lists.galene.org
[-- Attachment #2: Type: text/html, Size: 6387 bytes --]
next prev parent reply other threads:[~2021-05-01 7:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 17:12 [Galene] Protocol changes Juliusz Chroboczek
2021-05-01 7:49 ` Fabrice Rouillier [this message]
2021-05-01 10:23 ` [Galene] Re: Galene + Firefox & Nat Juliusz Chroboczek
2021-05-01 11:16 ` Fabrice Rouillier
2021-05-01 11:46 ` Michael Ströder
2021-05-01 11:49 ` Fabrice Rouillier
2021-05-01 12:33 ` Juliusz Chroboczek
2021-05-01 13:10 ` Fabrice Rouillier
2021-05-01 15:10 ` Juliusz Chroboczek
2021-05-01 15:15 ` Michael Ströder
2021-05-01 16:09 ` Juliusz Chroboczek
2021-05-01 15:50 ` Fabrice Rouillier
2021-05-01 14:25 ` 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=9A91101D-D607-45A0-846D-6CC9A58DE525@rouillier.fr \
--to=fabrice@rouillier.fr \
--cc=galene@lists.galene.org \
/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