| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
This fixes compilation on e.g. macOS and FreeBSD, where it is missing.
|
| |
|
| |
|
|
|
|
| |
Setting it as a int makes meson abort.
|
| |
|
|
|
|
| |
The meson build already required 1.x so this has been dead code for a while now.
|
|
|
|
| |
It was already set at creation time, so all we got was a warning.
|
|
|
|
|
|
| |
nice_address_to_string expects an already-allocated string, which is not
great for introspection. Adds nice_address_to_string_dup, which does the
same thing, but returns a newly allocated string.
|
| |
|
|
|
|
| |
Even if the TCP candidates are disabled.
|
|
|
|
|
| |
This should enable having servers that do both IPv4 and IPv6. And
ideally should make life easier for app developers.
|
|
|
|
|
| |
This should enable having servers that do both IPv4 and IPv6. And
ideally should make life easier for app developers.
|
|
|
|
|
| |
The checks were reversed, requiring for instance a non-relay candidate
for calling nice_candidate_relay_address()
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This is useful for accurately testing code coverage. You can use this with:
meson configure -Db_coverage=true
meson test
ninja coverage
|
| |
|
| |
|
|
|
|
|
|
| |
Limit the number of stored incoming checks based on the property
limiting the number of total connectivity checks instead of using
the fixed limit on the number of remote candidates.
|
| |
|
|
|
|
|
|
|
| |
This will find some interface that has the address and will not work
correctly if multiple interfaces have the same address. But in any
case, nothing in libnice expects that and we would need to break the
API to make that work.
|
|
|
|
|
|
| |
Bug reported and fix suggested by Masato Takahashi
Fixes #164
|
| |
|
|
|
|
| |
This should make the library more easily usable for bindings
|
|
|
|
|
|
| |
One use case for this is adding an ALPN header which is a MUST
requirement when a HTTP proxy is used in WebRTC (see RFC8835, section
3.4).
|
|
|
|
| |
inbound STUN with NOMINATION attr
|
|
|
|
| |
keepalive
|
|
|
|
|
|
|
|
| |
0.1.18.1 should not satisfy a check for 0.1.19, especially not
for libraries that release once a year at best.
If someone needs more control they should do a feature check for
the symbol in the headers or lib.
|
|
|
|
|
|
|
| |
Install a nice-version.h so that the version defines
are available.
https://gitlab.freedesktop.org/libnice/libnice/-/merge_requests/232
|
| |
|
|
|
|
| |
Can be useful to know which STUN server was used to discover the given candidate.
|
| |
|
| |
|
|
|
|
|
| |
There is a codepath where it can be used without being filled.
Found by coverity.
|
| |
|
| |
|
|
|
|
| |
Can be useful to know which TURN server is being used as relay server for a given candidate.
|
|
|
|
|
|
|
|
|
|
| |
It's possible that the callback will be called synchronously during the
close function, in this case, we need to be ready to the last reference
to the agent to be dropped in this callback.
This fix was suggested by Fabrice Bellet
Fixes #153
|
|
|
|
|
|
|
|
|
|
| |
If we have gathered a host IP-address that is link-local we should
never try to use it for anything else than trying to match it with
another link-local address. Some routers seem to have problems with
traffic from link-local addresses destined at external IP-addresses.
By definition link-local addresses should stay local so there's no
reason to access STUN/TURN from it or try to form a candidate with
another address that is not link-local.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
../agent/discovery.c: In function ‘on_refresh_remove_timeout’:
../agent/discovery.c:203:13: warning: Not available before 2.60
203 | G_GNUC_FALLTHROUGH;
| ^~~~~~~~~~~~~
../agent/conncheck.c: In function ‘priv_turn_allocate_refresh_retransmissions_tick_agent_locked’:
../agent/conncheck.c:1656:13: warning: Not available before 2.60
1656 | G_GNUC_FALLTHROUGH;
| ^~~~~~~~~~~~~
The comment /* fall through */ is enough to cause GCC and Clang to not
emit the implicit-fallthrough warning.
|
|
|
|
| |
This was probably added by mistake.
|
|
|
|
| |
This should fix builds on platforms openssl
|
| |
|
|
|
|
| |
Fixes issue found by Coverity
|
|
|
|
|
| |
In one case, the message pointer gets replaced by the rfc4571_message
one, so it wasn't getting cleared as expected.
|
|
|
|
|
|
|
| |
It's very tricky and unintuitive to have webrtcbin not sending data
because of the segment.
Fix https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/907
|
|
|
|
|
|
|
| |
Busy-looping is not a good idea, especially not when run under Valgrind,
where such a thread may result in well-behaved threads running thousands
of times slower. While passing --fair-sched=yes to Valgrind avoids the
issue, it's still better to make our busy-looping less aggressive.
|