Subj : Possible bug using mbfido no
To : Andrew Leary
From : Vincent Coen
Date : Sat Mar 01 2025 04:45 pm
Hello Andrew!
28 Feb 25 20:43, I wrote to you:
I have now added Sean Rima to the (so far) Z2DAILY nodelist as it was sent in
too late for entry to the main NODELIST system, but that will happen for next
Friday's one.
So Sean has added the AKA 250/101 and sent in requests for linking in to some
ECHO areas and it seams to be working - no real surprises there.
I do not follow the logic being used in mbse here as I am not the only one
running more that one net as there are a few around both in the USA and
Europe.
That said Michael may not have thought of that being a possibility when coding
the notify and areamgr / filemgr routines.
To my mind have the primary AKA in my case 250/1 at position 1 in the AKA
lists
should not be in the way of processing these requests as it would still be
valid for all connected nodes, yes ?
Clearly the fact that I have an AKA in the net the same as the subject node is
where mbse is confusing it but do not see why !
Ideas ?
Vincent
> Hello Andrew!
> 15 Feb 25 15:29, I wrote to you:
> As a follow on from previous msg regarding issues when using mbfido no
> on a secondary fido address at 2:263/1 where the infor sent is - well
> broken such as :
> Dear Sean Rima:
> The following is a flow report of all message areas
> Group @G @J (@I)
> P O S T E D R E C E I
> V E D Message area Last week Last month Last week
> Last Month - ------------------------------ ----------
> ---------- ---------- ----------
> With the rest blank I suspect that it relates to the address of the
> node is not in 2:25 or 2:250.
> I am going to try and allocate a new node address 2:0/101 as an aka to
> 263/1 and see if that fixes it - just have to remember to route such
> to 2:263/1 though.
> Will advise.
> Vincent
Vincent
--- Mageia Linux v9 X64/Mbse v1.1.0/GoldED+/LNX 1.1.5-b20240309
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
