Note December 2nd 2021:
This blog post is outdated. Check out the SPNs latest status.
On October 12th, the SPN reached the “Broader Testing”
What Does It Cost?
Reaching the “Broader Testing” phase is an important milestone for the SPN. Exciting weeks and months are ahead of us.
However, not all aspects and features of the SPN have been thoroughly tested, confirmed or implemented. As such, access to the SPN during the “Broader Testing” phase is free of charge, no credit will be charged from your accounts.
Who Gets Access?
Everybody who fulfills both these requirements is eligible for the “Broader Testing” phase:
- You have pre-ordered the SPN before September 30th, 2021
- You have an email attached to your account
What Happens If I Pre-Order the SPN After September 30th?
You will not be able to purchase your way into the “Broader Testing” phase retrospectively. However, you will be enqueued in the group right after - where you will be able to activate your SPN subscription as soon as the SPN reaches the “Alpha” phase.
Why Do I Need An Email to Participate?
In the “Broader Testing” phase, communication with all SPN testers is critical in order to find bugs and to mature the SPN into “Alpha” and beyond. Having users join the incomplete network without any means of communication would not help the SPN progress in any meaningful way.
We know many of you do not want to add an email address to your account due to privacy and we totally respect that. We thank you so much for your trust and are doing our best to progress the SPN into “Alpha” where everybody will be able to enjoy their SPN subscription.
During the “Broader Testing” phase we would reach out once ore twice per month to ask question like:
- What is working in the SPN?
- What is not working?
- Where should we add more servers?
- etc…
Your contributions and answers will shape the stability and future of the SPN. Thanks in advance!
Can I Add An Email Retrospectively?
Yes. If you pre-ordered the SPN before September 30th, 2021 you can add an email to your account retrospectively and still get access to the “Broader Testing” phase.
Thanks to Everyone Who Is Part of the Journey
We are super glad the SPN finally achieved this milestone and are hard at work pushing it forward into “Alpha” and beyond. Thank you for your support, your patience and your trust.
SPN “Broader Testing” Status and Goals
As we are heavily iterating and improving the SPN, all goals, issues and next steps will change over the next weeks. Visit the SPN Status Page in our docs for an up-to-date version.
Snapshot as of October 11th
0.1 How Can I Activate the SPN “Broader Testing” Phase?
- read the blog post to see if you are eligible
- log in to your Safing account to receive your access code
- in the Portmaster App
- switch to the “Beta” Release Channel
- Restart the Portmaster and Reload the UI
- You should now see a yellow “BETA” in the global settings
- Enable the SPN
- enter your Special Access Code
- configure the Use SPN setting globally and for different apps, depending on your needs
0.2 How Can I Test that the SPN Is Running?
- Go to https://duckduckgo.com/?q=what+is+my+ip to see your current IP address before activating the SPN
- Enable the SPN
- Reload DuckDuckGo and check if the IP address has changed
- Bonus Step: Visit some of the “what is my IP” websites, your IP address should change frequently (based on the destination server location)
1. Normally Works Well - Report if Broken
- Portmaster Client successfully connects to the SPN
- Normal browsing of websites
- Big file downloads
- Video streaming
- Low Bandwidth: up to 5MBit/s
2. Under Investigation - Please Test and Report
- Video Conferencing
- UDP based applications
- Medium Bandwidth: targeting 30MBit/s as next step
3. Under Construction
- Connecting to the SPN via Portmaster is currently very basic, new views showing what the SPN is currently doing are being designed and developed
- we will add instructions for how to test that the SPN is working on your device to the docs before October 12th
4. Known Issues
- The SPN re-uses connections to nodes. Due to missing route evaluation during routing calculation we currently cannot guarantee the minimum three hops.
- Speeds might vary greatly as we do not know the resource profile of the SPN yet.
- The SPN seems to be failing after sleep/suspend. Investigating. Disable/Enable SPN as a workaround.
- We’re leaking open file descriptors somewhere, which also affects Portmaster after some time. Restart Portmaster as a workaround.
- For stability, the client is artificially more sequential in order to provide more stability. This might lead to lag when lots of connections are initiated at the same time. Eg. when browsing to “big” websites.
How To Report Bugs
Bugs can be reported on the SPN repository on GitHub
October 1, 2021 • Written by David