Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
* [Galene] Protocol changes
@ 2021-04-29 17:12 Juliusz Chroboczek
  2021-05-01  7:49 ` [Galene] Galene + Firefox & Nat Fabrice Rouillier
  0 siblings, 1 reply; 13+ messages in thread
From: Juliusz Chroboczek @ 2021-04-29 17:12 UTC (permalink / raw)
  To: galene

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







^ permalink raw reply	[flat|nested] 13+ messages in thread

* [Galene] Galene + Firefox & Nat
  2021-04-29 17:12 [Galene] Protocol changes Juliusz Chroboczek
@ 2021-05-01  7:49 ` Fabrice Rouillier
  2021-05-01 10:23   ` [Galene] " Juliusz Chroboczek
  0 siblings, 1 reply; 13+ messages in thread
From: Fabrice Rouillier @ 2021-05-01  7:49 UTC (permalink / raw)
  To: galene

[-- 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 --]

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [Galene] Re: Galene + Firefox & Nat
  2021-05-01  7:49 ` [Galene] Galene + Firefox & Nat Fabrice Rouillier
@ 2021-05-01 10:23   ` Juliusz Chroboczek
  2021-05-01 11:16     ` Fabrice Rouillier
  0 siblings, 1 reply; 13+ messages in thread
From: Juliusz Chroboczek @ 2021-05-01 10:23 UTC (permalink / raw)
  To: Fabrice Rouillier; +Cc: galene

> 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

Please check whether the relay test has been successful in Galène's logs.
If it was not, then you didn't set up hairpinning correctly in your NAT.

If you're unable to get hairpinning to work, the suggested solution is to
use a TURN server that's not behind NAT, or at the very least a STUN
server.  You won't find any free TURN servers, but you will find a number
of reliable free STUN servers.

-- Juliusz

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [Galene] Re: Galene + Firefox & Nat
  2021-05-01 10:23   ` [Galene] " Juliusz Chroboczek
@ 2021-05-01 11:16     ` Fabrice Rouillier
  2021-05-01 11:46       ` Michael Ströder
  2021-05-01 12:33       ` Juliusz Chroboczek
  0 siblings, 2 replies; 13+ messages in thread
From: Fabrice Rouillier @ 2021-05-01 11:16 UTC (permalink / raw)
  To: Juliusz Chroboczek; +Cc: galene

There is a problem uniquely with firefox m, it works with all other clients on same conditions.

Enabling/disabling ipv6 using several kinds of networks give the same result.

Fabrice
Envoyé avec un smartphone

> Le 1 mai 2021 à 12:23, Juliusz Chroboczek <jch@irif.fr> a écrit :
> 
> 
>> 
>> 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
> 
> Please check whether the relay test has been successful in Galène's logs.
> If it was not, then you didn't set up hairpinning correctly in your NAT.
> 
> If you're unable to get hairpinning to work, the suggested solution is to
> use a TURN server that's not behind NAT, or at the very least a STUN
> server.  You won't find any free TURN servers, but you will find a number
> of reliable free STUN servers.
> 
> -- Juliusz

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [Galene] Re: Galene + Firefox & Nat
  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
  1 sibling, 1 reply; 13+ messages in thread
From: Michael Ströder @ 2021-05-01 11:46 UTC (permalink / raw)
  To: galene

On 5/1/21 1:16 PM, Fabrice Rouillier wrote:
> There is a problem uniquely with firefox m, it works with all other
> clients on same conditions.
Older versions of Firefox had WebRTC issues, most times with Jitsi.
Could you please mention exact version you're testing with?

Personally I'm using Galène + Firefox combo all the time without problems.

Ciao, Michael.

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [Galene] Re: Galene + Firefox & Nat
  2021-05-01 11:46       ` Michael Ströder
@ 2021-05-01 11:49         ` Fabrice Rouillier
  0 siblings, 0 replies; 13+ messages in thread
From: Fabrice Rouillier @ 2021-05-01 11:49 UTC (permalink / raw)
  To: Michael Ströder; +Cc: galene

Be carefull, the installation of Galene used is special (see my first mail). Firefox last version is not working (on ipv4 network)

