3 posts tagged with "firmware"

The first 2.8 alpha didn't last long. A problem turned up in its packet signing code, so 2.8.0 is revoked and 2.8.1 replaces it. If any of your nodes run 2.8.0, update them to 2.8.1.

2.8.1 is an alpha and isn't ready for wide deployment. Most people should wait. Install it if you're comfortable running into bugs and reporting them.

The revocation shouldn't overshadow the release. 2.8 signs packets, keeps your location private by default, and handles much larger meshes. Here's what changed, and what to know before you upgrade from 2.7.

This year marked the second time we have deployed an event-specific Meshtastic firmware at DEF CON, and the first time we have partnered with the event organizers and community groups such as Darknet-NG and the Lonely Hackers Club to create and roll it out. While the official numbers are not yet available, many attendees reported seeing more than 2,000 individual nodes connected during the event, with thousands of messages, including a healthy share of Rickrolls and even full Bee Movie scripts, flowing across both public and private channels throughout Las Vegas. This marks the largest known Meshtastic network to date.

As the Meshtastic project continues to grow, so does the number of supported hardware devices. While this growth is exciting and shows just how far the project has come, it also brings new challenges.

Supporting a wide range of hardware requires a significant amount of resources. This includes developer time for maintenance and bug fixes, GitHub runners to build firmware, server space to store hundreds of binaries, and space in the flasher and documentation. All of these factors contribute to increased complexity, making it harder for users to find the hardware they are looking for.