= Сообщение: 4108 из 7124 ====================================== FTSC_PUBLIC = От : mark lewis 1:3634/12.73 09 Dec 18 14:28:40 Кому : Markus Reschke 09 Dec 18 14:28:40 Тема : Candidates vision request FGHI : area://FTSC_PUBLIC?msgid=1:3634/12.73+5c0d6d67 На : area://FTSC_PUBLIC?msgid=2:240/1661+5bfd8f7d = Кодировка сообщения определена как: CP437 ================================== ==============================================================================
On 2018 Dec 09 19:32:22, you wrote to me:
MR>>> So it would extract additional addresses which aren't intended for MR>>> binkp for a node entry following the FTSC docs (if listed take just MR>>> the address in the IBN flag).
ml>> wrong... it extracts the domain from the "system name" field, the INA ml>> flag(s) and the IBN flag(s)... the domains listed in the "system name" ml>> field and the INA flags are default domains to attempt a connection ml>> with... they are valid to use if the domains attached to any IBN flags ml>> fail to connect...
MR> Sorry, you got that totally wrong.
no i didn't... i explained how binkd_nodelister.pl pulls the domains from the St.Louis nodelist lines...
MR> We're talking about the way multiple addresses are listed in the IBN MR> and INA flags.
i know this... the "system name" field must also be considered since it was the first "default" domain to use...
MR> And we found out that there are two ways, one documented in a FTSC doc MR> and the other one undocumented.
ARAICT, they are all documented right there in FTS-5001.006 and they're all perfectly viable and operational...
)\/(ark
Always Mount a Scratch Monkey Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong... ... My idea of housework is to sweep the room with a glance. --- * Origin: (1:3634/12.73)
