summaryrefslogtreecommitdiffhomepage
path: root/ios/MullvadVPN/TransportMonitor
AgeCommit message (Collapse)AuthorFilesLines
2025-09-30Apply new swift format rules to codebaseSteffen1-5/+8
# Conflicts: # ios/MullvadVPN/Coordinators/Settings/DAITA/SettingsDAITAView.swift # ios/MullvadVPN/View controllers/DeviceList/DeviceManagementView.swift
2025-05-21Remove dead code and add some more commentsmojganii1-9/+24
2025-03-03Send API requests across app/packet tunnel boundaryJon Petersson2-0/+79
2025-02-04Update copyright string in switft filesOskar2-2/+2
2025-01-14Enable compilation with Swift 6 for most targetsBug Magnet1-1/+1
2024-11-26Fix typoBug Magnet1-2/+2
2024-11-26Allow API connections in blocked stateBug Magnet1-0/+3
2023-12-11Moving MullvadTransport into MullvadRESTmojganii2-3/+0
2023-12-11Moving RelayCache into MullvadRESTmojganii1-1/+0
2023-10-16Add tests for PacketTunnelActor, TunnelManager and AppMessageHandler.Jon Petersson2-3/+3
2023-09-21Merge TunnelProviderMessaging into PacketTunnelCoreAndrej Mihajlov1-1/+1
2023-08-24Return RESTTransport from TransportProviderAndrej Mihajlov1-25/+8
Ensures that RESTTransport returns consistent values throughout execution and solves the following issues: - Dynamic implementation of RESTTransport implemented by TransportProvider may yield different values (i.e RESTTransport.name) when accessed at different times during network operation execution - Current implementation of RESTTransport on TransportProvider yields "TransportProvider" before the first call to sendRequest() which is not correct behavior becuase we always log the name of transport that's being used before sending request. - When starting the app with network link conditioner blocking traffic, TransportProvider seems to print "TransportProvider" indefinitely even after the first call to sendRequest().
2023-06-27New swiftformat rule, enable google swift guidelinesBug Magnet2-2/+2
2023-06-20Enable reusing the shadowsocks connection once it is establishedBug Magnet2-16/+10
2023-05-29Introduce MullvadTransport and move Shadowsocks there, share ↵Bug Magnet2-50/+11
TransportProvider implementation
2023-05-25Pass the API endpoint to Shadowsocks instead of hardcoding itBug Magnet1-2/+10
2023-05-22Reformat the code for Swift 5.8Andrej Mihajlov2-4/+4
2023-05-22Add shadowsocks-proxy crateEmīls2-9/+85
2023-02-28Replace OperationCompletion with ResultAndrej Mihajlov1-4/+4
Error is set to OperationError.cancelled if operation is cancelled.
2022-12-09Handle application updates with settings migrationsajacl1-0/+1
1. Block all the traffic when tunnel cannot read the settings (Introduced empty tunnel in `TunnelConfiguration`). 2. Introduce proper error enum, wrap WireGuard error and settings migration error. 3. Report possible errors to GUI.
2022-12-08Wrap system tunnel management into TunnelStoreAndrej Mihajlov2-80/+28
2022-11-17REST: replace transport registry with transport provider closureAndrej Mihajlov1-8/+17
2022-11-09Remove shared instancesAndrej Mihajlov1-2/+4
2022-11-07Add URLSessionTransport into REST namespaceAndrej Mihajlov1-2/+2
2022-11-02PacketTunnelTransport: accept tunnel manager instanceAndrej Mihajlov2-7/+19
2022-10-21Move common code into two new targets: RelaySelector, TunnelProviderMessagingAndrej Mihajlov1-0/+1
2022-10-20Move REST into separate frameworksajacl2-2/+5
2022-10-13Add transport support in REST APISajad Vishkai2-0/+122
Copyright © 2025 - 2026 Wayne Cole. WTFPL. Attribution appreciated. No warranty. Not liable for bodily damages.