577ce43942
This PR should fix the way we handle the `length` field in the `DataChannel` messages, previous to this fix relaying data (using the `webrtc-rs` crate) was impossible) The new way to handle this is if the actual message is bigger than what this data field says we ignore the extra bytes (which I think is the correct way to do it according to spec) Also, I added an integration test to verify relay messages using `iptables`, not the cleanest way to do it but the easiest, in this vein I tried to fix the caching for rust containers since 2 integration test in our current state would take ~20 minutes each.
relay
This crate houses a minimalistic STUN & TURN server.
Features
We aim to support the following feature set:
- STUN binding requests
- TURN allocate requests
- TURN refresh requests
- TURN channel bind requests
- TURN channel data requests
Relaying of data through other means such as DATA frames is not supported.
Building
You can build the server using: cargo build --release --bin relay
Running
For an up-to-date documentation on the available configurations options and a detailed help text, run cargo run --bin relay -- --help.
All command-line options can be overridden using environment variables.
Those variables are listed in the --help output at the bottom of each command.
The relay listens on port 3478.
This is the standard port for STUN/TURN and not configurable.
Additionally, the relay needs to have access to the port range 49152 - 65535 for the allocations.
Portal connection
When given a portal endpoint, the relay will connect to it and wait for an init message before commencing relay operations.
Design
The relay is designed in a sans-IO fashion, meaning the core components do not cause side effects but operate as pure, synchronous state machines. They take in data and emit commands: wake me at this point in time, send these bytes to this peer, etc.
This allows us to very easily unit-test all kinds of scenarios because all inputs are simple values.
The main server runs in a single task and spawns one additional task for each allocation. Incoming data that needs to be relayed is forwarded to the main task where it gets authenticated and relayed on success.