Packet #39440589 Success
ROUTING_APP packet from WYK0 bot w/BBS DM ‘cmd’ (🤖) to WYK WisMesh Tag (WWMT)
6
Total Receptions
6
Unique Gateways
2
Hop Count
2
Payload Bytes
Packet Information
| Database ID: | 39440589 |
|---|---|
| Mesh Packet ID: |
0x37614700
Used for correlation across gateways |
| Timestamp: | 2026-05-16 04:52:34 UTC |
| From Node: | WYK0 bot w/BBS DM ‘cmd’ (🤖) |
| To Node: | WYK WisMesh Tag (WWMT) |
| Success: | Processed |
| Protocol: |
ROUTING_APP
Port: 5 |
| Gateway: | Ranchlands BEAM [ConcernedThirdParty] (@@RL) |
|---|---|
| Channel: | Custom |
| RSSI: | Unknown |
| SNR: | Unknown |
| Hop Info: |
2/3 hops
Start: 3, Limit: 1 |
| Relay Node: |
c4
Last byte of the last hop that relayed this packet |
Payload Data
Protocol: ROUTING_APP
Size: 2 bytes
Decoded:
Yes
Decoded Data:
{
"error_reason": "NO_RESPONSE",
"type": "protobuf",
"portnum": "ROUTING_APP",
"message_class": "Routing"
}
Raw Packet Analysis
Complete field breakdown and MQTT privacy/exposure analysisPacket Structure
MQTT Packet Flow:
ServiceEnvelope (MQTT layer) → MeshPacket (Mesh layer) → Decoded Payload (Application data)
| Total Size: | 2 bytes |
|---|---|
| Gateway: | !848898f4 |
| Channel: | Custom |
| Payload Type: | ROUTING_APP |
| Hop Count: | 2 / 3 |
Privacy Summary
Exposure Level:
Direct Message
Direct Message
Privacy Features:
✓ Direct LoRa transmission (not via MQTT)
✓ Targeted to specific node
+ 2 more...
✓ Direct LoRa transmission (not via MQTT)
✓ Targeted to specific node
+ 2 more...
Exposure Risks:
âš Packet visible to MQTT subscribers
âš Multi-hop path visible (2 hops)
âš Packet visible to MQTT subscribers
âš Multi-hop path visible (2 hops)
MQTT ServiceEnvelope Fields
MQTT ServiceEnvelope contains the MeshPacket plus routing metadata
| Field | Value |
|---|---|
gateway_id |
!848898f4
Node ID format |
channel_id |
Custom
|
packet |
MeshPacket (2 bytes)
Contains the actual mesh network packet |
MeshPacket Fields
Core mesh packet with routing and payload information
| Field | Value | Type |
|---|---|---|
from |
1508830959
Source node ID |
uint32 |
to |
1208889781
Target node ID |
uint32 |
decoded.portnum |
5
ROUTING_APP |
enum |
decoded.payload_length |
2 bytes
|
size |
hop_limit |
1
Remaining hops allowed |
uint32 |
hop_start |
3
Initial hop limit |
uint32 |
hops_taken |
2
Calculated: hop_start - hop_limit |
derived |
rx_rssi |
Not set | int32 |
rx_snr |
Not set | float |
rx_time |
1778907153
Receive timestamp |
fixed32 |
via_mqtt |
False
Direct LoRa transmission |
bool |
want_ack |
False
No ACK requested |
bool |
priority |
120
Packet priority level |
enum |
delayed |
Not set | enum |
channel |
Not set | uint32 |
pki_encrypted |
False
Standard encryption |
bool |
next_hop |
Not set | uint32 |
relay_node |
196
Relay node ID |
uint32 |
tx_after |
Not set | uint32 |
timestamp |
1778907154.128786
Unix timestamp |
uint32 |
MQTT Privacy & Exposure Analysis
Analysis of privacy features and exposure risks when packet is shared via MQTT
Exposure Level: Direct Message
Privacy Features:
- ✓ Direct LoRa transmission (not via MQTT)
- ✓ Targeted to specific node
- ✓ Custom channel: Custom
- ✓ Gateway node ID tracked
Exposure Risks:
- âš Packet visible to MQTT subscribers
- âš Multi-hop path visible (2 hops)
MQTT-Specific Fields
| Gateway ID: | !848898f4 |
Complete Payload Analysis
Detailed breakdown of all payload fields and decoded data
Payload Metadata:
| Protocol: | ROUTING_APP |
|---|---|
| Size: | 2 bytes |
| Decoded: | Yes |
Complete Payload Data (JSON):
{
"error_reason": "NO_RESPONSE",
"type": "protobuf",
"portnum": "ROUTING_APP",
"message_class": "Routing"
}
Complete Protobuf Decode (JSON)
{
"service_envelope": {
"gateway_id": "!848898f4",
"channel_id": "Custom",
"packet": "MeshPacket (see mesh_packet below)"
},
"mesh_packet": {
"from": 1508830959,
"to": 1208889781,
"id": 929122048,
"rx_time": 1778907153,
"rx_snr": 0.0,
"rx_rssi": 0,
"hop_limit": 1,
"hop_start": 3,
"via_mqtt": false,
"want_ack": false,
"priority": 120,
"delayed": 0,
"channel_index": null,
"pki_encrypted": false,
"next_hop": 0,
"relay_node": 196,
"tx_after": 0,
"decoded": {
"portnum": 5,
"payload": "1808",
"want_response": null,
"dest": null,
"source": null,
"request_id": null,
"reply_id": null,
"emoji": null,
"parsed_payload": {
"error_reason": "NO_RESPONSE",
"type": "protobuf",
"portnum": "ROUTING_APP",
"message_class": "Routing"
}
}
}
}
Raw Packet Data (2 bytes)
1808
Hex Analysis:
| Size: | 2 bytes |
|---|---|
| Format: | Protobuf (Protocol Buffers) |
| Encoding: | Binary with varint and length-delimited fields |
This is the raw protobuf-encoded payload as received from MQTT.
The structure follows the Meshtastic protobuf schema definitions.
All Receptions
All gateways that received this packetCorrelation: Using Mesh Packet ID
Reception Locations
Loading...
Loading reception map...
Map shows gateway locations that received this packet. Hop counts are displayed if available.
| Gateway | Time Offset | RSSI | SNR | Hops | Relay | Channel | Timestamp | Actions |
|---|---|---|---|---|---|---|---|---|
| Ranchlands BEAM [ConcernedThirdParty] (@@RL) Primary |
0.000s
Reference |
Unknown | Unknown | 2 |
c4
|
Custom | 2026-05-16 04:52:34 UTC | Current |
| Pooty Base (POOT) |
-0.027s
Before |
-113.0 dBm | -16.50 dB | 1 |
37
BCNH
|
Custom | 2026-05-16 04:52:34 UTC | View |
| Concerned Third Party BEAM (@CTP) |
-0.011s
Before |
-132.0 dBm | -12.75 dB | 1 |
37
BCNH
|
Custom | 2026-05-16 04:52:34 UTC | View |
| AU518987077 BEAM [ConcernedThirdParty] (@AU) |
+0.010s
After |
Unknown | Unknown | 2 |
c4
|
Custom | 2026-05-16 04:52:34 UTC | View |
| Jitterbug BEAM [ConcernedThirdParty] (@JB) |
+0.021s
After |
Unknown | Unknown | 2 |
c4
|
Custom | 2026-05-16 04:52:34 UTC | View |
| Jitterbug ECHO [ConcernedThirdParty] (~JB) |
+0.528s
After |
-116.0 dBm | -14.00 dB | 2 |
73
4773
|
Custom | 2026-05-16 04:52:34 UTC | View |
6
Total Receptions
6
Unique Gateways