Skip to main content...

WPSD Now Part of the M17 Project

Sometimes, a match is truly made in heaven. And after some deliberating, I’ve agreed to place my WPSD project under the M17 Project umbrella.

There is, and always has been, very strong synergy and shared goals between the M17, OpenRTX and WPSD ecosystems. One of those cardinal goals, is paving the way for future ham radio – free from patent encumberances and manufacturer influence.

This “marriage” of projects so-to-speak, makes strategic sense in many ways. Most importantly, being our commitments to 100% free and open source initiatives in order to place amazing amateur radio technology and “vehicles” into amateur radio operators’ hands.

Additionally, both projects have grown exponentially over the past couple of years. With this kind of growth, comes more requirements, challenges and visions. It was important to me that WPSD remain impactful and sustainable. Through this project partnership, these goals will remain attainable, and help spread truly open digital voice mode operation across the globe for years to come.

Thirdly, both projects have large and vibrant user, development and support communities. Combining these forces will make it even easier and simpler to bring these truly freedom-centric technologies to countless ham shacks across the globe.

The combination of these two open source digital voice technologies will enable more innovation, more choice and a better user experience. I hope that you are as excited as I and the M17 team are!

WPSD Installs Only via Disk Images

TL;DR: WPSD can be installed only via the installation disk images.

When I first released WPSD to the masses, it was originally installed over existing Pi-Star installations via an installation script.

As WPSD grew, changed, improved, etc., I began offering updated installation disk images; and as of today, August 26, 2023, installation disk images are now the only method to installing WPSD. This means, that the installation script and method of installing WPSD over an existing Pi-Star instance is no longer available nor is it supported…

Additionally, we will be fully ceasing support of the older Pi-Star/“Buster”-based WPSD installations by the beginning of year 2024. Users who still run this older method of installation will no longer receive updates after 2024, and will need to upgrade their installation by installing the supported WPSD disk images. These older installations will eventually see a friendly message on their dashboards instructing them to upgrade to the disk image installation method.

Why This is Happening

Most importantly, the older WPSD-over-PiStar installations use Pi-Star’s very dated operating system, “Buster”. This operating system is end-of-life and is no longer supported.

Additionally, WPSD has evolved greatly, and we work closely with the developer(s) of the critical back-end software that performs the heavy lifting behind-the-scenes; and this software has also evolved greatly. Because of this evolution, there are simply too many incompatibilities with the much-newer WPSD code and programs running on older Pi-Star-based WPSD installations.

Being that our focus on development is based on the newer operating systems and newer underlying code, we’ve determined that installation disk images are more reliable to the users of WPSD and provides a better user experience.

Beware of Non-sanctioned WPSD Software & Disk Images

Public Service Announcement

As of June 8, 2023, W0CHP-PiStar-Dash (WPSD) is offered in three disk image “flavors”: RaspberryPi, OrangePi Zero, and NanoPi NEO. As we acquire alternative platforms to develop and test against, we release official images for them.

And for the time being, we offer the software for the older operating system that comes with the official Pi-Star (“buster”).

The Main Issue

Recently some unofficial/non-sanctioned disk images and code repositories of WPSD started appearing in the wild, specifically for the BananaPi platform.

Additionally, there are some creators / vendors of hotpots, shipping their BananaPi hotspots with these non-sanctioned disk images/software, which is actually not good for the user; and we also do not support the software on these hotspots.

Hints: if you ever see my code on GitHub, it’s not mine - I don’t host the official code there and I never have; and we also don’t have BananaPi official disk images released. Also, if you downloaded a disk image from a domain other than, or, it’s not an official disk image.

IMPORTANT: These are not official WPSD project images / software, and we do not support them (more on this later).

Why This Sucks for Users

