| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Differential Revision: https://phabricator.freedesktop.org/D1107
|
| |
|
|
| |
Add stun/usages/.dirstamp.
|
| |
|
|
|
|
|
|
|
| |
We’ve neglected to manually update this file once too often — it’s been
out of date for important new symbols (for example,
nice_agent_get_io_stream()) since at least 0.1.11.
Since the format is a simple extension of libnice.sym, we might as well
automatically generate it at dist time.
|
| | |
|
| |
|
|
|
|
|
|
| |
This explicitly removes all timers and main loop considerations from the
pseudo-TCP testing, which considerably simplifies arranging packet swaps
and mistimings for testing purposes.
This test suite includes a few tests for the FIN–ACK support.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This bumps our autoconf requirement to 2.62 (from 2.59c) and disables
automake portability warnings.
It does not introduce a hard dependency on gobject-introspection; but if
available, it requires version 1.30.0. Support can be enabled with
--enable-introspection, and is required to make distcheck.
The generated introspection file has not been checked thoroughly, and
may expose internal symbols. A lot of new annotations are needed to make
many of the symbols usable.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a massive commit that can't be split. We add ice-tcp support
into the agent by creating local host tcp-active/tcp-passive candidates.
We also need to find the local and remote candidates whenever we discover
a peer-reflexive because their data is important to setup the peer-reflexive
so a few changes were added to look for the local or remote candidate.
For TCP-ACTIVE remote peer-reflexive candidates, we can't add conncheck
pairs normally because TCP-PASSIVE (local) do not generate candidate pairs,
and we also can't have a connection from any local host, so we can only create
a single candidatepair with the local/remote that are connected.
The pair->socket of a candidate check pair will hold the connected tcp socket
(through connect for ACT or accept for PASS) and we will either have a
remote or a local peer-reflexive which will create a new candidate pair,
we cannot trigger checks on the initial candidate pair, we must only do it
on the new check pairs. but in the case of a tcp-passive, we don't get a new
local peer-reflexive candidate, so there is no new candidate with a new NiceSocket, so
when we get a triggered check, we need to match it to the candidate check pair
or when we select a pair, it will still use the original TCP-PASS socket.
We must store the new connected tcp socket in the peer reflexive candidates
since they represent that unique peer-reflx candidate's connection
|
| | |
|
| |
|
|
|
|
|
|
|
| |
As documented at the top of the file, this creates two PseudoTcpSockets
in a loopback configuration, and mutates the raw packets which are sent
between them, hoping to cause assertion failures and illegal memory
accesses in the pseudotcp code.
Best run under Valgrind or GDB.
|
| | |
|
| |
|
|
|
| |
We wan't to make sure not to have a race where a thread blocks in a blocking
receive or send while nice_agent_remove_stream() is called
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
It gets automatically generated by autotools, so just gets in the way if
checked into git.
|
| |
|
|
| |
Older compilers don't understand all of the flags
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
