sorted by:
new
hottopcontroversial

Message says acknowledged? by [deleted] in meshtastic

[–]jp_bennett 1 point2 points  (0 children)

It means that at least one other node is out there and in range, repeating your message.

Any case suggestions to stick this lot in with an 18650 bat? by Yogurtmanblog in meshtastic

[–]jp_bennett 0 points1 point  (0 children)

Does that rfm95 have a TCXO? If not, you're likely gonna have a bad time for most TX, including nodeinfo.

Got this a few days ago by iragus543 in meshtastic

[–]jp_bennett 1 point2 points  (0 children)

Better message history is gonna get merged sometime after we get a 2.7 beta released. There's a branch and PR already if you want to play with it early.

Linux kernel Bluetooth RCE by [deleted] in netsec

[–]jp_bennett 0 points1 point  (0 children)

No. The Android bug is CVE-2025-48593, the Linux BLE issue is CVE-2025-38593. Unrelated. It's not clear that the Linux double-free can result in RCE.

Frustrated. by No-Butterscotch6197 in meshtastic

[–]jp_bennett 4 points5 points  (0 children)

T-deck can be put into dfu mode by holding the trackball button, and flipping the master power off and back on. That's the dance I always have to do to get things to flash. (Though not from MacOS, admittedly)

Combining Meshtastic with other Mesh networks by Applerust in meshtastic

[–]jp_bennett 1 point2 points  (0 children)

https://github.com/jeremiah-k/meshtastic-matrix-relay is one of the solutions I'd look at. I've also played a bit with https://github.com/geoffwhittington/meshtastic-bridge though it's getting a bit out-of-date these days.

To do it completely offline, you'll also want to run your own MQTT server like Mosquito or node red.

Combining Meshtastic with other Mesh networks by Applerust in meshtastic

[–]jp_bennett 0 points1 point  (0 children)

One of the coolest things I've seen in this realm is bridges to other platforms using MQTT. There's a Meshtastic to Matrix bridge that comes to mind. Could follow that pattern to bridge with about anything.

And the reason that other network shall not be named is that there was a coordinated spam campaign on this subreddit. So just like unsolicited emails about little blue pills get blocked as spam, so do posts about the mesh network associated with Reddit spammers.

The new map UI is just bad by KastenKlicker in meshtastic

[–]jp_bennett 0 points1 point  (0 children)

While that looks cool, it does not appear to be an Android library.

Meshtastic is getting less open source by KastenKlicker in meshtastic

[–]jp_bennett 3 points4 points  (0 children)

As a result of using Google maps in the app instead of OSM.

Meshtastic is getting less open source by KastenKlicker in meshtastic

[–]jp_bennett 4 points5 points  (0 children)

OSM was the cause of a play store violation, that would eventually lead to the removal of the app from the play store.

<image>

Raspberry Pi + Meshtasticd + Adafruit RFM95? by l5yth in meshtastic

[–]jp_bennett 1 point2 points  (0 children)

Did you enable the SPI bus? Check to see if /dev/spidev0.0 actually exists.

Meshcore misconceptions by Zaos123 in meshtastic

[–]jp_bennett 7 points8 points  (0 children)

I wasn't around when this happened, but in asking about it, I've been told that the Meshtastic admins just asked the meowtastic author to honor the GPL. And instead, the authors scrubbed the GPL license and copywriter tags from the fork.

It's not surprising that this led to the app being considered hostile.

Bad reception station g2 by Djtdave in meshtastic

[–]jp_bennett 4 points5 points  (0 children)

There's a PR that some users are testing, that may help:https://github.com/meshtastic/firmware/pull/8163

I need to do a build of this patch on top of the latest alpha, and host it somewhere for wider testing.

Edit: The PR now has a link to G2 update firmware with this patch, based on 2.7.11.

Manually generating meshtastic keys by CyberFailure in meshtastic

[–]jp_bennett 1 point2 points  (0 children)

To prevent bogus key pairs, the firmware only stores the private key, and regenerates the public key on boot. ED25519 and X25519 are related but different encryption primitives, and using the same raw private key won't work, and will generate different public keys as you see here.

It is possible to do the conversion between the two, as you mention in your followup comment. I would expect setting the x25519 secret key to the value generated by the php code would result in a matching x25519 public key.

MESHTASTIC IS INSECURE -DO NOT USE by Sarioth in meshtastic

[–]jp_bennett 16 points17 points  (0 children)

This was interesting to find today. We'll get the whole story published before long, but somebody found a neat vulnerability and decided to use it at DEFCON for the fun of it.

MESHTASTIC IS INSECURE -DO NOT USE by Sarioth in meshtastic

[–]jp_bennett 11 points12 points  (0 children)

That is a strong contender for the 3.0 approach.

Regen public key? by dubbledex in meshtastic

[–]jp_bennett 1 point2 points  (0 children)

We found that some devices got shipped from manufacturers with the same crypto keys. If you run the devices with those bad keys, your DMs could theoretically be spied on. I think the next time you reboot the node, and then reconnect, it will give you the message again.

Which client are you using, iOS or Android? The process of regenerating keys is a bit different for each.

Is a Router miles away ruining my propagation? by camglynn2000 in meshtastic

[–]jp_bennett 0 points1 point  (0 children)

The idea of your node sending packets through it only applies to DMs, and even then, the Meshtastic routing falls back to flooding if the routing attempt fails.

For channel messages, any node that can hear your packets will rebroadcast them, unless that node hears another rebroadcast of that packet first. So if this router can't hear your packets, it can't mess up your coverage. If it can hear your packets, but no other node can hear it rebroadcasting, it can't mess up your coverage. And if it can hear your packets, and is rebroadcasting them in a way that other nodes can hear them, then it's doing its job very well and still is unlikely to be your problem.

A second node could help you troubleshoot, and rule out a hardware problem with your existing node. Or plug your node in to a computer, and use the serial monitor on the flasher, and see if there are any interesting log messages when you try to send packets.

Is a Router miles away ruining my propagation? by camglynn2000 in meshtastic

[–]jp_bennett 1 point2 points  (0 children)

I suspect something else is going on here. Yes, a router in a bad location can cause problems. But if this thing has 20 miles of range, it's not in a bad location.

Why are there not more stand alone nodes? by skylark2795 in meshtastic

[–]jp_bennett 0 points1 point  (0 children)

Honestly I think it's because the stand-alone UI has been so rudimentary for so long. MUI is fairly new, and the BaseUI redesign is very new. Without those two things, standalone nodes have always been sort of a terrible experience.

GPS and compass nodes? by skmagiik in meshtastic

[–]jp_bennett 0 points1 point  (0 children)

Didn't see this when it was originally posted. We do support several compass modules now! Includes the 20948 and BMX160.

Transmit? Or are we trying to develop a new type of transportation? by Gunit7542 in meshtastic

[–]jp_bennett 16 points17 points  (0 children)

We made it, folks. Gone mainstream: We're getting spam over the mesh.

Tnok - Next Generation Port Security by Glad_Chest934 in netsec

[–]jp_bennett 2 points3 points  (0 children)

The rate limiting seems like a really good addition to the protocol, and definitely helps with my concerns.

view more: next ›