You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 12, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Jul 12, 2023. It is now read-only.
externalIpv4 and externalIpv6 affect all candidates instead of just host #622
The addition of externalIpv4 and externalIpv6 to replace externalAddress lost the detail of affecting only the local candidates of type host. Using any of the newer parameters will change the address of ALL candidates, while using externalAddress would apply the given address only to host ones. So I guess this is a regression in behavior.
See screenshot, where externalIpv4 was set to 1.2.3.4:
Context
A Kurento server with externalIpv4 or externalIpv6 setting active, and also using a STUN or TURN server to retrieve srflx and relay candidates.
Hello @j1elo! 👋 we're sorry you found a bug... so first of all, thank you very much for reporting it.
To know about progress, check in Triage. All issues are considered Backlog Candidates until work priorities align and the issue is selected for development. It will then become part of our official Backlog.
Activity
github-actions commentedon Apr 8, 2022
Hello @j1elo! 👋 we're sorry you found a bug... so first of all, thank you very much for reporting it.
To know about progress, check in Triage. All issues are considered Backlog Candidates until work priorities align and the issue is selected for development. It will then become part of our official Backlog.