Fabrice

Envoyé avec un smartphone

> Le 1 mai 2021 à 13:46, Michael Ströder <michael@stroeder.com> a écrit :
> 
> On 5/1/21 1:16 PM, Fabrice Rouillier wrote:
>> There is a problem uniquely with firefox m, it works with all other
>> clients on same conditions.
> Older versions of Firefox had WebRTC issues, most times with Jitsi.
> Could you please mention exact version you're testing with?
> 
> Personally I'm using Galène + Firefox combo all the time without problems.
> 
> Ciao, Michael.
> _______________________________________________
> Galene mailing list -- galene@lists.galene.org
> To unsubscribe send an email to galene-leave@lists.galene.org

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [Galene] Re: Galene + Firefox & Nat
  2021-05-01 11:16     ` Fabrice Rouillier
  2021-05-01 11:46       ` Michael Ströder
@ 2021-05-01 12:33       ` Juliusz Chroboczek
  2021-05-01 13:10         ` Fabrice Rouillier
  2021-05-01 14:25         ` Fabrice Rouillier
  1 sibling, 2 replies; 13+ messages in thread
From: Juliusz Chroboczek @ 2021-05-01 12:33 UTC (permalink / raw)
  To: Fabrice Rouillier; +Cc: galene

> There is a problem uniquely with firefox m, it works with all other
> clients on same conditions.

Firefox has a different implementation of ICE than Chrome, so if your
configuration is incomplete, it's not impossible for one browser to
succeed and the other to fail.

What does Galène say about the relay test in the log?

-- Juliusz

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [Galene] Re: Galene + Firefox & Nat
  2021-05-01 12:33       ` Juliusz Chroboczek
@ 2021-05-01 13:10         ` Fabrice Rouillier
  2021-05-01 15:10           ` Juliusz Chroboczek
  2021-05-01 14:25         ` Fabrice Rouillier
  1 sibling, 1 reply; 13+ messages in thread
From: Fabrice Rouillier @ 2021-05-01 13:10 UTC (permalink / raw)
  To: Juliusz Chroboczek; +Cc: galene

[-- Attachment #1: Type: text/plain, Size: 650 bytes --]


> Firefox has a different implementation of ICE than Chrome, so if your
> configuration is incomplete, it's not impossible for one browser to
> succeed and the other to fail.
> 

In the present case, It is the contrary : all browsers succeed but firefox on some networks (mainly 4G SFR)

> What does Galène say about the relay test in the log?

I did try to reproduce using firefox on my IPAD with a 4G , I first got 

"pc ERROR: 2021/05/01 15:02:05 Incoming unhandled RTP ssrc(279383751), OnTrack will not be fired. mid RTP Extensions required for Simulcast »

But the second try did work. Strange.

Cheers,

Fabrice.


 


[-- Attachment #2: Type: text/html, Size: 2338 bytes --]

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [Galene] Re: Galene + Firefox & Nat
  2021-05-01 12:33       ` Juliusz Chroboczek
  2021-05-01 13:10         ` Fabrice Rouillier
@ 2021-05-01 14:25         ` Fabrice Rouillier
  1 sibling, 0 replies; 13+ messages in thread
From: Fabrice Rouillier @ 2021-05-01 14:25 UTC (permalink / raw)
  To: Juliusz Chroboczek; +Cc: galene

