As of January 2024, the Apple TV is very limited when it comes to file transfers. AirDrop and iCloud Drive were the most natural options for one-off “import and delete” of a profile, but they are not available. Another option was setting up a local server with a QR, but I find it quite a cumbersome UX.
+As of December 2024, the Apple TV is still limited when it comes to file transfers. AirDrop and iCloud Drive are the most natural options for one-off “import and delete” of a profile, but they are not available. Another option is setting up a local server with a QR, but I find it quite a cumbersome UX.
-Therefore, given that version 2.3.0 supports end-to-end CloudKit encryption, I deemed iCloud a very decent trade-off between usability and privacy. Let alone the convenience of the simple toggle, the iOS/macOS apps act as a remote to reflect local changes instantly on your Apple TV. This benefits the UX of the TV app dramatically, where you just use the remote to change the profile or toggle the connection.
+Therefore, given that Passepartout supports end-to-end CloudKit encryption, iCloud proved a decent trade-off between usability and privacy. Besides the convenience of the simple toggle, the iOS/macOS apps act as a remote to reflect local changes instantly on your Apple TV. This benefits the UX of the TV app dramatically, where you only use the remote to change the profile or toggle the connection.
-Bear in mind that only “Apple TV” profiles are shared and synchronized over iCloud, non-shared profiles follow the global iCloud app preference.
+Bear in mind that only “Apple TV” profiles are shared and synchronized over iCloud implicitly. Other profiles follow the “iCloud > Enabled” toggle (in 3.0.0) or the global iCloud app preference (before 3.0.0).
Also there was another bug in 2.3.0 that was preventing profiles from being saved to iCloud at all. Cycling the “Sync with iCloud” toggle should restore proper syncing.
-If you use encrypted DNS (DoH/DoT), you may encounter the error message “iPhone is not connected to the internet” when trying to use Siri. Unfortunately, this is an Apple bug.
+They finally do!
-Starting from version 3.0.0, Passepartout stores one VPN configuration per profile. This means you can build your workflows directly from the Apple Shortcuts app and that they can execute in the background.
-Unfortunately Apple is guilty of not fixing a related bug. I mean, it’s been there for years -since iOS 9 with my first bug report dating back to 2017- without them caring at all. No feedback and not even a proper response. And of course, no progress.
+Use the “Set VPN” action in Shortcuts and pick your profiles by name. Beware that having on-demand enabled may affect some automation.
+ +The “Connect to provider server” automation is a bit more complex but will be restored soon.
+ +Unfortunately, Apple is guilty of not fixing a related bug. I mean, it’s been there for years -since iOS 9 with my first bug report dating back to 2017- without them caring at all. No feedback and not even a proper response. And of course, no progress.
This is one of the several threads remarking the issue:
@@ -126,6 +132,14 @@In short, there’s really nothing I can do about it.
+I’m working on it.
+ +I’m working on it.
+On the other hand, if you install a TestFlight build from scratch, paid features will not be available.
+WARNING: this trick is currently ineffective on macOS.
+You should contact with your provider to double check if there is interest in being added to Passepartout. Beware that some may be concerned instead. Ultimately, you can submit your provider request for a viability review to providers@passepartoutvpn.app.
@@ -206,7 +222,13 @@Historically, Passepartout has used a low MTU setting (1250 bytes) in order to maximize compatibility, at the cost of performance. iOS version 1.13.0 -and any macOS version- supports tunnel MTU customization. With this update, it sounded reasonable to also leverage a standard (higher) MTU (usually 1500).
-If such change is making the app struggle in your environment, I encourage you to try lowering the MTU. You can easily do that by setting MTU to “Manual” in “Network settings”. You will then be able to pick something down to 1200 bytes. Decrease incrementally until you restore VPN operation.
+If such a change is making the app struggle in your environment, I encourage you to try lowering the MTU.
+ +Add a “Routing” module to your profile and specify a custom MTU value. Decrease incrementally until you restore the VPN operation.
+ +You can change the MTU by setting MTU to “Manual” in “Network settings”. You will then be able to pick something down to 1200 bytes.
Last but not least: make sure that you’re not experiencing a simple DNS issue. Try pinging a remote machine by IP address: if that works, then DNS is the culprit. This usually happens when your server, whatever the reason, doesn’t push public DNS servers to clients. There’s a quick workaround: enter “Network settings” in Passepartout, set “DNS” to “Manual” and add an explicit DNS server address. That should fix it.
+Last but not least: make sure that you’re not experiencing a simple DNS issue. Try pinging a remote machine by IP address: if that works, then DNS is the culprit. This usually happens when your server, whatever the reason, doesn’t push public DNS servers to clients.
+ +There’s a quick workaround: add a “DNS” module in your profile and add an explicit DNS server address. That should fix it.
+ +Enter “Network settings”, set “DNS” to “Manual” and add an explicit DNS server address.
Bear in mind that some providers require specific credentials for their direct OpenVPN servers. That’s why Passepartout, in those cases, has a convenient link in the bottom of the Account screen showing you where to find such credentials on your provider’s website.
+Bear in mind that some providers require specific credentials for their direct OpenVPN servers. That’s why Passepartout, in those cases, has a convenient link at the bottom of the OpenVPN “Credentials” screen (“Account” in 2.3.x), showing you where to find such credentials on your provider’s website.
Regarding Mullvad in particular, remember to strip spaces from the username.
@@ -288,23 +316,17 @@ key-direction 1Unless redirect-gateway is either:
Talking about OpenVPN, unless redirect-gateway is either:
the default gateway is NOT changed. That is, your external IP won’t be the VPN’s IP. Double check the “Default gateway” entry in the “Configuration” page to see how your host profile looks like. On the other hand, the default gateway is always enforced for provider profiles.
- -This has been recently fixed in Passepartout 1.6.0 as it’s the standard OpenVPN behavior. Before 1.6.0, Passepartout erroneously assumed that all traffic should go through the VPN implicitly.
+the default gateway is NOT changed. That is, your external IP won’t be the VPN’s IP. This is not the case for provider profiles, though, where the default gateway is always enforced to be the provider gateway to avoid unintended leaks.
Try this website to test your external IP before and after this change.
-The reason behind not providing a widget is exactly the same as Siri Shortcuts. A widget would still need to open the app, thus making it quite useless.
-The reason why Passepartout does not present any personal information in app is privacy. Obtaining one’s IP address, regardless of being connected to a VPN or not, involves querying -and trusting- a third party service. Knowing such info is also of little use, given that most of the time you don’t want to share your VPN IP address and therefore link your identity to it. However, this feature might be introduced later as a diagnostic tool.
diff --git a/feed.xml b/feed.xml index 4ce3ac3..c60c7b7 100644 --- a/feed.xml +++ b/feed.xml @@ -1 +1 @@ -