mirror of https://github.com/outbackdingo/firezone.git synced 2026-01-28 10:18:51 +00:00

Files

Thomas Eizinger 66c85e28b0 feat(connection): use STUN to generate server-reflexive candidate (#3268 )

Currently, `firezone-connection` can only handle connections on a LAN.
Via the use of a STUN server, we can discover our public IP and attempt
to direct, hole-punched connection across multiple subnets.

2024-01-19 04:11:07 +00:00

router

feat(connection): use STUN to generate server-reflexive candidate (#3268 )

2024-01-19 04:11:07 +00:00

src

feat(connection): use STUN to generate server-reflexive candidate (#3268 )

2024-01-19 04:11:07 +00:00

Cargo.toml

build(deps): Bump redis from 0.23.3 to 0.24.0 in /rust (#2864 )

2024-01-17 03:37:38 +00:00

docker-compose.lan.yml

feat: dynamically configure network & redis for LAN integration test (#3286 )

2024-01-17 22:11:29 +00:00

docker-compose.wan.yml

feat(connection): use STUN to generate server-reflexive candidate (#3268 )

2024-01-19 04:11:07 +00:00

README.md

feat: introduce firezone-connection with basic test suite (#2965 )

2023-12-23 00:45:43 +00:00

README.md

firezone-connection integration tests

This directory contains Docker-based integration tests for the firezone-connection crate. Each integration test setup is a dedicated docker-compose file.

Running

To run one of these tests, use the following command:

sudo docker compose -f ./docker-compose.lan.yml up --exit-code-from dialer --abort-on-container-exit --build

This will force a re-build of the containers and exit with 0 if everything works correctly.

Design

Each file consists of at least:

A dialer
A listener
A redis server

Redis acts as the signalling channel. Dialer and listener use it to exchange offers & answers as well as ICE candidates.

The various files simulate different network environments. We use nftables to simulate NATs and / or force the use of TURN servers.