Virtual Private Server (VPS) Hosting provided by Central Point Networking cpnllc.com
For some reason, the "Nodelist" and "Recent Callers" features are not working.
| Sysop: | Ray Quinn |
|---|---|
| Location: | Visalia, CA |
| Users: | 60 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 03:46:48 |
| Calls: | 12 |
| Files: | 12,929 |
| Messages: | 98,349 |
Check out the US 99 menu above for links to information about US Highway 99, after which the US 99 BBS is named.
Be sure to click on the Amateur Radio menu item above for packet BBSes, packet software, packet organizations, as well as packet how-to's. Also included is links to local and some not-so-local Amateur Radio Clubs.
Just did a notify using mbfido no 2:263/1
Node reports that the netmails come from 2:263/0
Now my AKAs are as set up :
1 2:250/1@fidonet 11
2 2:25/21@fidonet 12
3 2:250/0@fidonet 13
4 2:25/0@fidonet 14
5 2:263/0@fidonet 15
This is because I am the Host for region 2:25 and therefore 2:250 and 2:263
My primary node is 2:250/1 and 2:25/21 is used for the Elist software.
As region 25 is the UK including Northern Ireland but Southern Ireland
is an independent country it has its own net as 2:263 and there are 2 nodes present .1 and .5. and I am the host at 2:263/0 as that has to
be defined in the nodelist.
I have had a look at the source code at mbfido / notify.c and I cannot
see where it obtains system AKA from but at a guess it is the last one
so how do I tell mbfido no to use the first entry (2:250/1) ?
I did a mbfido no 2:250/1 but that did not produce anything, then did
a mbfido no 2:25/21 then unpacked the archive being sent to that
address as the system reported all AKA's are locked - reasonably as it
was trying to send to itself. So moved over the pkt and let mbse deal
with it into my netmail inbox area for 250/1 (I have 2 more one for
25/21 and one for 25/0 & 25/21 and no I have no idea who two different akas are being used as : NETMAIL is set Fido Aka 2:250/1 all traffic to/from me at 250/1. NETMAIL2 is set Fido Aka 2:25/0 for Z2 netmail traffic. NETMAIL3 is set Fido Aka 2:25/21 for the Elist AKA 25/21.
The only conclusion I can draw is that the problem netmail sent from MBFIDO NO uses the Last AKA but I cannot define what one is used so
the question is how do I fix it without breaking the other two Netmail
msg areas.
Hope I have made this clear but if you have a query regarding all
this, fire away.
Vincent
Hello Vincent!
14 Feb 25 17:35, you wrote to all:
Just did a notify using mbfido no 2:263/1
Node reports that the netmails come from 2:263/0
Now my AKAs are as set up :
1 2:250/1@fidonet 11
2 2:25/21@fidonet 12
3 2:250/0@fidonet 13
4 2:25/0@fidonet 14
5 2:263/0@fidonet 15
This is because I am the Host for region 2:25 and therefore 2:250
and
2:263
My primary node is 2:250/1 and 2:25/21 is used for the Elist
software. As region 25 is the UK including Northern Ireland but
Southern Ireland is an independent country it has its own net as
2:263 and there are 2 nodes present .1 and .5. and I am the host
at 2:263/0 as that has to be defined in the nodelist.
I have had a look at the source code at mbfido / notify.c and I
cannot see where it obtains system AKA from but at a guess it is
the last one so how do I tell mbfido no to use the first entry
(2:250/1) ?
I did a mbfido no 2:250/1 but that did not produce anything,
then did a mbfido no 2:25/21 then unpacked the archive being sent
to that address as the system reported all AKA's are locked -
reasonably as it was trying to send to itself. So moved over the
pkt and let mbse deal with it into my netmail inbox area for
250/1 (I have 2 more one for 25/21 and one for 25/0 & 25/21 and
no I have no idea who two different akas are being used as :
NETMAIL is set Fido Aka 2:250/1 all traffic to/from me at 250/1.
NETMAIL2 is set Fido Aka 2:25/0 for Z2 netmail traffic. NETMAIL3
is set Fido Aka 2:25/21 for the Elist AKA 25/21.
The only conclusion I can draw is that the problem netmail sent
from MBFIDO NO uses the Last AKA but I cannot define what one is
used so the question is how do I fix it without breaking the
other two Netmail msg areas.
Hope I have made this clear but if you have a query regarding all
this, fire away.
Vincent
MBSE defaults to using the closest AKA to the destination. For
2:263/1, that would be 2:263/0. There currently isn't a way to
override which AKA is used. I am considering adding support for this,
but it'll take a while to get that done and debugged.
I do recommend that you setup a NetMail area for every AKA your system
has. This insures that MBFIDO has a place to put incoming netmail for
any of your system's AKA addresses.
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