mirror of
https://github.com/meshtastic/protobufs.git
synced 2026-04-20 22:13:55 +00:00
work on mqtt/multichannel
This commit is contained in:
parent
5a23071d23
commit
a66504ed64
3 changed files with 60 additions and 1 deletions
23
apponly.proto
Normal file
23
apponly.proto
Normal file
|
|
@ -0,0 +1,23 @@
|
|||
syntax = "proto3";
|
||||
|
||||
option java_package = "com.geeksville.mesh";
|
||||
option java_outer_classname = "AppOnly";
|
||||
option optimize_for = LITE_RUNTIME;
|
||||
|
||||
import "mesh.proto";
|
||||
|
||||
/**
|
||||
This message wraps a MeshPacket with extra metadata about the sender and how it arrived.
|
||||
*/
|
||||
message ServiceEnvelope {
|
||||
/** The (probably encrypted) packet */
|
||||
MeshPacket packet = 1;
|
||||
|
||||
/** The global channel ID it was sent on */
|
||||
string channel_id = 2;
|
||||
|
||||
/** The sending mesh. FIXME, is this necessary? can we use this to authenticate/prevent fake
|
||||
nodeid impersonation for senders - i.e. use mesh id (which is authenticated) + local node id as
|
||||
the globally trusted nodenum */
|
||||
string mesh_id = 3;
|
||||
}
|
||||
|
|
@ -1,7 +1,7 @@
|
|||
syntax = "proto3";
|
||||
|
||||
option java_package = "com.geeksville.mesh";
|
||||
option java_outer_classname = "MeshProtos";
|
||||
option java_outer_classname = "DeviceOnly";
|
||||
option optimize_for = LITE_RUNTIME;
|
||||
|
||||
import "mesh.proto";
|
||||
|
|
|
|||
36
docs/docs.md
36
docs/docs.md
|
|
@ -3,6 +3,9 @@
|
|||
|
||||
## Table of Contents
|
||||
|
||||
- [apponly.proto](#apponly.proto)
|
||||
- [ServiceEnvelope](#.ServiceEnvelope)
|
||||
|
||||
- [deviceonly.proto](#deviceonly.proto)
|
||||
- [DeviceState](#.DeviceState)
|
||||
|
||||
|
|
@ -43,6 +46,39 @@
|
|||
|
||||
|
||||
|
||||
<a name="apponly.proto"></a>
|
||||
<p align="right"><a href="#top">Top</a></p>
|
||||
|
||||
## apponly.proto
|
||||
|
||||
|
||||
|
||||
<a name=".ServiceEnvelope"></a>
|
||||
|
||||
### ServiceEnvelope
|
||||
This message wraps a MeshPacket with extra metadata about the sender and how it arrived.
|
||||
|
||||
|
||||
| Field | Type | Label | Description |
|
||||
| ----- | ---- | ----- | ----------- |
|
||||
| packet | [MeshPacket](#MeshPacket) | | The (probably encrypted) packet |
|
||||
| channel_id | [string](#string) | | The global channel ID it was sent on |
|
||||
| mesh_id | [string](#string) | | The sending mesh. FIXME, is this necessary? can we use this to authenticate/prevent fake nodeid impersonation for senders - i.e. use mesh id (which is authenticated) + local node id as the globally trusted nodenum |
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
<a name="deviceonly.proto"></a>
|
||||
<p align="right"><a href="#top">Top</a></p>
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue