#81 Stop All Forward (FS 1) keeps BBS ‘Still connected’

[Red Tuby]

When using "FS 1" to stop all forwarding which aborts all connect scripts, when trying to "FR <bbs>" to the same BBS to restart a forwarding attempt, FBB reports that the BBS is still connected, but checking the "%" status shows that it is not.</bbs>

So something has gotten stuck somewhere.

`fs 1

Stopping forwarding on port 1
--0 new/1 old msgs--matrix-->
fr ei2gyb
BBS EI2GYB already connected
--0 new/1 old msgs--matrix-->

fr ei2gyb
--0 new/1 old msgs--matrix-->
BBS EI2GYB already connected
--0 new/1 old msgs--matrix-->
%

LinFBB version 7.0.11 (Linux) compiled on Dec 7 2022
Bid:32000 Lang:1 Ports:4 Ch:44 FBB Ok BIN Ok

Uptime : 63 days, 14 hours 58 minutes
Load average : 1.04, 1.37, 1.57
Available disks: C:

MiB Mem : 3837.9 total, 1440.9 free, 1326.3 used, 1070.7 buff/cache
MiB Swap: 0.0 total, 0.0 free, 0.0 used, 2244.9 avail Mem

Channel usage:
Ch Callsign N1 N2 N3 Cnect Cmput T-Out Used Status Buf Freq
02 PE1RRR- 0 14 00 00 5:50 0:00 10:00 500 Transfer 0 LINBPQ

--0 new/1 old msgs--matrix-->
`

[Red Tuby]

fs 1
Stopping forwarding on port 1
--0 new/1 old msgs--matrix-->
fr ei2gyb
BBS EI2GYB already connected
--0 new/1 old msgs--matrix-->
fr ei2gyb
--0 new/1 old msgs--matrix-->
BBS EI2GYB already connected
--0 new/1 old msgs--matrix-->
%
LinFBB version 7.0.11 (Linux) compiled on Dec 7 2022
Bid:32000 Lang:1 Ports:4 Ch:44 FBB Ok BIN Ok
Uptime : 63 days, 14 hours 58 minutes
Load average : 1.04, 1.37, 1.57
Available disks: C:
MiB Mem : 3837.9 total, 1440.9 free, 1326.3 used, 1070.7 buff/cache
MiB Swap: 0.0 total, 0.0 free, 0.0 used, 2244.9 avail Mem
Channel usage:
Ch Callsign N1 N2 N3 Cnect Cmput T-Out Used Status Buf Freq
02 PE1RRR- 0 14 00 00 5:50 0:00 10:00 500 Transfer 0 LINBPQ
--0 new/1 old msgs--matrix-->

Fixed formatting, I hope!

[Dave van der Locht]

I've just verified the issue and can confirm it's a bug.

Need to do some debugging to see why reporting is wrong or why LinFBB thinks it's still forwarding and pinpoint + fix the exact cause.

The 'already connected' part of the message looks to be wrong too as the checking mechanism seems to look at a forwarding flag, not a connection state. Which explains why it isn't shown with the % command.