| 0c4e06b4c6107a1b94f764e279e4fb4161e905b0 |
|
07-Oct-2015 |
Peter Boström <pbos@webrtc.org> |
Use suffixed {uint,int}{8,16,32,64}_t types.
Removes the use of uint8, etc. in favor of uint8_t.
BUG=webrtc:5024
R=henrik.lundin@webrtc.org, henrikg@webrtc.org, perkj@webrtc.org, solenberg@webrtc.org, stefan@webrtc.org, tina.legrand@webrtc.org
Review URL: https://codereview.webrtc.org/1362503003 .
Cr-Commit-Position: refs/heads/master@{#10196}
/external/webrtc/webrtc/p2p/stunprober/stunprober_unittest.cc
|
| dc13abc331b8e5ce2bdf99722aba3fdd9c0444ff |
|
18-Jun-2015 |
Guo-wei Shieh <guoweis@chromium.org> |
Initially when the design was to do this experiment in browser, which doesn't have webrtc code, it requires some glue code to bridge the difference between what's available in webrtc::base and browser process. Now since we're moving to renderer process, we could reuse a lot of existing interfaces instead of rolling our own.
BUG=webrtc:4576
R=pthatcher@webrtc.org
Review URL: https://codereview.webrtc.org/1173353002.
Cr-Commit-Position: refs/heads/master@{#9466}
/external/webrtc/webrtc/p2p/stunprober/stunprober_unittest.cc
|
| 72e9f044471078f40999c93823424e4f0e825c21 |
|
09-Jun-2015 |
Guo-wei Shieh <guoweis@chromium.org> |
Better determination of Symmetric NAT.
If we're using shared socket mode, Symmetric NAT can be correctly determined by having more than 1 srflx per Requester (i.e. socket).
Design Doc updated at https://docs.google.com/document/d/11zruojoNqZgZYDrSVk0O3JHqFz2cFldWYQbroZdZRBg/edit#heading=h.t7npdccia97t
BUG=4576
R=pthatcher@webrtc.org
Review URL: https://codereview.webrtc.org/1166013002
Cr-Commit-Position: refs/heads/master@{#9396}
/external/webrtc/webrtc/p2p/stunprober/stunprober_unittest.cc
|
| 1ab67aef80cd1461ad3446aa7f53b82d833352fa |
|
19-May-2015 |
Guo-wei Shieh <guoweis@chromium.org> |
Address the corner cases
1. when an IP is reported by DNS but it doesn't serve any traffic, we shouldn't count failure from that.
2. shared socket mode should should only be true for the case where multiple IPs are resolved and successfully pinged.
3. allow multiple STUN servers now.
Fix a bug in symnat detection. SymNAT will provide the same IP but different port.
If we have more than 1 srflx IP, we'll fail the experiment.
BUG=4576
R=pthatcher@webrtc.org
Review URL: https://webrtc-codereview.appspot.com/51849004
Cr-Commit-Position: refs/heads/master@{#9215}
/external/webrtc/webrtc/p2p/stunprober/stunprober_unittest.cc
|
| 37931c4b851919e55b17ef571118d696317d0aa3 |
|
15-May-2015 |
Guo-wei Shieh <guoweis@chromium.org> |
Stunprober interface, its implementation and a command line driver.
Chrome will only see stunprober.h and stunprobercontext.h and link with libstunprober.a.
It has support for shared and non-shared mode. In shared mode, a socket will be used to ping all resolved IPs once. In non-shared mode, each ping will get a new socket.
The thread scheduling will try to run MaybeScheduleStunRequest every 1 ms. When the time is up for next ping, it'll send it out.
BUG=4576
R=pthatcher@webrtc.org
Review URL: https://webrtc-codereview.appspot.com/51729004
Cr-Commit-Position: refs/heads/master@{#9194}
/external/webrtc/webrtc/p2p/stunprober/stunprober_unittest.cc
|