Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hack to make sure we pass candidates in libnice even when there's only mdns #1766

Merged
merged 1 commit into from
Nov 10, 2021

Conversation

lodoyun
Copy link
Contributor

@lodoyun lodoyun commented Nov 8, 2021

Description

This PR introduces a hack to fix this issue until we can use an updated version of libnice with this fix.
In short, when connecting with Chrome and libnice with ice-lite there's a change we're not passing any remote candidates to libnice because they are mdns candidates and they are not valid. Instead of resolving those candidates (which may not always work), this hack just passes a "dummy" candidate to get libnice to progress to the next state.

[] It needs and includes Unit Tests

Changes in Client or Server public APIs

[] It includes documentation for these changes in /doc.

@lodoyun lodoyun changed the title Hack to avoid not passing candidates in libnice Hack to avoid make sure we pass candidates in libnice even when there's only mdns Nov 8, 2021
Copy link
Contributor

@jcague jcague left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, it would be interesting to have reminders in GitHub to review hacks in the future

@lodoyun lodoyun merged commit 9fff095 into lynckia:master Nov 10, 2021
@lodoyun lodoyun deleted the fix/libniceStuckWithNoCandidates branch November 10, 2021 08:31
@lodoyun lodoyun changed the title Hack to avoid make sure we pass candidates in libnice even when there's only mdns Hack to make sure we pass candidates in libnice even when there's only mdns Nov 10, 2021
@ranthwar-vcx
Copy link

@lodoyun This fix is working only for chrome and Edge....FF and safari is breaking with this changes....Can you suggest us any alternative fix for safari and FF....

@lodoyun
Copy link
Contributor Author

lodoyun commented Feb 2, 2022

This is a problem specific to using libnice and, I've only been able to reproduce it with ice-lite.
How are you reproducing this? This is a pretty rare issue since, I've only seen it happen when both Licode and the browser are in AWS.
If that's your issue, disabling ice-lite (config.erizo.iceLite = false) or using nicer (config.erizo.useNicer = true) will fix it.
Let me know if that works for you

@ranthwar-vcx
Copy link

Thanks for the reply.

We are using latest libNice module along with Trickle set to True..We are using Normal desktop browsers for FF,Safari.

Thanks..Will try those with that options...

Will there be any other issues/side affects if i turned above flags..??

Regards
Ram

@lodoyun
Copy link
Contributor Author

lodoyun commented Feb 2, 2022

Using ice-lite and libnice helps with an issue that we detected that could cause users to go through TURN unnecessarily. Wether you ever experience that issue depends on your Licode deployment (particularly where your TURN servers are), you may not run into it at all. Other than that, I'm not aware of any other issue with libnice when iceLite is turned off.
Nicer may be a bit riskier long-term since we're focusing on libnice now and don't plan to actively update Nicer in the future.

@ranthwar-vcx
Copy link

Thanks @lodoyun .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants