[HECnet] *** Very important information ***

[Johnny Billquist]

You might have been unlucky and caught things exactly at a point where I 
restarted decnet-1-1023. Since it's PyDECnet, any changes in 
configuration requires a restart, and I'm doing changes to the config 
quite often right now.

   Johnny

On 2021-11-22 17:05, Thomas DeBellis wrote:
> Then I think I got a false negative from the 36 bit DECnet 'ping' utility.
> 
>     NETPTH>*venti*
> 
>     [Routing path from VENTI2 (2.522) to VENTI (2.20)]
> 
>       From              Via        Back          Thru       Cost    Hops
>     VENTI2 (2.522)    =>NI-0-0   /BRG-0   <=    A2RTR (2.1023)      5      2
>     A2RTR  (2.1023)   =>DUP-1    /KDP-0-0 <=    VENTI (2.20)       -1     -1
> 
>     NETPTH>*mim*
> 
>     [Routing path from VENTI2 (2.522) to MIM (1.13)]
> 
>       From              Via        Back          Thru         Cost    Hops
>     VENTI2 (2.522)    =>NI-0-0   /BRG-0   <=    A2RTR (2.1023)       
>     -1    -1
>     A2RTR  (2.1023)   =>MUL-1    /
>     ?NETPTH NTMAN failed, reason:
>     Parameter missing
> 
> I immediately tested with the node fetch batch job and it worked fine:
> 
>     10:38:42 USER MIM::DU1:[DECNET]
>     10:38:42 USER   FIX.T20;122;P775656             17 33280(8)  
>     21-Nov-2021 23:00:10
> 
> 
> On 11/22/21 11:02 AM, Johnny Billquist wrote:
>> Hi. MIM will continue to be the source. And now Mim.Update.UU.SE is a 
>> CNAME to Mim.Stupi.NET, so hopefully nothing needs to change anywhere.
>>
>>   Johnny
>>
>> On 2021-11-22 16:58, Thomas DeBellis wrote:
>>> Hi Johhny,
>>>
>>> Will MIM continue to be the online source of record for the T20.CMD 
>>> node list?  Or should I go elsewhere to fetch it?
>>>
>>> --T
>>>
>>> On 11/22/21 10:52 AM, Johnny Billquist wrote:
>>>> On 2021-11-22 16:51, Robert Armstrong wrote:
>>>>>> Peter Lothberg <roll at stupi.com> wrote:
>>>>>> hecnet-1023, 192.108.202.70  is UP but I drop all packets towards 
>>>>>> it that
>>>>>> are not HECnet tunnels in one or the other form.. (linux.....)
>>>>>
>>>>>    Did you include Multinet in your rules?
>>>>>
>>>>>    A2RTR used to have a Multinet tunnel to MIM (Johnny's RSX TCP/IP 
>>>>> stack supports that), and when I change it to
>>>>>
>>>>>     circuit MUL-1 Multinet hecnet-1-1023.stupi.net:700:connect 
>>>>> --cost=12
>>>>>
>>>>> it doesn't connect.  FWIW, the previous connection was
>>>>>
>>>>>     #circuit MUL-1 Multinet mim.update.uu.se:700:connect --cost=12
>>>>
>>>> Sorry, that would be my fault. I saw that Peter had some comments 
>>>> about links to you in the config, so I didn't do anything. Let me 
>>>> set you up as with Mim before then, but to hecnet-1-1023. In a sec...
>>>>
>>>>   Johnny
>>>>
>>

-- 
Johnny Billquist                  || "I'm on a bus
                                   ||  on a psychedelic trip
email: bqt at softjar.se             ||  Reading murder books
pdp is alive!                     ||  tryin' to stay hip" - B. Idol