Thomas Eizinger 3f3ea96ca7 test(connlib): generate resources with wildcard and ? addresses (#5209) ...

Currently, `tunnel_test` only tests DNS resources with fully-qualified
domain names. Firezone also supports wildcard domains in the forms of
`*.example.com` and `?.example.com`.

To include these in the tests, we generate a bunch of DNS records that
include various subdomains for such wildcard DNS resources.

When sampling DNS queries, we already take them from the pool of global
DNS records which now also includes these subdomains, thus nothing else
needed to be changed to support testing these resources.

2024-06-05 06:54:08 +00:00

..

messages

test(connlib): generate resources with wildcard and ? addresses (#5209)

2024-06-05 06:54:08 +00:00

tun_device_manager

refactor(firezone-tunnel): move routes and DNS control out of connlib and up to the Client (#5111)

2024-06-03 14:32:08 +00:00

callbacks.rs

refactor(firezone-tunnel): move routes and DNS control out of connlib and up to the Client (#5111)

2024-06-03 14:32:08 +00:00

error.rs

test(connlib): simulate IO in state machine tests (#4728)

2024-05-22 23:10:58 +00:00

lib.rs

refactor(firezone-tunnel): move routes and DNS control out of connlib and up to the Client (#5111)

2024-06-03 14:32:08 +00:00

messages.rs

test(connlib): simulate IO in state machine tests (#4728)

2024-05-22 23:10:58 +00:00

proptest.rs

test(connlib): generate resources with wildcard and ? addresses (#5209)

2024-06-05 06:54:08 +00:00

tun_device_manager.rs

refactor(firezone-tunnel): move routes and DNS control out of connlib and up to the Client (#5111)

2024-06-03 14:32:08 +00:00

windows.rs

refactor(firezone-tunnel): move routes and DNS control out of connlib and up to the Client (#5111)

2024-06-03 14:32:08 +00:00