[HECnet] MIM?

Paul Koning paulkoning at comcast.net
Tue Oct 23 06:51:18 PDT 2018



> On Oct 23, 2018, at 3:54 AM, Johnny Eriksson <bygg at cafax.se> wrote:
> 
> supratim sanyal wrote:
> 
>> Johnny,
> 
> The other Johnny will now give a short answer:
> 
>> I am suddenly seeing this from IMPVAX. Not sure what to make of this
>> 
>> $ dir mim::
>> %%%%%%%%%%%  OPCOM  23-OCT-2018 04:15:10.77  %%%%%%%%%%%
>> Message from user DECNET on IMPVAX
>> DECnet event 4.18, adjacency down
>> From node 1.559 (IMPVAX), 23-OCT-2018 04:15:10.77
>> Circuit TCP-0-0, Unexpected packet type, Adjacent node = 1.13 (MIM)
>> Packet beginning = 010D040140020200002C010000000000
> 
> The packet in question is an init packet, used to start up a link.
> 
> If tcpdump knew about this, it would look somewhat like:
> 
>  Init, 1.13 info 01 size 576 ver 2/0/0 timer 300
> 
> Why MIM decided to restart the link is another question.

I would guess that is a Multinet link, right?  A conforming DECnet implementation would not send an init message without restarting the data link layer first, which would produce a "circuit down" event.  So the unexpected packet type is indeed a reasonable complaint for it to generate.

	paul





More information about the Hecnet-list mailing list