Expand description
The GATT bearer: a mesh reached through a node’s Mesh Proxy service
rather than on the advertising channels. ProxyBearer is the client
(a gateway whose radio is busy scanning, or a mesh out of advertising
range but within one connection’s); ProxyServer is a node’s side.
Proxy PDUs (SAR and type, crate::bearer::proxy_segments and
crate::bearer::ProxyRx) go to Mesh Proxy Data In as writes without
response and come back as notifications of Data Out. Proxy Configuration
messages set which destinations the proxy forwards to us: on connecting,
an empty reject list, so it forwards everything.
Modules§
- uuid
- The Mesh Proxy service and its characteristics (checked against the SIG’s assigned numbers in the tests).
Structs§
- Proxy
Bearer - A connection to a node’s Mesh Proxy service, as a
Bearer. - Proxy
Server - A node’s Mesh Proxy service, for one client at a time, as a
Bearer: what the node sends goes to the client (when its filter lets the destination through) and torelay(the advertising bearer); what the client sends goes to the node and torelay, unchanged.
Enums§
- Config
- A Proxy Configuration message (opcode and parameters).
- Error
- Errors connecting to a proxy.
- Filter
Type - A proxy’s filter: which destinations it forwards to its client.