summaryrefslogtreecommitdiffhomepage
path: root/mullvad-relay-selector/src/error.rs
AgeCommit message (Collapse)AuthorFilesLines
2025-10-22Add entry and exit no relay errorsJonatan Rhodin1-0/+6
The old no relay error is still kept for single hop
2025-09-10Add offending query to relay select errSebastian Holmin1-3/+3
2025-04-09Improve error message when an unavailable ip version is selectedJonatan Rhodin1-4/+4
2025-03-25Avoid using an unavailable ip version to connect to a relayJonatan Rhodin1-0/+3
Co-authored-by: Sebastian Holmin <sebastian.holmin@mullvad.net>
2024-10-18Run nightly formatterMarkus Pettersson1-2/+1
2024-10-18Introduce `Singlehop` and `Multihop` as distinct typesMarkus Pettersson1-1/+2
2024-08-28Filter out OpenVPN relays when a core privacy feature is enabledDavid Lönnhager1-0/+3
Core privacy features currently include PQ, multihop, and DAITA
2024-08-16Propagate inner obfuscation errorDavid Lönnhager1-1/+1
2024-06-24Run `cargo +nightly fmt`Sebastian Holmin1-1/+2
2024-03-27Refactor `mullvad-relay-selector`Markus Pettersson1-0/+66
Implement a system built on 'queries' for selecting appropriate relays. A query is a set of constraints which dictates which relay(s) that *can* be chosen by the relay selector. The user's settings can naturally be expressed as a query. The semantics of merging two queries in a way that always prefer user settings is defined by the new `Intersection` trait. Split `mullvad-relay-selector` into several modules: - `query.rs`: Definition of a query on different types of relays. This module is integral to the new API of `mullvad-relay-selector` - `matcher.rs`: Logic for filtering out candidate relays based on a query. - `detailer.rs`: Logic for deriving connection details for the selected relay. - `tests/`: Integration tests for the new relay selector. These tests only use the public APIs of `RelaySelector` and make sure that the output matches the expected output in different scenarios.