Hello all,
Just added a simh vax 11/780 to HECnet node 31.270 (FATTY) . Circuit is up. Using the copy known nodes command I get "unable to connect to listener" error. Any thoughts on this?
Thank you,
Brian.
Hi,
I've just noticed that nodes 29.600-699 had been allocated to someone and they've since disappeared from the HECnet node database... or possibly I imagined the whole thing... except for the fact that I had an inbound multinet circuit for nodes in that range. I've just removed the circuit and the firewall ACL for incoming on TCP port 9604. The circuit hadn't been used in some time.
In no other particular order of peers:
29.400-403 (Ales Petan) has been gone a while.
29.450-469 (Trevor Warwick) similarly.
46.1-9 (Douglas Hall) has been gone for quite a long time.
52.* (Brian Hechinger) has been down for a few weeks... and has changed incoming IP address once or twice too.
I'm not complaining, just wondering. Known areas are going dark at a rate greater than 0 too.
Oh, and ANKE (1.1023) went >BANG< a few days ago.
Regards
Keith
Hi, I have a couple of strange issues on RSX-11M-PLUS with the latest TCP/IP stack (build 14-FEB-2023 00:19).
1) If I create a LB{1,2]SYSLOGIN.CMD with a couple of entries such as:
set /named
set /vt2xx=ti:
when I login, it executes the commands but then I can type nothing at all into the terminal screen, it is completely frozen.
2) When I try to send an e-mail (I think it is set up OK), it gives the following error:
>SEN
To: PETER.WHISKER(a)GMAIL.COM
Connection to local node:: failed,
CONN STATUS= 2 STATUS2= 0
SENT0 -- STOP ERROR
The [IPLOG]MAILD.LOG shows:
Sun, 19 Feb 2023 09:47:58 (MAI.0) MAIL11 got connection from CLIONA:: (Unknown M
AIL11 V3.0)
Sun, 19 Feb 2023 09:47:58 (MAI.0) Connection lost
I'm a bit lost as to how to debug this further - has anyone else encountered it or can Johnny shed any light?
Thanks
Peter Whisker
Hi,
I'm attempting to connect to the area 29 node and Keith Halewood has very helpfully set me up with a listener.
I've been getting a strange error on the Multinet link and updated to the latest BQ-IP from December 2022 before posting this. I continue to have the same problem after the update.
My IP stack is fine - I can ping and get the NTPDATE time and I can access my RSX11M system via Telnet.
The Node has the right area and number and I can access it from the other node using RMT.
However when I try to bring up the link to HECNet I keep getting this error repeating:
>NCP SET CIR IP-0-0 STA ON
14:29:03 COT -- Date is 13-FEB-2023
14:29:03 MLTNET V1.27 starting.
>
>
14:29:05 MLTNET - IP-0-0 XMIT fail. IOSB=-3
14:29:10 MLTNET - IP-0-0 XMIT fail. IOSB=-3
I can see the traffic leaving on my DSL router to the Area 29 router and the replies coming back. So I am bit mystified. I think IOSB error -3 is IE.DNR - Device not ready?
Node details:
>NCP SHO KNO NOD
Known nodes summary as of 13-FEB-2023 14:32:39
Executor node = 29.850 (CLIONA)
State = On, Identification = CLIONA RSX11M+ V4.6
Remote Active Next
Node State Links Delay Circuit Node
29.1 (A29RT1) Unreachable
29.2 (A29RT2) Unreachable
29.852 (SADHBH) Reachable UNA-0 29.852 (SADHBH)
Below is recent correspondence - I will post it hear as it may be helpful:
Hi
It’s set up as a “Level 2 router” – perhaps that is the problem? I’ve looped in Johnny in case he has an idea where the problem may be?
Regards
Peter
>; =====================================================================
>; DEC - Section 1 - Define the target and remote nodes
>; =====================================================================
>;
>; Generating node 29.850 (CLIONA), Id = CLIONA RSX11M+ V4.6
>; Node type is level 2 router
>; Highest node number in network is 1023
>; Highest area number in the network is 63
>; Network command terminal and layered product support will be included
>; The MACRO-11 and FORTRAN/COBOL/BASIC+2 user libraries will be supplied
>;
>; The remote node names are:
>; 29.852 (SADHBH)
>; 29.2 (A29RT2)
>; 29.1 (A29RT1)
>;
>; <EOS> Do you want to:
>* <RET>-Continue, S-Skip, R-Repeat section, P-Pause, E-Exit [S]:
>;
>;
From: Keith Halewood <Keith.Halewood(a)pitbulluk.org>
The only thing I can think of is DECnet with more than 1 interface needs to be an L1 router and not an endnode. Other than that, I’m not at all familiar with RSX and Johnny’s IP stack.
From: Peter Whisker [mailto:peter@whisker.org.uk]
I'm getting IOSB error -3 which I think may be IE.DNR Device not ready. I can see the IP traffic going out and back on the interfaces both sides of my router. I need to check if I've missed some DECnet configuration.
On Mon, 13 Feb 2023, 10:39 Keith Halewood, <Keith.Halewood(a)pitbulluk.org> wrote:
I can see your connection attempts. The DECnet router 29.2 is reporting ‘unexpected packet type’, adjacent node 29.850, packet header 01 29.850
Hi,
I have 20 years experience of PDP-11s and RSX-11M in particular which I haven't used much since 2000, so I have decided to brush up again and have spun up a couple of RSX-11M-PLUS 4.6 nodes in simh. They are happily chatting away over BQ-IP and LAT and I guess the next stage is to request a connection to HECnet. My two geographically nearest node areas are Northolt (UK) and London (UK) - both within 30km of me.
It looks like Northolt area 29 (Keith Halewood) might have a main routing node. London is in area 8 with admin Sampsa Laine. I'm just wondering if either of these areas allow new connections ot what is the best way to go?
Many thanks
Peter Whisker
Addlestone, Surrey UK.
FYI - AWS is doing maintenance on 2/27/2023 at 8AM GMT so A2RTR will be down. That's the middle of the night/very early morning for us here in the USA.
Bob
-----Original Message-----
From: Amazon Web Services, Inc. [mailto:no-reply-aws@amazon.com]
Sent: Friday, February 10, 2023 2:03 PM
To: bob(a)sparetimegizmos.com
Subject: Scheduled maintenance for Amazon Lightsail instances on Mon, 27 Feb 2023 08:00:00 GMT
Dear Amazon Lightsail Customer,
One or more of your Amazon Lightsail instances is scheduled for maintenance in a 2 hour window starting on Mon, 27 Feb 2023 08:00:00 GMT.
Maintenance activity will result in the following Lightsail instance(s) in the us-west-2 region to be unavailable and then rebooted:
HECnet
If you have any questions or concerns please contact the AWS Support Team on the community forums and via AWS Premium Support at: http://aws.amazon.com/support
Sincerely,
Amazon Lightsail Team
Amazon Web Services, Inc. is a subsidiary of Amazon.com, Inc. Amazon.com is a registered trademark of Amazon.com, Inc. This message was produced and distributed by Amazon Web Services Inc., 410 Terry Ave. North, Seattle, WA 98109-5210