There are quite a few issues with these disk images and non-official software I will lay out for you:

  1. The “fake” disk images are HUGE. As in the order of 7+GB. This is indicative of a poorly-created / manually-created disk image, and a poor disk image-creation process.

  2. The base operating system used in these unofficial disk images are based on the 2017 Debian upstream version 9.x (code-name: “Stretch”), and has been end-of-life since 2020. That means no security or other updates have been available since July of 2020. WPSD has deliberately never supported Stretch. Read: It’s incredibly old, it’s unsupported and severely outdated.

  3. The unofficial disk images and vendor hotspots with the unofficial software are using severely outdated WPSD code. WPSD is a rolling release/continuous delivery software; which means updates are frequent and rapid. As of this writing, the unofficial disk images are using code from approximately 8 months ago (this is considered “old code”). So old, that…

  4. Because of #3, users of non-sanctioned disk image/software are unable to keep up-to-date due to the code and infrastructure changes we made about 6 months ago.

Concerns of (Un-)Fairness and Lack of Collaboration

While I and my small team of developers and contributors are rabid Open Source advocates (which is why all my code is open), and we encourage improvement, innovation etc.; there are some back-end things that exist and work behind the scenes of WPSD in order to keep it up-to-date and maintain a properly-working system. And these processes and infrastructure components are not open, for reliability and security reasons.

Example, when you run a manual update or your hotspot updates nightly automatically, how and where does this happen? It happens from my servers; which contain lots of back-end code, host and ID file generation tasks, etc. Guess who pays for this? I do; solely.

So what this means, is that all of these unofficial WPSD images and software installs are pointing to the same infrastructure that my/our official software uses. That’s a lot of traffic I never agreed to, and worse, the creators of these non-sanctioned disk images never consulted me regarding this traffic, etc. Kinda shitty. All of this extra unauthorized traffic isn’t fair to the users of the official WPSD software and disk images.

Hotspot Vendors Take Note

While I’m very flattered that hostpot vendors want to ship my awesome software with their products, it’s not a simple as just using the code or disk images from my website. It’s best to work with me directly, so that we can help get your product(s) working perfectly for your hotspots and users with my software.

Otherwise your users won’t have the “Real Deal” WPSD software and they won’t be able to update, nor will they ever be able to receive support. Working with me and my project team ensures a better and more supported user experience.

If you insist on creating non-sanctioned versions of the software for your hotspots, create your own back-end infrastructure to update them - don’t use mine.

Please support your own software and remove references of W0CHP from the code. I don’t want my name/call sign associated with old and insecure software.

See next section…

The Future of Hostpots with WPSD

Without mentioning names (yet); some prominent hotspot vendors and creators have been working with me on custom versions and disk images for their products. This is the way to do it, and I applaud the vendors for working with me…it’s best for the users.

You will begin to see these official WPSD disk images for these hotspot products soon, and these hotpots will contain/ ship with official WPSD software.

When released, we will make an official announcement in the various and official mediums.

Update: 8/25/2023

W0CHP-PiStar-Dash/WPSD is now the official software for BridgeCom’s SkyBridge Max/Plus Hotspots, and they will be shipping with WPSD pre-installed very soon. We also have a custom SkyBridge disk image available.

Update: 6/11/2023

W0CHP-PiStar-Dash/WPSD is now the official software for ZUMradio’s ZUMspots, and they will be shipping with WPSD pre-installed very soon. We also have custom ZUMspot disk images available.

Customers of These Hotspots Using “Fake” WPSD Software

I will not apologize on behalf of the vendors providing you with outdated and unsupported software - they should have known better and worked with me and my team. If you are affected from this unsupported and outdated software, speak with them, and lobby them to work directly with the WPSD team and me.

Thanks for reading and 73, W0CHP.

No More Read-Only File-System in W0CHP-PiStar-Dash

…or, “R/O no mo, yo.” 😆

Most users are accustomed to W0CHP-PiStar-Dash (and Pi-Star) having a forced Read-Only file system by default. While this can be useful, it’s unnecessary in W0CHP-PiStar-Dash and in fact, is a pain in the ass sometimes.

Soon, when W0CHP-PiStar-Dash automatically updates itself at night, or when users invoke an update, the file-system will no longer be in Read-Only mode by default.

Scheduled Downtime October 5-7, 2022

Update 10/7/22:
Network move complete; all systems operational.

Beginning October 5, the various resources hosted on the network will experience intermittent, and some extended outages and downtime.

The network is moving to a different physical location, but will retain the same asynchronous fiber connections speeds, IPs, etc.

I anticipate the outages lasting no more than 48 hours. Once fully complete, I will update this post accordingly.

Resources that will be affected