Subj : Not find zone 1, 3 and 4
To   : Wilfred van Velzen
From : mark lewis
Date : Tue Jul 14 2026 10:31 am


 On 2026 Jul 14 15:13:32, you wrote to me:

 ml>> #######################################
 ml>> # include all known FTN networks list #
 ml>> #######################################
 ml>> include /sbbs/ftn/nodelist/binkd-networks.conf

 WV> I don't think this will help prevent the warnings that Angel is seeing in
 WV> his log. But who knows, let him try it... ;-)

true... i did also mention the problem may be the remote(s) not presenting 
their FTN domain(s) in their address list when the connection is made... that's 
a problem on the remote end and Angel doesn't show us the portion above these 
lines which tells the remote being connected to...

 ml>> the list is pretty accurate and has been built over years of binkd
 ml>> connections with systems flying othernet addresses... yes, some/many
 ml>> of these old FTNs may not exist any more... it doesn't hurt anything
 ml>> to keep them listed and it is the only remaining list i know of for so
 ml>> many of the FTN othernets that existed...

 WV> There is a public spreadsheet on google docs with a list of FTN networks:

 WV> https://docs.google.com/spreadsheets/d/17pmf7cS9ocU99Rm6qlJD_OncqmbDI5Qj8Yw
 WV> 99A5bgVc/edit#gid=0

i remember there being a sheet but i haven't looked it over in a long while... 
i trust my list a little more, though, because i do update it when i see a new 
FTN domain pop up in my binkd logs... with a very similar error message, too 
:wink:

)\/(ark

"The soul of a small kitten in the body of a mighty dragon. Look on my majesty, 
ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a shiny thing!"
.... Psychoceramics: The study of crackpots.
---
 * Origin:  (1:3634/12.73)

.