home.social

#mesh-networking — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #mesh-networking, aggregated by home.social.

fetched live
  1. #Reticulum version 1.3.7 is out, so I asked #Codex to compare the 1.3.7 Python tree (obtained from Mark's source code) against my protocol Specification previously extracted from the Reticulum Network Stack version 1.3.5.

    Result: no apparent wire-level protocol break. The main changes are operational/interface-discovery related, plus verifier maintenance.

    salemdata.net/johnpress/?p=1068 for Codex assessment.

    #RNS #MeshNetworking #ProtocolAnalysis

  2. #Reticulum version 1.3.7 is out, so I asked #Codex to compare the 1.3.7 Python tree (obtained from Mark's source code) against my protocol Specification previously extracted from the Reticulum Network Stack version 1.3.5.

    Result: no apparent wire-level protocol break. The main changes are operational/interface-discovery related, plus verifier maintenance.

    salemdata.net/johnpress/?p=1068 for Codex assessment.

    #RNS #MeshNetworking #ProtocolAnalysis

  3. Reticulum has no separate protocol spec; the Python implementation is effectively the reference. But GitHub, PyPI, and RNS-distributed releases may not show the same version.

    I documented how I fetched the signed 1.3.7 release over Reticulum itself using rngit, including signer validation and artifacts retrieved.

    salemdata.net/johnpress/?p=1056

    #Reticulum #RNS #LoRa #MeshNetworking #OpenSource #microReticulum

  4. Reticulum has no separate protocol spec; the Python implementation is effectively the reference. But GitHub, PyPI, and RNS-distributed releases may not show the same version.

    I documented how I fetched the signed 1.3.7 release over Reticulum itself using rngit, including signer validation and artifacts retrieved.

    salemdata.net/johnpress/?p=1056

    #Reticulum #RNS #LoRa #MeshNetworking #OpenSource #microReticulum

  5. Reticulum has no separate protocol spec; the Python implementation is effectively the reference. But GitHub, PyPI, and RNS-distributed releases may not show the same version.

    I documented how I fetched the signed 1.3.7 release over Reticulum itself using rngit, including signer validation and artifacts retrieved.

    salemdata.net/johnpress/?p=1056

    #Reticulum #RNS #LoRa #MeshNetworking #OpenSource #microReticulum

  6. Reticulum has no separate protocol spec; the Python implementation is effectively the reference. But GitHub, PyPI, and RNS-distributed releases may not show the same version.

    I documented how I fetched the signed 1.3.7 release over Reticulum itself using rngit, including signer validation and artifacts retrieved.

    salemdata.net/johnpress/?p=1056

    #Reticulum #RNS #LoRa #MeshNetworking #OpenSource #microReticulum

  7. Reticulum has no separate protocol spec; the Python implementation is effectively the reference. But GitHub, PyPI, and RNS-distributed releases may not show the same version.

    I documented how I fetched the signed 1.3.7 release over Reticulum itself using rngit, including signer validation and artifacts retrieved.

    salemdata.net/johnpress/?p=1056

    #Reticulum #RNS #LoRa #MeshNetworking #OpenSource #microReticulum

  8. Commercial telcos can't serve regional Australia by design, not by malice. It's arithmetic: sparse markets don't clear the return threshold.

    Mesh networks flip it. Every LoRa node is a subscriber, a relay, and infrastructure at once, cooperative by physics, not choice. New piece on building cooperatively owned networks and what Helium's collapse into a corporation-in-disguise teaches about protecting them.

    gaggl.com/blogs/2026-07-08-coo

    #MeshNetworking #LoRaWAN #Cooperatives #RegionalAustralia #DigitalCommons

  9. Commercial telcos can't serve regional Australia by design, not by malice. It's arithmetic: sparse markets don't clear the return threshold.

    Mesh networks flip it. Every LoRa node is a subscriber, a relay, and infrastructure at once, cooperative by physics, not choice. New piece on building cooperatively owned networks and what Helium's collapse into a corporation-in-disguise teaches about protecting them.

    gaggl.com/blogs/2026-07-08-coo

    #MeshNetworking #LoRaWAN #Cooperatives #RegionalAustralia #DigitalCommons

  10. Cooperative by Design: Why Mesh Networks and Community Telcos Are Built for Each Other

    A commercial telco and a mesh network are not different ways of solving the same problem. They are built on opposite assumptions about how infrastructure works. Understanding why that matters is the key to understanding why regional Australia keeps getting left behind, and what to do about it. The Economics of Absence In regional and rural Australia, the connectivity gap is not a failure of effort or ambition. It is the predictable output of a particular economic model.

    web.brid.gy/r/https://gaggl.co

  11. TP-Link Deco BE77 Review: Great Mesh Wi-Fi for the Eero-Weary

    I’ve tested a lot of Wi-Fi routers over the years, and they’re pretty much always better than the…
    #NewsBeep #News #Technology #CA #Canada #meshnetworking #reviews #router #SmartHome #TP-Link #Wirelessnetworking
    newsbeep.com/ca/781575/

  12. How does a #Reticulum mesh actually behave on #LoRa when messages must traverse multiple transport nodes?

    I ran seven GPS-disciplined #TBeamSupreme units running #microReticulum, forced AMY<->GUY traffic through five intermediate nodes, parsed all seven logs into SQLite, and produced a microsecond-scale chronology plus CAD-delay plot. The test exposes forwarding, channel contention, and radio backoff in one trace.

    salemdata.net/johnpress/?p=1041

    #MeshNetworking #ESP32 #OpenSource

  13. How does a #Reticulum mesh actually behave on #LoRa when messages must traverse multiple transport nodes?

    I ran seven GPS-disciplined #TBeamSupreme units running #microReticulum, forced AMY<->GUY traffic through five intermediate nodes, parsed all seven logs into SQLite, and produced a microsecond-scale chronology plus CAD-delay plot. The test exposes forwarding, channel contention, and radio backoff in one trace.

    salemdata.net/johnpress/?p=1041

    #MeshNetworking #ESP32 #OpenSource

  14. How does a #Reticulum mesh actually behave on #LoRa when messages must traverse multiple transport nodes?

    I ran seven GPS-disciplined #TBeamSupreme units running #microReticulum, forced AMY<->GUY traffic through five intermediate nodes, parsed all seven logs into SQLite, and produced a microsecond-scale chronology plus CAD-delay plot. The test exposes forwarding, channel contention, and radio backoff in one trace.

    salemdata.net/johnpress/?p=1041

    #MeshNetworking #ESP32 #OpenSource

  15. How does a #Reticulum mesh actually behave on #LoRa when messages must traverse multiple transport nodes?

    I ran seven GPS-disciplined #TBeamSupreme units running #microReticulum, forced AMY<->GUY traffic through five intermediate nodes, parsed all seven logs into SQLite, and produced a microsecond-scale chronology plus CAD-delay plot. The test exposes forwarding, channel contention, and radio backoff in one trace.

    salemdata.net/johnpress/?p=1041

    #MeshNetworking #ESP32 #OpenSource

  16. How does a #Reticulum mesh actually behave on #LoRa when messages must traverse multiple transport nodes?

    I ran seven GPS-disciplined #TBeamSupreme units running #microReticulum, forced AMY<->GUY traffic through five intermediate nodes, parsed all seven logs into SQLite, and produced a microsecond-scale chronology plus CAD-delay plot. The test exposes forwarding, channel contention, and radio backoff in one trace.

    salemdata.net/johnpress/?p=1041

    #MeshNetworking #ESP32 #OpenSource

  17. TP-Link Deco BE77 Review: Great Mesh Wi-Fi for the Eero-Weary

    I’ve tested a lot of Wi-Fi routers over the years, and they’re pretty much always better than the…
    #NewsBeep #News #Technology #AU #Australia #meshnetworking #reviews #router #SmartHome #TP-Link #Wirelessnetworking
    newsbeep.com/au/778881/

  18. TP-Link Deco BE77 Review: Great Mesh Wi-Fi for the Eero-Weary

    I’ve tested a lot of Wi-Fi routers over the years, and they’re pretty much always better than the…
    #NewsBeep #News #Technology #AU #Australia #meshnetworking #reviews #router #SmartHome #TP-Link #Wirelessnetworking
    newsbeep.com/au/778881/

  19. Mesh networking projects, including AREDN (arednmesh.org/) and other high-speed data networks, can use 44Net tunnels to interconnect sites and experiment with IP-based services across multiple networks. #44net #44yearsof44net #meshnetworking #aredn #networking

  20. Mesh networking projects, including AREDN (arednmesh.org/) and other high-speed data networks, can use 44Net tunnels to interconnect sites and experiment with IP-based services across multiple networks. #44net #44yearsof44net #meshnetworking #aredn #networking

  21. Mesh networking projects, including AREDN (arednmesh.org/) and other high-speed data networks, can use 44Net tunnels to interconnect sites and experiment with IP-based services across multiple networks. #44net #44yearsof44net #meshnetworking #aredn #networking

  22. Mesh networking projects, including AREDN (arednmesh.org/) and other high-speed data networks, can use 44Net tunnels to interconnect sites and experiment with IP-based services across multiple networks. #44net #44yearsof44net #meshnetworking #aredn #networking

  23. Mesh networking projects, including AREDN (arednmesh.org/) and other high-speed data networks, can use 44Net tunnels to interconnect sites and experiment with IP-based services across multiple networks. #44net #44yearsof44net #meshnetworking #aredn #networking

  24. See: IBM’s discussion of post-quantum cryptography:

    youtu.be/RYUR9BdDgyI?is=EwT735

    Hey #Reticulum: what is the plan for PQC? Reticulum depends on public-key cryptography, while PQC may impose significant packet-size, CPU, and memory costs for LoRa-class devices.

    The White House has accelerated Federal PQC migration deadlines: key establishment by 2030.

    #PQC #Cryptography #LoRa #MeshNetworking #Privacy

    whitehouse.gov/presidential-ac

    Very troubling: government harvesting now, decrypt later.

  25. See: IBM’s discussion of post-quantum cryptography:

    youtu.be/RYUR9BdDgyI?is=EwT735

    Hey #Reticulum: what is the plan for PQC? Reticulum depends on public-key cryptography, while PQC may impose significant packet-size, CPU, and memory costs for LoRa-class devices.

    The White House has accelerated Federal PQC migration deadlines: key establishment by 2030.

    #PQC #Cryptography #LoRa #MeshNetworking #Privacy

    whitehouse.gov/presidential-ac

    Very troubling: government harvesting now, decrypt later.

  26. See: IBM’s discussion of post-quantum cryptography:

    youtu.be/RYUR9BdDgyI?is=EwT735

    Hey #Reticulum: what is the plan for PQC? Reticulum depends on public-key cryptography, while PQC may impose significant packet-size, CPU, and memory costs for LoRa-class devices.

    The White House has accelerated Federal PQC migration deadlines: key establishment by 2030.

    #PQC #Cryptography #LoRa #MeshNetworking #Privacy

    whitehouse.gov/presidential-ac

    Very troubling: government harvesting now, decrypt later.

  27. See: IBM’s discussion of post-quantum cryptography:

    youtu.be/RYUR9BdDgyI?is=EwT735

    Hey #Reticulum: what is the plan for PQC? Reticulum depends on public-key cryptography, while PQC may impose significant packet-size, CPU, and memory costs for LoRa-class devices.

    The White House has accelerated Federal PQC migration deadlines: key establishment by 2030.

    #PQC #Cryptography #LoRa #MeshNetworking #Privacy

    whitehouse.gov/presidential-ac

    Very troubling: government harvesting now, decrypt later.

  28. See: IBM’s discussion of post-quantum cryptography:

    youtu.be/RYUR9BdDgyI?is=EwT735

    Hey #Reticulum: what is the plan for PQC? Reticulum depends on public-key cryptography, while PQC may impose significant packet-size, CPU, and memory costs for LoRa-class devices.

    The White House has accelerated Federal PQC migration deadlines: key establishment by 2030.

    #PQC #Cryptography #LoRa #MeshNetworking #Privacy

    whitehouse.gov/presidential-ac

    Very troubling: government harvesting now, decrypt later.

  29. Each #MeshNetworking radio test cycle requires rebuilding and uploading separate #ESP32S3 firmware images 4 each #TBeamSupreme, because each unit has different blocker rules to simulate network topology.

    Moving the compile step from my older Intel workstation to a Ryzen 7950 box cuts roughly 8–9 minutes from each iteration. That adds up fast when testing, retesting, and chasing radio anomalies.

    salemdata.net/johnpress/?p=974

    #Reticulum #PlatformIO #EmbeddedSystems #Forgejo #Gentoo #HardwareHacking

  30. Each #MeshNetworking radio test cycle requires rebuilding and uploading separate #ESP32S3 firmware images 4 each #TBeamSupreme, because each unit has different blocker rules to simulate network topology.

    Moving the compile step from my older Intel workstation to a Ryzen 7950 box cuts roughly 8–9 minutes from each iteration. That adds up fast when testing, retesting, and chasing radio anomalies.

    salemdata.net/johnpress/?p=974

    #Reticulum #PlatformIO #EmbeddedSystems #Forgejo #Gentoo #HardwareHacking

  31. Each #MeshNetworking radio test cycle requires rebuilding and uploading separate #ESP32S3 firmware images 4 each #TBeamSupreme, because each unit has different blocker rules to simulate network topology.

    Moving the compile step from my older Intel workstation to a Ryzen 7950 box cuts roughly 8–9 minutes from each iteration. That adds up fast when testing, retesting, and chasing radio anomalies.

    salemdata.net/johnpress/?p=974

    #Reticulum #PlatformIO #EmbeddedSystems #Forgejo #Gentoo #HardwareHacking

  32. Each #MeshNetworking radio test cycle requires rebuilding and uploading separate #ESP32S3 firmware images 4 each #TBeamSupreme, because each unit has different blocker rules to simulate network topology.

    Moving the compile step from my older Intel workstation to a Ryzen 7950 box cuts roughly 8–9 minutes from each iteration. That adds up fast when testing, retesting, and chasing radio anomalies.

    salemdata.net/johnpress/?p=974

    #Reticulum #PlatformIO #EmbeddedSystems #Forgejo #Gentoo #HardwareHacking

  33. Each #MeshNetworking radio test cycle requires rebuilding and uploading separate #ESP32S3 firmware images 4 each #TBeamSupreme, because each unit has different blocker rules to simulate network topology.

    Moving the compile step from my older Intel workstation to a Ryzen 7950 box cuts roughly 8–9 minutes from each iteration. That adds up fast when testing, retesting, and chasing radio anomalies.

    salemdata.net/johnpress/?p=974

    #Reticulum #PlatformIO #EmbeddedSystems #Forgejo #Gentoo #HardwareHacking

  34. Ich überlege, mir einen Repeater für #meshcore zuzulegen. Spontan würde ich zum SenseCAP P1 pro greifen. Wie sind eure Erfahrungen damit oder habt ihr gerade einen anderen Repeater, mit dem ihr happy seid?
    #meshtastic #MeshNetworking

  35. Ich überlege, mir einen Repeater für #meshcore zuzulegen. Spontan würde ich zum SenseCAP P1 pro greifen. Wie sind eure Erfahrungen damit oder habt ihr gerade einen anderen Repeater, mit dem ihr happy seid?
    #meshtastic #MeshNetworking

  36. Ich überlege, mir einen Repeater für #meshcore zuzulegen. Spontan würde ich zum SenseCAP P1 pro greifen. Wie sind eure Erfahrungen damit oder habt ihr gerade einen anderen Repeater, mit dem ihr happy seid?
    #meshtastic #MeshNetworking

  37. Ich überlege, mir einen Repeater für #meshcore zuzulegen. Spontan würde ich zum SenseCAP P1 pro greifen. Wie sind eure Erfahrungen damit oder habt ihr gerade einen anderen Repeater, mit dem ihr happy seid?
    #meshtastic #MeshNetworking

  38. Ich überlege, mir einen Repeater für #meshcore zuzulegen. Spontan würde ich zum SenseCAP P1 pro greifen. Wie sind eure Erfahrungen damit oder habt ihr gerade einen anderen Repeater, mit dem ihr happy seid?
    #meshtastic #MeshNetworking

  39. Published a new Reticulum testing note: simulating mesh-network distance in the lab by using software “blocking pairs” between nearby T-Beams. This lets a desktop test force packets through intermediate transport nodes instead of requiring people scattered miles apart.

    salemdata.net/johnpress/?p=874

    #Meshtastic #Reticulum #LoRa #MeshNetworking #TBeam #EmbeddedSystems

  40. Published a new Reticulum testing note: simulating mesh-network distance in the lab by using software “blocking pairs” between nearby T-Beams. This lets a desktop test force packets through intermediate transport nodes instead of requiring people scattered miles apart.

    salemdata.net/johnpress/?p=874

    #Meshtastic #Reticulum #LoRa #MeshNetworking #TBeam #EmbeddedSystems

  41. Published a new Reticulum testing note: simulating mesh-network distance in the lab by using software “blocking pairs” between nearby T-Beams. This lets a desktop test force packets through intermediate transport nodes instead of requiring people scattered miles apart.

    salemdata.net/johnpress/?p=874

    #Meshtastic #Reticulum #LoRa #MeshNetworking #TBeam #EmbeddedSystems

  42. Published a new Reticulum testing note: simulating mesh-network distance in the lab by using software “blocking pairs” between nearby T-Beams. This lets a desktop test force packets through intermediate transport nodes instead of requiring people scattered miles apart.

    salemdata.net/johnpress/?p=874

    #Meshtastic #Reticulum #LoRa #MeshNetworking #TBeam #EmbeddedSystems

  43. Published a new Reticulum testing note: simulating mesh-network distance in the lab by using software “blocking pairs” between nearby T-Beams. This lets a desktop test force packets through intermediate transport nodes instead of requiring people scattered miles apart.

    salemdata.net/johnpress/?p=874

    #Meshtastic #Reticulum #LoRa #MeshNetworking #TBeam #EmbeddedSystems

  44. 📡 Battlemesh v18 is happening!

    Join us from 7–13 September 2026 in Gornji Karin, Croatia, for a week of talks, workshops, hacking, testing, and collaboration around community networks, mesh networking, OpenWrt, and open communication infrastructure.

    Participation is free and open to everyone.

    Read the announcement and find all details here:
    battlemesh.org/BattleMeshV18/A

    Please share and help us spread the word!

    #Battlemesh #CommunityNetworks #OpenWrt #MeshNetworking #FOSS

  45. 📡 Battlemesh v18 is happening!

    Join us from 7–13 September 2026 in Gornji Karin, Croatia, for a week of talks, workshops, hacking, testing, and collaboration around community networks, mesh networking, OpenWrt, and open communication infrastructure.

    Participation is free and open to everyone.

    Read the announcement and find all details here:
    battlemesh.org/BattleMeshV18/A

    Please share and help us spread the word!

    #Battlemesh #CommunityNetworks #OpenWrt #MeshNetworking #FOSS

  46. 📡 Battlemesh v18 is happening!

    Join us from 7–13 September 2026 in Gornji Karin, Croatia, for a week of talks, workshops, hacking, testing, and collaboration around community networks, mesh networking, OpenWrt, and open communication infrastructure.

    Participation is free and open to everyone.

    Read the announcement and find all details here:
    battlemesh.org/BattleMeshV18/A

    Please share and help us spread the word!

    #Battlemesh #CommunityNetworks #OpenWrt #MeshNetworking #FOSS

  47. 📡 Battlemesh v18 is happening!

    Join us from 7–13 September 2026 in Gornji Karin, Croatia, for a week of talks, workshops, hacking, testing, and collaboration around community networks, mesh networking, OpenWrt, and open communication infrastructure.

    Participation is free and open to everyone.

    Read the announcement and find all details here:
    battlemesh.org/BattleMeshV18/A

    Please share and help us spread the word!

    #Battlemesh #CommunityNetworks #OpenWrt #MeshNetworking #FOSS

  48. 📡 Battlemesh v18 is happening!

    Join us from 7–13 September 2026 in Gornji Karin, Croatia, for a week of talks, workshops, hacking, testing, and collaboration around community networks, mesh networking, OpenWrt, and open communication infrastructure.

    Participation is free and open to everyone.

    Read the announcement and find all details here:
    battlemesh.org/BattleMeshV18/A

    Please share and help us spread the word!

    #Battlemesh #CommunityNetworks #OpenWrt #MeshNetworking #FOSS

  49. I used #Bluetooth / #BLE as a short-range stand-in for #LoRa to test #Reticulum mesh behavior with #TBeamSupreme units.

    The RSSI graph worked: carry two units away from a base pair, watch signal strength decay, disappear, then recover on return.

    The GPS trace? Woeful. Useful lesson: RSSI test succeeded; urban T-Beam GPS precision did not.

    salemdata.net/johnpress/?p=757

    #MeshNetworking #ESP32 #FieldTesting #OpenSource

  50. I used #Bluetooth / #BLE as a short-range stand-in for #LoRa to test #Reticulum mesh behavior with #TBeamSupreme units.

    The RSSI graph worked: carry two units away from a base pair, watch signal strength decay, disappear, then recover on return.

    The GPS trace? Woeful. Useful lesson: RSSI test succeeded; urban T-Beam GPS precision did not.

    salemdata.net/johnpress/?p=757

    #MeshNetworking #ESP32 #FieldTesting #OpenSource

  51. I used #Bluetooth / #BLE as a short-range stand-in for #LoRa to test #Reticulum mesh behavior with #TBeamSupreme units.

    The RSSI graph worked: carry two units away from a base pair, watch signal strength decay, disappear, then recover on return.

    The GPS trace? Woeful. Useful lesson: RSSI test succeeded; urban T-Beam GPS precision did not.

    salemdata.net/johnpress/?p=757

    #MeshNetworking #ESP32 #FieldTesting #OpenSource

  52. I used #Bluetooth / #BLE as a short-range stand-in for #LoRa to test #Reticulum mesh behavior with #TBeamSupreme units.

    The RSSI graph worked: carry two units away from a base pair, watch signal strength decay, disappear, then recover on return.

    The GPS trace? Woeful. Useful lesson: RSSI test succeeded; urban T-Beam GPS precision did not.

    salemdata.net/johnpress/?p=757

    #MeshNetworking #ESP32 #FieldTesting #OpenSource

  53. I used #Bluetooth / #BLE as a short-range stand-in for #LoRa to test #Reticulum mesh behavior with #TBeamSupreme units.

    The RSSI graph worked: carry two units away from a base pair, watch signal strength decay, disappear, then recover on return.

    The GPS trace? Woeful. Useful lesson: RSSI test succeeded; urban T-Beam GPS precision did not.

    salemdata.net/johnpress/?p=757

    #MeshNetworking #ESP32 #FieldTesting #OpenSource

  54. Skipping the #TBeamSupreme for this test: two bare #RaspberryPiZero2W boards running #microReticulum with my BLE interface, each sending poetry to the other over their built-in Bluetooth radios.

    Two $17 SBCs, 8.8 MB builds, fully secure Reticulum link, and ambidextrous roles: start both, and they decide who is client/server.

    #Bluetooth #BLE #Reticulum #RaspberryPi #MeshNetworking