Subj : Weekly nodelist report on noteworthy changes (290)
To   : Andrew Leary
From : Michiel van der Vlist
Date : Sun Oct 18 2020 11:56:30

Hello Andrew,

On Sunday October 18 2020 01:18, you wrote to me:


 AL> 1:320/119 is still running OS/2, and does use O-T/Track for the Ping
 AL> function.

Ah, that explains why it is still IPv4 only. ;-)

Here I let Fmail handle PING and TRACE. Works for me. :)

 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.

 AL> 1:320/219 is my main node these days;

OK, so from now on I will treat it as such.

 AL> while 1:320/319 is a test system for MBSE, so that hopefully the major
 AL> bugs are squashed before they affect my production system.

Understood.

 MV>> As an aside... You still use diffs? I was stopped using diffs
 MV>> ages ago. I use the full sized lists. I do make the diff
 MV>> available fir anyone interseted, but there are no takers. Also I
 MV>> do not use the weekly nodelist. I use Z2DAILY and DAILYUTF for
 MV>> anythng needing a nodelist. Uncompressed. Binkd does fine with
 MV>> its internal compreesion...

 AL> I use the weekly nodelist and diff here mainly to ensure that the
 AL> software still supports it correctly.  I do copy my region segment
 AL> into MBSE's nodelist directory so that newly added nodes in my region
 AL> are listed here before they make the weekly nodelist.

But not for 119 and 219?

 MV>> Ping to 1:320/319 routed via 219 timed 12:47 UTC

 AL> I'll take a look in the logs.

I will do some more ping tests...

Later...

Got a quick Pong responce from 1"320/219 and a quick trace response from 1:320/219 o pings to 119 and 319.

Still waiting for the Pong from 119 and 319.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
 * Origin: Nodelist Police Station (2:280/5555)

.