Subj : sbbsecho
To : Digital Man
From : Bill McGarrity
Date : Tue Nov 07 2017 06:26 am
Hiya Rob...
Found an anomaly in sbbsecho where it creates a PKT yet is sending the same pkt
to two different address whereas one of the downlinks is rejecting them due to
iot not being addressed to them...
Downlinks report (address 24:30/1):
+ 15-Jan-2016 00:15:12 mbfido[8594] Packet : 14160543.pkt type 2+
+ 15-Jan-2016 00:15:12 mbfido[8594] From : 24:24/1 to 24:120/4
+ 15-Jan-2016 00:15:12 mbfido[8594] Dated : 14-01-2016 16:05:32
+ 15-Jan-2016 00:15:12 mbfido[8594] Program : SBBSecho 2.32
? 15-Jan-2016 00:15:12 mbfido[8594] packet is not for us, aborting
From my sbbsecho log....
2016-01-14 16:05:32 Sending packet (c:\fd\outbound\14160543.pkt) to 24:120/4
2016-01-14 16:05:32 File (c:\fd\outbound\14160543.pkt) for 24:120/4 added to
BSO/FLO file: c:\fd\outbound.018\00780004.clo
As to where it should go to...
Now... where it's not supposed to go to...
2016-01-14 16:05:42 Sending packet (c:\fd\outbound\14160543.pkt) to 24:30/0
2016-01-14 16:05:42 File (c:\fd\outbound\14160543.pkt) for 24:30/0 added to
BSO/FLO file: c:\fd\outbound.018\001e0000.hlo
