aioice
aioice copied to clipboard
asyncio-based Interactive Connectivity Establishment (RFC 5245)
Tested on version 0.7.6. If multiple checks from a remote peer arrive before __check_list_ from _Connection_ class is set, then all of them are appended to the __early_checks_ list and...
In my setup I have a WebRTC data channel that I use to transfer relatively big data packages of ~30 MB. I observed connection closings when running the code on...
The following will ignore all docker interfaces when gathering candidates ``` ice.get_host_addresses(block_list=["docker*"]) ``` The following will only allow ethernet interfaces when gathering candidates ``` ice.get_host_addresses(block_list=["eth*"]) ```
Currently aioice: - emits all local ICE candidates in one go - expects remote ICE candidates to be provided in one go Adding ICE trickle support is highly desirable, but:...
RFC 8445
According to the readme, aioice is based on RFC 5245. There is now RFC 8445 that obsoletes RFC 5245: https://datatracker.ietf.org/doc/html/rfc8445#section-21 I am not very familiar with the codebase of aioice...
Hi! Inside `get_component_candidates` under the `Connection` class, the local UDP ports are randomly selected by the kernel, since 0 is provided as the port to `create_datagram_endpoint`. I have a use-case...
while test i saw when check_periodic run check_start while prevision paring still in progress this can produce incorrect nomination fix like this ``` def check_periodic(self) -> bool: + for pair...
Hi, we have a setup where sometimes a STUN server needs to be used (in a company network) and sometimes a TURN server needs to be used (e.g. mobile Hotspot),...
there are any plain to support multiple stun and turn servers or any easy way to archive this? thanks