[HECnet] Feeling somewhat isolated here in area 29

supratim sanyal supratim at riseup.net
Mon Oct 29 11:11:45 PDT 2018


Makes sense, I saw this and was trying to figure out why UDP is coming in. All good, then.

952 937  84.160537 82.70.71.174 -> 172.30.0.184 UDP 58 Source port: 64355  Destination port: 60003

Thanks
Supratim


Sent from Mail for Windows 10

From: Keith Halewood
Sent: Monday, October 29, 2018 14:09
To: hecnet at Update.UU.SE
Subject: RE: [HECnet] Feeling somewhat isolated here in area 29

Sorry about all that! I think multinet went back to decnet over tcp/ip defaults when I created another circuit. It’s all up and running now.

Keith

From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Keith Halewood
Sent: 29 October 2018 17:57
To: hecnet at Update.UU.SE
Subject: RE: [HECnet] Feeling somewhat isolated here in area 29

Hi,

I’m coming in from 82.70.71.174. I can ping you fine, from the container and from the vax instance. I’ve rebooted the instance… it still doesn’t appear to be connecting though.

Keith


From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of supratim sanyal
Sent: 29 October 2018 17:46
To: hecnet at Update.UU.SE
Subject: RE: [HECnet] Feeling somewhat isolated here in area 29

Keith,

IMPVAX seems to be alive and well with two other MULTINET links connected. Can you ping 52.23.221.223 successfully?

Also what IP are you coming in from?

$ mc ncp show active circuits


Active Circuit Volatile Summary as of 29-OCT-2018 17:41:34

   Circuit          State                   Loopback     Adjacent
                                              Name      Routing Node

  QNA-1             on                                1.550 (QCOCAL)
  TCP-0-0           on                                1.13 (MIM)
  TCP-0-1           on
  TCP-0-10          on       -synchronizing
  TCP-0-2           on                                1.750
  TCP-0-3           on                               39.1 (MASON)
  TCP-0-4           on       -synchronizing
  TCP-0-5           on       -synchronizing
  TCP-0-6           on       -synchronizing
  TCP-0-7           on       -synchronizing
  TCP-0-8           on       -synchronizing
  TCP-0-9           on       -synchronizing
$
$ mc ncp tell legato show exec


Node Volatile Summary as of 29-OCT-2018 17:41:51

Executor node = 2.1 (LEGATO)

State                    = on
Identification           = DECnet for OpenVMS VAX V7.3


$ mc ncp tell mim show exec


Node Volatile Summary as of 29-OCT-2018 17:42:00

Executor node = 1.13 (MIM)

State                    = on
Identification           = "RSX system at Update, Sweden"


$ mc ncp tell 1.750 show exec


Node Volatile Summary as of 29-OCT-2018 17:42:18

Executor node = 1.750

State                    = on
Identification           = SIMH VAX


$ mc ncp tell mason show exec


Node Volatile Summary as of 29-OCT-2018 17:42:31

Executor node = 39.1 (MASON)

State                    = on
Identification           = HP DECnet for OpenVMS Alpha


$

Sent from Mail for Windows 10

From: supratim sanyal
Sent: Monday, October 29, 2018 13:36
To: hecnet at Update.UU.SE
Subject: RE: [HECnet] Feeling somewhat isolated here in area 29

Looking at what happened to IMPVAX now.

Supratim

Sent from Mail for Windows 10

From: Keith Halewood
Sent: Monday, October 29, 2018 12:49
To: hecnet at Update.UU.SE
Subject: [HECnet] Feeling somewhat isolated here in area 29

Hi,

I have a TCP (via multinet) connection to IMPVAX which is hardly ever down. It is at the moment.
Anybody else willing to give me some links to other areas?

Regards,

Keith



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sonic.net/pipermail/hecnet-list/attachments/20181029/c91eb77f/attachment-0001.html>


More information about the Hecnet-list mailing list