Subj : Weekly nodelist report on noteworthy changes (290) To : Michiel van der Vlist From : Andrew Leary Date : Sun Oct 18 2020 01:18:40 Hello Michiel! 17 Oct 20 14:49, you wrote to me: MV> I send another ping to 1:320/319, routed via 1:320/119. Time 08:11 MV> UTC. No bounce this time, but over four hours after the fact no Pong MV> from 1:320/319 either. Also no trace from 1:320/119. You use O-T/Track MV> for the bounce, so it is a reasonable assumption that you use O-T for MV> the Ping as well. I don't use O-T any more, apart from the fact that MV> it is 16 bit abandonware, it does not cooperate well with BSO. But in MV> the past, I managed to make it Ping, but never Trace. 1:320/119 is still running OS/2, and does use O-T/Track for the Ping function. MV> It seems for historic reasons that I route mail for you nick of the MV> woods via 1:320/119. That must be a remnant from time that 119 was MV> your only listed node number. I will change the routting to go via MV> 1:320/219 and try again. Later I will try a direct connect with 319. 1:320/219 is my main node these days; while 1:320/319 is a test system for MBSE, so that hopefully the major bugs are squashed before they affect my production system. MV> As an aside... You still use diffs? I was stopped using diffs ages MV> ago. I use the full sized lists. I do make the diff available fir MV> anyone interseted, but there are no takers. Also I do not use the MV> weekly nodelist. I use Z2DAILY and DAILYUTF for anythng needing a MV> nodelist. Uncompressed. Binkd does fine with its internal MV> compreesion... I use the weekly nodelist and diff here mainly to ensure that the software still supports it correctly. I do copy my region segment into MBSE's nodelist directory so that newly added nodes in my region are listed here before they make the weekly nodelist. MV> Ping to 1:320/319 routed via 219 timed 12:47 UTC I'll take a look in the logs. Andrew --- GoldED+/LNX 1.1.5-b20180707 * Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219) .