|Submitter||Diff||Changes||Open Issues||Last Updated|
|Error loading review requests:|
40 bytes, text/x-review-board-request
|Details | Review|
It looks like the idea of only creating a socket entry in nICEr for TCP active sockets, without a real network socket being created (they get created once a connection attempt from the active socket to a given target is started) is a bad idea as we don't know if the port number is actually available. Here is how I think we should do it instead: - at gathering internally allocate TCP active socket with port number 9 - I don't think that multiple sockets on port 9 should be duped, but double check - at the time of requesting a connection from an active socket to a destination, then allocate a socket with an ephemeral port number (with the n-try loop like we do it at gathering time for passive and so sockets)
Created attachment 8649576 [details] MozReview Request: Bug 1195396: create ephemeral sockets for TCP active on connect only Bug 1195396: create ephemeral sockets for TCP active on connect only
Mass change P2->P3 to align with new Mozilla triage process.