Send admin-made owner changes and admin NodeInfo requests past the routine throttle

An admin set_owner announced the new name through the routine NodeInfo path, so a rename made within
30 minutes of the last NodeInfo never went out - and the reboot set_owner schedules inherits that
throttle from the persisted transmit history. Inside an edit transaction nothing was sent at all.
The change is now announced on the 60 s interactive gate once it is saved, at commit for a
transaction.

A signed NodeInfo request from a node holding a live PKC admin session is likewise answered on the
60 s gate, past the 30 minute floor and the 12 h per-requester suppression.
This commit is contained in:
James Rich committed 2026-10-30 13:59:44 -05:00
1 parent 332b5b0a2c
commit b65fa9505c
10 files changed
+297 -6

No files matched your search

+2
View File
@@ -61,6 +61,8 @@ class NodeInfoModule : public ProtobufModule<meshtastic_User>, private concurren
/// Set across sendOurNodeInfo()'s own allocReply(), so the transmit stamp waits for an accepted send.
bool deferHistoryStamp = false;
bool suppressReplyForCurrentRequest = false;
/// The request came from a node holding a remote admin session, so it is answered on the interactive path.
bool adminRequestForCurrentRequest = false;
/// Sender -> uptime seconds (Time::getUptimeSecs()) at our last reply. Seconds, not millis:
/// the suppression window is hours wide. See handleReceivedProtobuf().
std::map<NodeNum, uint32_t> lastNodeInfoSeen;