Subj : Re: Weekly nodelist report on noteworthy changes (255)
To   : Andrew Leary
From : Nodelist Police Commissioner
Date : Sat Sep 12 2020 11:47:04

Hello Andrew,

On 2020-09-12 02:23:43, you wrote to me:

 NC>>>> New hostname for host and node:
 NC>>>> Host,322,Mass_Net_Central,Central_MA,Carlos_Roldan,-Unpublished-
 NC>>>> ,300, C M,INA:necrobbs.ddns.net,IBN:24556
 NC>>>> ,756,Necronomicon_BBS,NewBedford_MA,
 NC>>>> Carlos_Roldan,-Unpublished-,300,CM,INA:necrobbs.ddns.net,IBN

 NC>>>> connect to address 75.67.168.60: No route to host

 MvdV>>> Confirmed.

 MvdV>>> I still don't get it. Is it really that hard to test it before
 MvdV>>> submitting it to the nodelist?!

 NC>> In this case it's probably not the hostname that is the problem. 'No
 NC>> route to host' most of the time means there is no system on that IP.
 NC>> So maybe his dynamic IP already changed...

 AL> I've had both incoming and outgoing sessions with 1:322/0@fidonet on
 AL> that IP today.  Perhaps there is an IP routing problem between your
 AL> ISP and his?

I can now connect to his system too, so it was a temporary problem...

However I do notice he still shows his AmigaNet AKA on his 1:322/756 node, while he left AmigaNet ages ago on his own accord. :-(


Regards, NPC.

--- FMail-lnx64 2.1.0.18-B20170815
 * Origin: NPC Station (2:280/464)

.