Linking BBS

[FredB1959]

My BBS is sends a bbslink request but gets an answer from my test bbs pa8f that the BBS Link is disabled.

2025-03-29 22:11:24,329 | INFO | Device:2 Channel:2 SendingChannel: bbslink MeshBot looking for peers
2025-03-29 22:11:26,623 | WARNING | Device:2 Ignoring DM: System: BBS Link is disabled for your node. From: test bbs pa8f
2025-03-29 22:11:26,624 | INFO | Device:2 Sending DM: MeshBot, here for you like a friend who is not. Try sending: ping @foo or, cmd To: test bbs pa8f

When test BBS pa8f sends a bbslink request the same thing occurs

2025-03-29 22:19:45,594 | INFO | Device:2 Channel:2 ReceivedChannel: bbslink MeshBot looking for peers From: test bbs pa8f
2025-03-29 22:19:45,596 | DEBUG | System: Bot detected Commands:[{'cmd': 'bbslink', 'index': 0}] From: !8e19eabd
2025-03-29 22:19:45,597 | WARNING | System: BBS Link is disabled for node 2384063165.
2025-03-29 22:19:46,798 | INFO | Device:2 Sending DM: System: BBS Link is disabled for your node. To: test bbs pa8f
2025-03-29 22:19:47,457 | WARNING | Got Own Welcome/Help header. From: test bbs pa8f

Any ideas on how to solve this?

73, Fred/PA8F

[SpudGunMan]

Did you lock down the peer for synch or is it still in open mode?

[SpudGunMan]

I need to fix the other way thanks for identifying that!

The concept is one bot asks for the messages from the other bot which serves them up. It's not bidirectional in transfer.

You would use the schedule option to set up the request. It's a bit of tinkering to set it up.

[ghost]

@SpudGunMan
The way we have configured it now is by turning on the scheduler and automaticly send a "bbslink MeshBot looking for peers"

Isn't it better to use a while loop in case bbslink_whitelist contains nodes, like:

bbslink_whitelist = "nodeno!,nodeno2,nodeno3,nodeno4"
array = string.split(",")
for nodeid in array:
    # execute.synrhonize(nodeid) (or something like that).

Maybe it's even better also beïng able to set a time in config.ini so synchronization will be done after {amount of seconds}.
Guess it's also something to store the last synchronization and use a hard limit in the code itself to avoid both nodes initiating a synchronization and get a lot of trash over RF ;-)

Without setting the scheduler synchronization didn't seem to work (unless it's only once an hour (or longer)).

[SpudGunMan]

I patched the bug identified here thank you - the idea to set a time is good but I also need to config which node and channel the communication goes out on so thats more values needed and if people only want synch on like Sunday .. this is where I got trapped up in handling the config/schedule stuff

[ghost]

True on that @SpudGunMan ...

Awesome!

I was more thinking about something like;

bbslink_autosync = True # True = Automatic Sync enabled, False = Automatic Sync disabled (Use scheduler).
# bbslink_whitelist = "node_id!interface number"
bbslink_whitelist = "nodeno1!iface1,nodeno2!iface1,nodeno3!iface2,nodeno4!iface1,nodeno5!iface2"

def synchronize(node_id, iface):
    print(f"Synchronizing with {node_id} via {iface}")

if bbslink_autosync:
    node_list = bbslink_whitelist.split(',')
    for node in node_list:
        node_id, iface = node.split('!')
        synchronize(node_id, iface)

Adding all those other stuff I mentioned requires quite a bunch more of coding as I have noticed. By the way, the bbslink_whitelist would be awesome to have with interfaces (hostname) as well.... hostname = localhost:4403, localhost:4004 in case multiple ports are used with for example meshtasticd ;-)

[SpudGunMan]

Those are good ideas one fear I have with a loop like that is it eats up airtime if things go bad or offline which is common over time I feel.

Airtime is so limited

As for the interfaces this is in context of the meshtastic API which when proto feed is open today its a pipe to proto, I am unaware the API would support multiple tcp hosts like that (it needs to be networked in MQTT in firmware)