Node map
Nodes with GPS in their adverts. Grey lines are links inferred from flood paths (thicker = more packets). Click a node for its neighbours and paths. Packets moving in real time are on the live map.
Live traffic
Packets as the observer hears them, and what your own radio (AB8M Home) is doing. "?" = guessed from a 1-byte hash.
Channel messages
Decrypted traffic on the channels in config.json. Click a message for its packet.
Traffic
Packets heard per interval, by packet type.
Network graph
The same links as the node map, laid out by connection instead of geography: each line is two nodes seen next to each other in a heard path (thicker = more packets). Starts from the map positions and relaxes. Drag to rearrange, hover to highlight neighbours, click for details. Uses the time range and observer above.
Network events
Repeaters heard advertising each day, and changes worth a look: new keys, new nearby repeaters, ones gone quiet, and your watched repeaters.
Repeaters heard advertising, per day
Events
Who heard me
How far packets from your own nodes spread: every copy an observer heard (yours or the neomesh ones) carries the chain of repeaters it passed through. Counts flooded adverts and decoded channel messages; SNR is only known for the last hop into an observer.
First repeater to pick it up
Reach by hop — share of sends each repeater relayed at that distance
Recent sends — click one for its relay tree
Signal trends — direct links
SNR of every node your observer hears first-hand (the last repeater on a flood, or a zero-hop advert), in 6-hour medians. "vs. before" compares the last 24 h with the rest of the period: −3 dB or worse is flagged. A slow slide over days points at antenna, coax or new obstructions; many links jumping at once usually means weather (tropospheric ducting).
Channel airtime
Estimated share of time the channel is busy where your observer listens, from each packet's length and the radio settings (LoRa time-on-air formula). Only what the observer heard; it's a lower bound. The higher the busy share, the likelier two packets collide.
Average busy share by weekday and hour
Flood redundancy
How the mesh duplicates traffic, from every copy any observer heard. In every copy: of packets heard more than once, the share that passed through this repeater on every copy — it's the only way that traffic got out. Runs parallel to: another repeater that carried the same packets on a different branch. Limited to what the observers hear.
Copies of each flood packet your observer heard
Coverage — MeshMapper
Community wardriving coverage for your radio settings, from MeshMapper. Their map, shown in a frame: pan and zoom inside it.
Nodes heard
Click a row for signal history. "Direct" = packets this node transmitted that the observer heard first-hand. Source: Advert = heard it advertise itself; MeshMapper = identity from the MeshMapper directory (an MM next to a location means only the position came from there).
Packet history
Search everything stored — raw packets are kept 90 days. Search a node name (packets it sent or relayed), a key or path-hash prefix, a packet hash, or message text. Click a row for the packet details, ▶ to replay it on the live map.
Set filters and press Search.
Hops to observer
How far flood packets travelled before they reached you.
Noise floor
dBm, from the observer's 5-minute status reports. Lower is quieter.
Channel airtime
Share of time the radio spent receiving / transmitting.
Busiest repeaters
How often each repeater appears in the paths you heard.
Storage & backups
Raw packets and status reports older than the retention period are deleted hourly; channel messages and DMs are kept. A copy of the database is made every night.