Hello mark,

On Saturday June 09 2018 13:51, you wrote to me:

 ml>>> how can the NC respond to a 9999 number if it is not in the
 ml>>> nodelist and their software enforces nodelist lookups?

 MV>> Use a private nodelist segment with the 9999 entry and the
 MV>> connect data for that application.

 ml> is the nodelist not good enough to use if the entry is already there?
 ml> maybe they're working on their connections with other members of the
 ml> network?

I know you like to play devil's advocate, but this must have been one of your
off days. Surely you can do better than that?

No, of course the entry in the nodelist is not good enough. It does not list
any contact info at all, so an override of some kind is needed anyway for
establishing a connection with the applicants system.

Other than that, the reason NlCheck flagged it as "error" is not the presence
of the 9999 number as such, but the fact that Pvt is missing.

 MV>> BTW, how does the NC repsond to an application coming from -1/-1
 MV>> when his software does not support negative net- and node
 MV>> numbers?

 ml> that's easy... it is rolled over and displayed as 32767/32676...

Considering that you had an off day, I will forgive the 767|676 typo.

Yes, in a 15 bit system, -1 may be representated as 32767. But 15 bit systems
are not all that common in Fidonet. 16 or 32 bit systems are more common. In
those it would be 65535 or 4294967295.

I say "may" because I have yet to see nodenumber handling software that allows
entering -1 as a node or net number. Binkd rejects it. Fmail rejects it. Maybe
TJ's original Fido could handle it.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303