96
submitted 3 weeks ago* (last edited 3 weeks ago) by mmmac@lemmy.zip to c/meshtastic@mander.xyz

Traceroute:

https://meshview.bayme.sh/graph/traceroute/1000442475

About 200 miles as the crow flies.

The mesh spans up to yuba city at this point, so about 270 miles

top 9 comments
sorted by: hot top controversial new old
[-] Hasherm0n@lemmy.world 7 points 3 weeks ago

I'm not really familiar with meshtastic, but this caught my eye on all because I live in SLO county. Looks really cool. I'll have to dig deeper.

[-] mmmac@lemmy.zip 7 points 3 weeks ago

Connect with the other SLO guys on our discord https://bayme.sh/ the user mk is our primary SLO contact

[-] mesamunefire@piefed.social 4 points 3 weeks ago

Oh yeah central valley hits it all the time with 7 hops. Its awesome. Wish the hop system worked more like meshcore but it is what it is.

[-] mmmac@lemmy.zip 2 points 3 weeks ago

What are your primary direct connections? Assuming yuba and sutter buttes?

[-] sqweeeeeeee@fosscad.io 1 points 3 weeks ago

I wonder why Meshtastic didn't just duplicate APRS design for the most part. The routing in APRS seems far superior

[-] mmmac@lemmy.zip 1 points 3 weeks ago

APRS routing is not adaptive to moving topology; Meshtastic explicitly supports mobile nodes and dynamic meshes

MT is more meant for flexible, off-grid, ad-hoc meshes with mixed mobile/static nodes and evolving routing optimizations

In my opinion, faux unicast on a broadcast medium is generally not a good fit

[-] sqweeeeeeee@fosscad.io 2 points 3 weeks ago* (last edited 3 weeks ago)

Yeah, I was misremembering exactly how APRS worked. I had a higher power mobile in my vehicle set up to digipeat packets from my handheld, but I guess that most mobile/handheld APRS radios are not digipeating. I just liked that with APRS the repeating stations name was appended to the packet, and I also liked that you could specify a path if desired.

Sometimes I am using meshtastic with just a couple of nodes in the middle of nowhere, and it currently works great for that. But at my house I've got a rooftop node, and then there is a mountaintop repeater many miles away that the rooftop node can hit, and a static node in FarAwayTown on the other side of the mountain. If I were able to set a path to "hop3" in the first scenario, but change it to "rooftop,mountaintop,FarAwayTown,hop3", it would allow me to communicate to those in FarAwayTown without bogging down the local mesh. I was pretty stoked that I could create solar meshtastic nodes to stick on a rooftop or nearby mountaintop for less than $20 to extend range, but doing so seems to cause a lot of congestion locally.

Then again, it is likely that I have no idea what I am talking about and need to study up on meshtastic ๐Ÿ˜† I'm pretty new to this.

[-] Demonmariner@lemmy.world 3 points 3 weeks ago

What modem preset are you using?

[-] mmmac@lemmy.zip 5 points 3 weeks ago* (last edited 3 weeks ago)

We're on medium fast right now due to node density in the bay

Blue dots = MF Orange dots = ms Red dots = lf

this post was submitted on 10 Nov 2025
96 points (100.0% liked)

Meshtastic

1418 readers
1 users here now

A community to discuss Meshtastic (https://meshtastic.org/docs/introduction)

founded 2 years ago
MODERATORS