157e76f8a1
AndroidNetworkMonitor::BindSocketToNetwork incorrectly checks if the socket_fd is NETWORK_UNSPECIFIED, when it should instead be checking if the network_handle is that. This causes the PhysicalSocket to think that it has succesfully bound to the port, when it really has not. This stops IceCandidates from being created for these addresses (although a socket is listening). The net result of this is that webrtc connections don't work when both peers are using Wifi-Direct to communicate, although we didn't notice this previously since we were using Wifi-Direct only on one side. TBR=pthatcher@webrtc.org Bug: webrtc:8403 Change-Id: Ibe8f5424654ac9db1f79927ba7ac241fd40d9cba Reviewed-on: https://webrtc-review.googlesource.com/12442 Commit-Queue: Taylor Brandstetter <deadbeef@webrtc.org> Reviewed-by: Taylor Brandstetter <deadbeef@webrtc.org> Cr-Commit-Position: refs/heads/master@{#20331}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
Development
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: http://build.chromium.org/p/client.webrtc
- Coding style guide
- Code of conduct