The WebRTC specification has RTCIceTransports=relay, which means that all communications MUST go through a relay.
(In reply to comment #0) > The WebRTC specification has RTCIceTransports=relay, which means that all > communications MUST go through a relay. In that case, you can just not send any non-relay candidates to the peer and not set any remote non-relay candidates. I don't see a reason to add an API just for such a special use case.
The problem is that even if we do that, once libnice receives a packet through a relay, it "discovers" the address of the other side and tries to establish a direct connection.
(In reply to comment #2) > The problem is that even if we do that, once libnice receives a packet > through a relay, it "discovers" the address of the other side and tries to > establish a direct connection. You're right, I forgot about peer-reflexive candidates. I guess those can be easily disabled with a property, but I'd still go with just using the nice_agent_set_selected_pair to force it to use the relay.
You could have multiple relays, etc.
Migrated to Phabricator: http://phabricator.freedesktop.org/T101
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.