Streaming won't start when offline (server on local network)

[rija1]

I've set up the solution on a local network that may be disconnected from the internet at times.

When offline, the "iceConnectionState" never becomes "connected" but remains at the "new" stage.
When online, it works fine and the audio stream plays without issues.

I am wondering why WebRTC seems to require an internet connection when both the client and server are running locally.

Any ideas or workaround to avoid this?

Thank you

[JoJoBond]

Can you describe your setup?
I personally have 3LAS running in a wifi network without Internet and it works just fine.

[rija1]

Oh right it must come from my setup then indeed. It stops working as soon as I turn off the wifi in my case.

I am using these settings :
"RtcConfig": null,
"FallbackFFmpegPath": "/usr/local/bin/ffmpeg",
"FallbackUseMp3": true,
"FallbackUseWav": true,
"FallbackMp3Bitrate": 128,
"FallbackWavSampleRate": 16000,

The server and client nodes both run on my mac on ports 3000 and 3001.
I see the same issue with both Google Chrome and Firefox.

Also I modified the script to include four players on the same page (four language channels) so it may come from this. However it works perfectly fine as soon as I am connected to the internet that's why it keeps me wondering (but I can't see anything trying to connect to the internet in my developer tools' Network tab).

[JoJoBond]

Can you reduce your setup to a single player for now?
Since I never tested running the server on MacOS, there is a possibility that this is some kind of Apple shenanigan.
So, if possible, could you try running it in a true Linux environment? A VM would probably do just fine for testing.

[rija1]

I just tried it on Ubuntu and got the same thing going, the streaming stops as soon as I turn off the Wifi. I actually only have one player but 4 buttons to initialise the player with a different web socket, I will try to run the original version of your code when I will have time. Thank you for your support anyways, this is much appreciated.

…

On 15 Apr 2023, at 01:06, JoJoBond ***@***.***> wrote: Can you reduce your setup to a single player for now? Since I never tested running the server on MacOS, there is a possibility that this is some kind of Apple shenanigan. So, if possible, could you try running it in a true Linux environment? A VM would probably do just fine for testing. — Reply to this email directly, view it on GitHub <#26 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMNSLEMDDACDDYDPKP5BK3XBGPTRANCNFSM6AAAAAAW6MNXZE>. You are receiving this because you authored the thread.

[rija1]

I just tested this again with a fresh install of the project and get the same results.
So it seems that it is not related to the OS nor to the customisations I've made.

@JoJoBond can you definitely launch a stream when your wifi is totally off and the ethernet cable unplugged ?

One thing I didn't mention is that the event log doesn't show any error, it just won't start playing :

[20:22:50] Init of WebSocketClient succeeded
[20:22:50] Trying to connect to server.
[20:22:50] Established connection with server.

[JoJoBond]

@JoJoBond can you definitely launch a stream when your wifi is totally off and the ethernet cable unplugged ?

I tested following scenarios:

Local test with 127.0.0.1 IP. Ethernet with internet is connected.
Ethernet that is connected to a Wifi AP with 192.168.0.X/24 IP. No internet connection.

Both do work.

[rija1]

OK, I will have to dive deeper in the webRTC connection process to find where is the issue. Thanks anyways. Le sam. 15 avr. 2023, 20:44, JoJoBond ***@***.***> a écrit :

…

@JoJoBond <https://github.com/JoJoBond> can you definitely launch a stream when your wifi is totally off and the ethernet cable unplugged ? I tested following scenarios: Local test with 127.0.0.1 IP. Ethernet with internet is connected. Ethernet that is connected to a Wifi AP with 192.168.0.X/24 IP. No internet connection. Both do work. — Reply to this email directly, view it on GitHub <#26 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMNSLGN5I3JC5ETYCETLCLXBKZVLANCNFSM6AAAAAAW6MNXZE> . You are receiving this because you authored the thread.Message ID: ***@***.***>