adam/meshing-around
1
0 Fork 0
mirror of https://github.com/SpudGunMan/meshing-around.git synced 2026-10-30 22:01:57 +01:00
Code Issues 12 Packages Projects Releases Wiki Activity

messages sent via tcp connection are sent as Text not PKI #76

New Issue
Closed
opened 2026-10-05 01:20:08 +02:00 by adam · 2 comments
adam commented 2026-10-05 01:20:08 +02:00
Owner
Copy link
Copy source

I have interface configured as such:
[interface] type = tcp hostname = redacted port = 4403 mac = redacted dummy = True
Inbound messages are reported to upstream mqtt as PKI, however outbound messages from meshing-around are sent in the clear as Text.

It looks like send_message() is determining the key based on the inbound channel? According to the logs, all inbound messages are being seen as "Channel:0":

2025-10-05 00:22:31,901 | INFO | Device:1 Channel: 0 Received DM: Motd From: drp mobile
2025-10-05 00:22:34,103 | INFO | Device:1 Sending DM: MOTD: REDACTED To: drp mobile

I have interface configured as such: ` [interface] type = tcp hostname = redacted port = 4403 mac = redacted dummy = True ` Inbound messages are reported to upstream mqtt as PKI, however outbound messages from meshing-around are sent in the clear as Text. It looks like send_message() is determining the key based on the inbound channel? According to the logs, all inbound messages are being seen as "Channel:0": 2025-10-05 00:22:31,901 | INFO | Device:1 Channel: 0 Received DM: Motd From: drp mobile 2025-10-05 00:22:34,103 | INFO | Device:1 Sending DM: MOTD: REDACTED To: drp mobile <!-- github-sync-id:3484363244 -->
adam closed this issue 2026-10-05 01:20:08 +02:00
adam commented 2026-10-05 01:20:09 +02:00
Author
Owner
Copy link
Copy source

UDP systems (and MQTT) do not use ChannelID like RF systems, they use a hashID of the channel name. will look at patches for this possibly.

One way to handle RF vs IP packets is [interface] [interface2] segment the IP to softNodes?

UDP systems (and MQTT) do not use ChannelID like RF systems, they use a hashID of the channel name. will look at patches for this possibly. One way to handle RF vs IP packets is [interface] [interface2] segment the IP to softNodes? <!-- github-comment-id:3369163588 -->
adam commented 2026-10-05 01:20:10 +02:00
Author
Owner
Copy link
Copy source

patch in with debug log to trap these https://github.com/SpudGunMan/meshing-around/commit/1568d026f2289490452624012b080b5ee2a0a66c this is on lab branch

patch in with debug log to trap these https://github.com/SpudGunMan/meshing-around/commit/1568d026f2289490452624012b080b5ee2a0a66c this is on lab branch <!-- github-comment-id:3508941824 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/meshing-around#76