[-- Attachment #1: Type: text/plain, Size: 189 bytes --]


> What does Galène say about the relay test in the log?
> 
Nothing bad :

2021/05/01 15:01:05 Relay test successful in 98.857478ms, RTT = 1.135147ms


Fabrice.

> -- Juliusz


[-- Attachment #2: Type: text/html, Size: 1221 bytes --]

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [Galene] Re: Galene + Firefox & Nat
  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 15:50             ` Fabrice Rouillier
  0 siblings, 2 replies; 13+ messages in thread
From: Juliusz Chroboczek @ 2021-05-01 15:10 UTC (permalink / raw)
  To: Fabrice Rouillier; +Cc: galene

> 2021/05/01 15:01:05 Relay test successful in 98.857478ms, RTT = 1.135147ms

Excellent.

> In the present case, It is the contrary : all browsers succeed but firefox on
> some networks (mainly 4G SFR)

SFR uses a CGNAT (the provider NATs your traffic), so you're running
behind two layers of NAT in that case, one of which you don't control.
That's a configuration that's nearly impossible to debug, but we can try.

If you manage to reproduce the failure, could you please go to
about:firefox-internals in Firefox and tell us what the candidate list
looks like?

> "pc ERROR: 2021/05/01 15:02:05 Incoming unhandled RTP ssrc(279383751), OnTrack
> will not be fired. mid RTP Extensions required for Simulcast »

That's really weird -- it means that Galene received a packet that it
wasn't expecting.  I have no clue how that could have happened.

-- Juliusz

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [Galene] Re: Galene + Firefox & Nat
  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
  1 sibling, 1 reply; 13+ messages in thread
From: Michael Ströder @ 2021-05-01 15:15 UTC (permalink / raw)
  To: galene

On 5/1/21 5:10 PM, Juliusz Chroboczek wrote:
> If you manage to reproduce the failure, could you please go to
> about:firefox-internals in Firefox

Did you mean the internal link about:webrtc ?

Ciao, Michael.

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [Galene] Re: Galene + Firefox & Nat
  2021-05-01 15:10           ` Juliusz Chroboczek
  2021-05-01 15:15             ` Michael Ströder
@ 2021-05-01 15:50             ` Fabrice Rouillier
  1 sibling, 0 replies; 13+ messages in thread
From: Fabrice Rouillier @ 2021-05-01 15:50 UTC (permalink / raw)
  To: Juliusz Chroboczek; +Cc: galene

Ok next next time a colleague has an sfr connexion and Firefox, I will ask for details. 

Fabrice

> Le 1 mai 2021 à 17:10, Juliusz Chroboczek <jch@irif.fr> a écrit :
> 
> 
>> 
>> 2021/05/01 15:01:05 Relay test successful in 98.857478ms, RTT = 1.135147ms
> 
> Excellent.
> 
>> In the present case, It is the contrary : all browsers succeed but firefox on
>> some networks (mainly 4G SFR)
> 
> SFR uses a CGNAT (the provider NATs your traffic), so you're running
> behind two layers of NAT in that case, one of which you don't control.
> That's a configuration that's nearly impossible to debug, but we can try.
> 
> If you manage to reproduce the failure, could you please go to
> about:firefox-internals in Firefox and tell us what the candidate list
> looks like?
> 
>> "pc ERROR: 2021/05/01 15:02:05 Incoming unhandled RTP ssrc(279383751), OnTrack
>> will not be fired. mid RTP Extensions required for Simulcast »
> 
> That's really weird -- it means that Galene received a packet that it
> wasn't expecting.  I have no clue how that could have happened.
> 
> -- Juliusz

^ permalink raw reply	[flat|nested] 13+ messages in thread

* [Galene] Re: Galene + Firefox & Nat
  2021-05-01 15:15             ` Michael Ströder
@ 2021-05-01 16:09               ` Juliusz Chroboczek
  0 siblings, 0 replies; 13+ messages in thread
From: Juliusz Chroboczek @ 2021-05-01 16:09 UTC (permalink / raw)
  To: Michael Ströder; +Cc: galene

>> If you manage to reproduce the failure, could you please go to
>> about:firefox-internals in Firefox

> Did you mean the internal link about:webrtc ?

Yes, sorry.

^ permalink raw reply	[flat|nested] 13+ messages in thread

end of thread, other threads:[~2021-05-01 16:09 UTC | newest]

Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-04-29 17:12 [Galene] Protocol changes Juliusz Chroboczek
2021-05-01  7:49 ` [Galene] Galene + Firefox & Nat Fabrice Rouillier
2021-05-01 10:23   ` [Galene] " 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

Galène videoconferencing server discussion list archives

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://lists.galene.org/galene

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 galene galene/ https://lists.galene.org/galene \
		galene@lists.galene.org
	public-inbox-index galene

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git