diff --git a/index.html b/index.html index 414618e..abf38cc 100644 --- a/index.html +++ b/index.html @@ -145,7 +145,7 @@ .btn-group { display: flex; gap: 1em; - flex-wrap: nowrap; + flex-wrap: wrap; justify-content: center; } .btn-groups { @@ -153,6 +153,18 @@ flex-direction: column; gap: 1em; } + .section-title { + margin: 0.5em 0 0; + font-size: 1rem; + text-transform: uppercase; + letter-spacing: 0.08em; + color: #2C2D3C; + } + .section { + display: flex; + flex-direction: column; + gap: 0.75em; + } .btn-small { display: inline-block; margin-top: 0.5em; @@ -207,6 +219,9 @@ flex-direction: column; align-items: center; } + .section-title { + text-align: center; + } .btn { width: 100%; justify-content: center; @@ -251,44 +266,89 @@
-
- - Info Icon -
- Web Dashboard - Network metrics & analytics -
- - - Map Icon -
- CT Map - Nodes seen by CT Mesh -
- - - Globe Icon -
- Global Map - Nodes around the world -
- +
+
+ + Discord Icon +
+ Discord + Join the community +
+ +
-
- - Discord Icon -
- Discord - Join the community -
- - - Meshtastic Icon -
- Meshtastic - Learn more! -
- +
+

Meshtastic

+
+ + Meshtastic Icon +
+ Meshtastic + Learn more! +
+ + + Info Icon +
+ Web Dashboard + Network metrics & analytics +
+ + + Map Icon +
+ CT Map + Nodes seen by CT Mesh +
+ + + Globe Icon +
+ Global Map + Nodes around the world +
+ + + Info Icon +
+ Meshtastic Resources + Channels, MQTT, tools +
+ +
+
+
+

MeshCore

+
+ + MeshCore Logo +
+ MeshCore + Project website +
+ + + Map Icon +
+ MeshCore Map + Live node map +
+ + + Map Icon +
+ MeshCore Wardrive + Coverage maps +
+ + + Info Icon +
+ MeshCore Resources + Tools and maps +
+ +
@@ -297,4 +357,4 @@
- \ No newline at end of file + diff --git a/meshcore-resources.html b/meshcore-resources.html new file mode 100644 index 0000000..ef0cee1 --- /dev/null +++ b/meshcore-resources.html @@ -0,0 +1,204 @@ + + + + + + CT Mesh MeshCore Resources + + + + + + + + +
+
+

MeshCore Resources

+ +

Community-run Web Tools

+
+

These tools use data reported to our MQTT server by nodes across the state.

+
    +
  • MeshCore Map NEW! - live map showing MeshCore nodes
    • +
  • MeshCore Wardriving Map NEW! - coverage maps for MeshCore (you can also contribute!). Note: a new app is in testing and may supersede this.
    • +
+
+ +

Official Links

+

meshcore.co.uk

+

flasher.meshcore.co.uk

+
Note: the flasher requires WebSerial or Web Bluetooth support in your browser.
+ +

MQTT

+

Our MQTT broker is uplink-only and designed for fixed nodes across the state to serve as gateway nodes. Its purpose is not to bridge gaps or extend mesh coverage, but to report local traffic to our own web-based tools for analytical data and metrics to assess the mesh's performance. This role is best suited for stable, well-placed nodes with reliable coverage.

+

MeshCore MQTT uplink uses meshcoretomqtt on a Raspberry Pi or similar Linux computer with the service installed. This configuration stanza goes in your .env.local file after the first two MQTT servers that upload to analyzer.letsmesh.net. This also requires a custom firmware. See custom repeater firmware setup.

+ +
+ + 
# MQTT Broker 3 - CT Mesh
+MCTOMQTT_MQTT3_ENABLED=true
+MCTOMQTT_MQTT3_SERVER=mqtt.ctmesh.org
+MCTOMQTT_MQTT3_PORT=1883
+MCTOMQTT_MQTT3_USE_TLS=false
+MCTOMQTT_MQTT3_USERNAME=meshdev
+MCTOMQTT_MQTT3_PASSWORD=large4cats
+
+ + Back to CT Mesh +
+ + + diff --git a/meshcore.svg b/meshcore.svg new file mode 100644 index 0000000..2ecb872 --- /dev/null +++ b/meshcore.svg @@ -0,0 +1,68 @@ + + + + +Created by potrace 1.16, written by Peter Selinger 2001-2019 + + + + + + + + + + + + diff --git a/resources.html b/resources.html new file mode 100644 index 0000000..58d8641 --- /dev/null +++ b/resources.html @@ -0,0 +1,225 @@ + + + + + + CT Mesh Meshtastic Resources + + + + + + + + +
+
+

Meshtastic Resources

+ +

Mesh Channels

+

Default (Primary) Channel

+

Most CT chatter occurs on the default LongFast channel.

+

Name: LongFast or (blank)

+

Key: AQ==

+

Key size: Default or 1 byte

+ +

CT's established community secondary channel

+

Name: ConnNet

+

Key: pJgk5XqJY8Ar+jSqC5W81g==

+

Key size: 128 bit

+ +

MQTT

+

Our MQTT broker is uplink-only and designed for fixed nodes across the state to serve as gateway nodes. Its purpose is not to bridge gaps or extend mesh coverage, but to report local traffic to our own map and other web-based tools for analytical data and metrics to assess the mesh's performance. This role is best suited for stable, well-placed nodes with reliable coverage. If that describes your setup, follow the steps at on this page to get set up.

+ +

Key Settings

+
+

MQTT > Enabled > ON

+

MQTT > Encryption Enabled > ON

+

MQTT > Map Report > OFF

+

MQTT > Root Topic > msh/US/CT

+

MQTT > Address > mqtt.ctmesh.org

+

MQTT > Username > meshdev

+

MQTT > Password > large4cats

+

MQTT > TLS Enabled > OFF

+

Channels > Primary Channel > Positions Enabled > ON

+

Channels > Primary Channel > Approximate Location > (set as desired)

+

Channels > Primary Channel > MQTT Uplink > ON

+

Channels > Primary Channel > MQTT Downlink > OFF

+

Settings > Modules > Neighbor Info > ON

+

LoRa > Ok to MQTT > ON

+
+ +

Note: CT Mesh's MQTT server is bridged and uplinks to the MQTT servers for both meshtastic.liamcottle.net and meshmap.net.

+ +

Community-run Web Tools

+
+

These tools use data reported to our MQTT server by nodes across the state.

+
    +
  • Meshtastic Map - live map of Meshtastic nodes CT Mesh has heard
    • +
  • Malla - deeper packet-level metrics and mesh performance insights fed from MQTT
    • +
  • PotatoMesh NEW! - packet, chat, node list, and map fed from RF on Box Mountain
    • +
  • MeshInfo legacy, partially broken - MQTT gateway setup info, secondary map, graphs, message history, etc.
    • +
+
+ +

Infrastructure Nodes

+

Important: Infrastructure roles like ROUTER, REPEATER, ROUTER_CLIENT, or ROUTER_LATE are rarely appropriate. Unless your node is sitting on top of one of the tallest buildings in Hartford with clear line-of-sight across the region, using these roles will hurt more than help. For almost everyone, the correct choice is CLIENT. If you think you've got a node that truly warrants an infrastructure role, reach out first - we'd rather make sure it benefits the mesh than inadvertently weakens it.

+ + Back to CT Mesh +
+ + +