11 Aug
2018
11 Aug
'18
6:15 a.m.
OK, so who is "SANYAL" at node 1.550? If you'd like an account on my RSTS/E
system, all you need do is ask. I'm one of those sys admins who actually
reads his event logs. :)
Regards,
Mark
11 Aug
11 Aug
4:41 p.m.
Hi Mark,
I have DCL script generating this web page once a week - perhaps you see this pinging your
system? Or maybe I was looking for a guest account many months ago for some reason I can?t
remember.
http://sanyalnet-openvms-vax.freeddns.org:82/falserver/hecnet-status.html
Supratim Sanyal
Germantown, MD
On Aug 11, 2018, at 12:15 AM, Mark Abene <phiber at
phiber.com> wrote:
OK, so who is "SANYAL" at node 1.550? If you'd like an account on my RSTS/E
system, all you need do is ask. I'm one of those sys admins who actually reads his
event logs. :)
Regards,
Mark
12 Aug
12 Aug
4:55 a.m.
This was a recent attempt. It's not a huge big deal. I don't have public
guest accounts, but I would make someone a personal account if they asked
nicely.
Honestly mapping the whole network seems a little redundant, since Johnny
already does that and the information is reasonably up to date on his web
site.
-Mark
On Sat, Aug 11, 2018 at 7:41 AM, Supratim Sanyal <supratim at riseup.net>
wrote:
Hi Mark,
I have DCL script generating this web page once a week - perhaps you see
this pinging your system? Or maybe I was looking for a guest account many
months ago for some reason I can?t remember.
http://sanyalnet-openvms-vax.freeddns.org:82/falserver/hecnet-status.html
Supratim Sanyal
Germantown, MD
On Aug 11, 2018, at 12:15 AM, Mark Abene <phiber at phiber.com> wrote:
OK, so who is "SANYAL" at node 1.550? If you'd like an account on my
RSTS/E system, all you need do is ask. I'm one of those sys admins who
actually reads his event logs. :)
Regards,
Mark
5:23 a.m.
Mark - this makes me a bit worried since I have not had a chance to get on HECnet for at
least a month. What was the date/time you see logged?
Supratim
On Aug 11, 2018, at 10:55 PM, Mark Abene <phiber at
phiber.com> wrote:
This was a recent attempt. It's not a huge big deal. I don't have public guest
accounts, but I would make someone a personal account if they asked nicely.
Honestly mapping the whole network seems a little redundant, since Johnny already does
that and the information is reasonably up to date on his web site.
-Mark
On Sat, Aug 11, 2018 at 7:41 AM, Supratim Sanyal
<supratim at riseup.net> wrote:
Hi Mark,
I have DCL script generating this web page once a week - perhaps you see this pinging
your system? Or maybe I was looking for a guest account many months ago for some reason I
can?t remember.
http://sanyalnet-openvms-vax.freeddns.org:82/falserver/hecnet-status.html
Supratim Sanyal
Germantown, MD
> On Aug 11, 2018, at 12:15 AM, Mark Abene <phiber at phiber.com> wrote:
>
> OK, so who is "SANYAL" at node 1.550? If you'd like an account on my
RSTS/E system, all you need do is ask. I'm one of those sys admins who actually reads
his event logs. :)
>
> Regards,
> Mark
>
8:14 a.m.
July 23rd. Only a couple of weeks ago...
Event type 34.0, Object spawned
Occurred 23-Jul-31 21:26:18.4 on node 61.151 (MARDUK)
Source node = 1.550
Source process = 0 SANYAL
Destination process = 19
User = 61,1
Password = ...
On Sat, Aug 11, 2018 at 8:23 PM, Supratim Sanyal <supratim at riseup.net>
wrote:
Mark - this makes me a bit worried since I have not
had a chance to get on
HECnet for at least a month. What was the date/time you see logged?
Supratim
On Aug 11, 2018, at 10:55 PM, Mark Abene <phiber at phiber.com> wrote:
This was a recent attempt. It's not a huge big deal. I don't have public
guest accounts, but I would make someone a personal account if they asked
nicely.
Honestly mapping the whole network seems a little redundant, since Johnny
already does that and the information is reasonably up to date on his web
site.
-Mark
On Sat, Aug 11, 2018 at 7:41 AM, Supratim Sanyal <supratim at riseup.net>
wrote:
Hi Mark,
I have DCL script generating this web page once a week - perhaps you see
this pinging your system? Or maybe I was looking for a guest account many
months ago for some reason I can?t remember.
http://sanyalnet-openvms-vax.freeddns.org:82/falserver/hecnet-status.html
Supratim Sanyal
Germantown, MD
On Aug 11, 2018, at 12:15 AM, Mark Abene <phiber at phiber.com> wrote:
OK, so who is "SANYAL" at node 1.550? If you'd like an account on my
RSTS/E system, all you need do is ask. I'm one of those sys admins who
actually reads his event logs. :)
Regards,
Mark
11:25 a.m.
On 2018-08-12 04:55, Mark Abene wrote:
Honestly mapping the whole network seems a little
redundant, since
Johnny already does that and the information is reasonably up to date on
his web site.
Well, that's not really true. I do not map, or try to keep some kind of
map of HECnet. I have my nodename database, which is entirely voluntary
to register nodes in, and I know that not all nodes on HECnet are in there.
In addition, this does not give much clue about how things are
connected, and for some machines, nothing more than the owner, name and
number is registered.
That said, I do not think it is realistic to automatically try to map
out HECnet anyway, so I think that any such attempts should be thought
about a second time, and probably be abandoned.
There are several problems with trying any kind of mapping. The first is
that there are no proper protocol that is suitable. NICE would be the
obvious first choice, but for example Cisco routers do not provide NICE
at all. And so, you can not traverse and follow connections that way.
There are no other way of just exploring what connections exist, so then
we instead have to resort to an exhaustive search of all node numbers,
using all kind of protocols a machine *might* answer to, which will
trigger all kind of logging events and possibly security systems getting
activated, which is not good.
Some kind of voluntary system is the only acceptable option I think. If
people want to, that could be a way. Possibly using FAL to explore and
find other nodes, but it would have to be based on lists of machines to
probe, which would need to be manually kept up to date.
Similar things have been attempted in the past, with mixed to poor
results, I would say.
Johnny
-Mark
On Sat, Aug 11, 2018 at 7:41 AM, Supratim Sanyal <supratim at riseup.net
<mailto:supratim at riseup.net>> wrote:
Hi Mark,
I have DCL script generating this web page once a week - perhaps you
see this pinging your system? Or maybe I was looking for a guest
account many months ago for some reason I can?t remember.
http://sanyalnet-openvms-vax.freeddns.org:82/falserver/hecnet-status.html
<http://sanyalnet-openvms-vax.freeddns.org:82/falserver/hecnet-status.html>
Supratim Sanyal
Germantown, MD
On Aug 11, 2018, at 12:15 AM, Mark Abene <phiber at phiber.com
<mailto:phiber at phiber.com>> wrote:
--
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
OK, so who is "SANYAL" at node
1.550? If you'd like an account on
my RSTS/E system, all you need do is ask. I'm one of those sys
admins who actually reads his event logs.? :)
Regards,
Mark
2:16 p.m.
Hi,
Regarding the mapping, you may have noticed the odd NML (I think) originating from here.
I've been parsing the output of areas, circuit/node/area adjacency and then the
script, such as it is, hops around and attempts the 'next stage' of discovery via
tell <node of interest> etc..
It has its obvious limitations - a snapshot of currently connected, lowest cost adjacency
(nodes and areas) but of course if a 'tell' is rebuffed by a node, then I can only
infer.
Regards,
Keith
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of
Johnny Billquist
Sent: 12 August 2018 10:25
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] My RSTS/E system...
On 2018-08-12 04:55, Mark Abene wrote:
Honestly mapping the whole network seems a little
redundant, since
Johnny already does that and the information is reasonably up to date
on his web site.
Well, that's not really true. I do not map, or try to keep some kind of map of HECnet.
I have my nodename database, which is entirely voluntary to register nodes in, and I know
that not all nodes on HECnet are in there.
In addition, this does not give much clue about how things are connected, and for some
machines, nothing more than the owner, name and number is registered.
That said, I do not think it is realistic to automatically try to map out HECnet anyway,
so I think that any such attempts should be thought about a second time, and probably be
abandoned.
There are several problems with trying any kind of mapping. The first is that there are no
proper protocol that is suitable. NICE would be the obvious first choice, but for example
Cisco routers do not provide NICE at all. And so, you can not traverse and follow
connections that way.
There are no other way of just exploring what connections exist, so then we instead have
to resort to an exhaustive search of all node numbers, using all kind of protocols a
machine *might* answer to, which will trigger all kind of logging events and possibly
security systems getting activated, which is not good.
Some kind of voluntary system is the only acceptable option I think. If people want to,
that could be a way. Possibly using FAL to explore and find other nodes, but it would have
to be based on lists of machines to probe, which would need to be manually kept up to
date.
Similar things have been attempted in the past, with mixed to poor results, I would say.
Johnny
-Mark
On Sat, Aug 11, 2018 at 7:41 AM, Supratim Sanyal <supratim at riseup.net
<mailto:supratim at riseup.net>> wrote:
Hi Mark,
I have DCL script generating this web page once a week - perhaps you
see this pinging your system? Or maybe I was looking for a guest
account many months ago for some reason I can?t remember.
http://sanyalnet-openvms-vax.freeddns.org:82/falserver/hecnet-status.html
<http://sanyalnet-openvms-vax.freeddns.org:82/falserver/hecnet-status.
html>
Supratim Sanyal
Germantown, MD
On Aug 11, 2018, at 12:15 AM, Mark Abene <phiber at phiber.com
<mailto:phiber at phiber.com>> wrote:
--
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
OK, so who is "SANYAL" at node
1.550? If you'd like an account on
my RSTS/E system, all you need do is ask. I'm one of those sys
admins who actually reads his event logs.? :)
Regards,
Mark
3:12 p.m.
Hi.
On 2018-08-12 14:16, Keith Halewood wrote:
Hi,
Regarding the mapping, you may have noticed the odd NML (I think) originating from here.
I've been parsing the output of areas, circuit/node/area adjacency and then the
script, such as it is, hops around and attempts the 'next stage' of discovery via
tell <node of interest> etc..
NML is properly called, as a protocol, NICE. Network Information and
Control Exchange, or something like that.
Accessing information through that does not normally generate any
logging information in RSX, and does not bother me. But as I mentioned
below, Cisco routers, for example, does not implement this protocol, so
you can't explore things beyond those points easily.
It has its obvious limitations - a snapshot of
currently connected, lowest cost adjacency (nodes and areas) but of course if a
'tell' is rebuffed by a node, then I can only infer.
By exploring adjacent nodes and known circuits, you'd get a more
complete picture, as it will also show you connections which are not the
lowest cost paths.
However, as I said, it will only give a partial picture anyway. I also
found out the other day that it don't seem like RSTS/E implements it
either, or maybe it depends on version and maybe it's optional.
Not sure how much Tops-10 supports either. And it might be even more
complex/limited with odd implementations, like the Linux hack.
Johnny
Regards,
Keith
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of
Johnny Billquist
Sent: 12 August 2018 10:25
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] My RSTS/E system...
On 2018-08-12 04:55, Mark Abene wrote:
--
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
Honestly mapping the whole network seems a little
redundant, since
Johnny already does that and the information is reasonably up to date
on his web site.
Well, that's not really true. I do not map, or try to keep some kind of map of
HECnet. I have my nodename database, which is entirely voluntary to register nodes in, and
I know that not all nodes on HECnet are in there.
In addition, this does not give much clue about how things are connected, and for some
machines, nothing more than the owner, name and number is registered.
That said, I do not think it is realistic to automatically try to map out HECnet anyway,
so I think that any such attempts should be thought about a second time, and probably be
abandoned.
There are several problems with trying any kind of mapping. The first is that there are
no proper protocol that is suitable. NICE would be the obvious first choice, but for
example Cisco routers do not provide NICE at all. And so, you can not traverse and follow
connections that way.
There are no other way of just exploring what connections exist, so then we instead have
to resort to an exhaustive search of all node numbers, using all kind of protocols a
machine *might* answer to, which will trigger all kind of logging events and possibly
security systems getting activated, which is not good.
Some kind of voluntary system is the only acceptable option I think. If people want to,
that could be a way. Possibly using FAL to explore and find other nodes, but it would have
to be based on lists of machines to probe, which would need to be manually kept up to
date.
Similar things have been attempted in the past, with mixed to poor results, I would say.
Johnny
-Mark
On Sat, Aug 11, 2018 at 7:41 AM, Supratim Sanyal <supratim at riseup.net
<mailto:supratim at riseup.net>> wrote:
Hi Mark,
I have DCL script generating this web page once a week - perhaps you
see this pinging your system? Or maybe I was looking for a guest
account many months ago for some reason I can?t remember.
http://sanyalnet-openvms-vax.freeddns.org:82/falserver/hecnet-status.html
<http://sanyalnet-openvms-vax.freeddns.org:82/falserver/hecnet-status.
html>
Supratim Sanyal
Germantown, MD
On Aug 11, 2018, at 12:15 AM, Mark Abene <phiber at phiber.com
<mailto:phiber at phiber.com>> wrote:
OK, so who is "SANYAL" at node
1.550? If you'd like an account on
my RSTS/E system, all you need do is ask. I'm one of those sys
admins who actually reads his event logs.? :)
Regards,
Mark
5:24 p.m.
On Aug 12, 2018, at 9:12 AM, Johnny Billquist <bqt
at softjar.se> wrote:
Hi.
On 2018-08-12 14:16, Keith Halewood wrote:
Both Tops-10 (v7.04) and Tops-20 (v7.1) have a pretty complete NICE
implementation although I was only able to check non-routing nodes - I
forget whether they support routing. The Linux hack has a very limited NICE
implementation - any attempt to show line or circuit information
returns ?No information in database?.
John.
Hi,
Regarding the mapping, you may have noticed the odd NML (I think) originating from here.
I've been parsing the output of areas, circuit/node/area adjacency and then the
script, such as it is, hops around and attempts the 'next stage' of discovery via
tell <node of interest> etc..
NML is properly called, as a protocol, NICE. Network Information and Control Exchange, or
something like that.
Accessing information through that does not normally generate any logging information in
RSX, and does not bother me. But as I mentioned below, Cisco routers, for example, does
not implement this protocol, so you can't explore things beyond those points easily.
It has its obvious limitations - a snapshot of
currently connected, lowest cost adjacency (nodes and areas) but of course if a
'tell' is rebuffed by a node, then I can only infer.
By exploring adjacent nodes and known circuits, you'd get a more complete picture, as
it will also show you connections which are not the lowest cost paths.
However, as I said, it will only give a partial picture anyway. I also found out the
other day that it don't seem like RSTS/E implements it either, or maybe it depends on
version and maybe it's optional.
Not sure how much Tops-10 supports either. And it might be even more complex/limited with
odd implementations, like the Linux hack.
Johnny
Regards,
Keith
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of
Johnny Billquist
Sent: 12 August 2018 10:25
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] My RSTS/E system...
On 2018-08-12 04:55, Mark Abene wrote:
--
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 Honestly mapping the whole network seems a little
redundant, since
Johnny already does that and the information is reasonably up to date
on his web site.
Well, that's not really true. I do not map, or try to keep
some kind of map of HECnet. I have my nodename database, which is entirely voluntary to
register nodes in, and I know that not all nodes on HECnet are in there.
In addition, this does not give much clue about how things are connected, and for some
machines, nothing more than the owner, name and number is registered.
That said, I do not think it is realistic to automatically try to map out HECnet anyway,
so I think that any such attempts should be thought about a second time, and probably be
abandoned.
There are several problems with trying any kind of mapping. The first is that there are
no proper protocol that is suitable. NICE would be the obvious first choice, but for
example Cisco routers do not provide NICE at all. And so, you can not traverse and follow
connections that way.
There are no other way of just exploring what connections exist, so then we instead have
to resort to an exhaustive search of all node numbers, using all kind of protocols a
machine *might* answer to, which will trigger all kind of logging events and possibly
security systems getting activated, which is not good.
Some kind of voluntary system is the only acceptable option I think. If people want to,
that could be a way. Possibly using FAL to explore and find other nodes, but it would have
to be based on lists of machines to probe, which would need to be manually kept up to
date.
Similar things have been attempted in the past, with mixed to poor results, I would say.
Johnny
>
> -Mark
>
>
> On Sat, Aug 11, 2018 at 7:41 AM, Supratim Sanyal <supratim at riseup.net
> <mailto:supratim at riseup.net>> wrote:
>
> Hi Mark,
>
> I have DCL script generating this web page once a week - perhaps you
> see this pinging your system? Or maybe I was looking for a guest
> account many months ago for some reason I can?t remember.
> http://sanyalnet-openvms-vax.freeddns.org:82/falserver/hecnet-status.html
> <http://sanyalnet-openvms-vax.freeddns.org:82/falserver/hecnet-status.
> html>
>
> Supratim Sanyal
> Germantown, MD
>
>
> On Aug 11, 2018, at 12:15 AM, Mark Abene <phiber at phiber.com
> <mailto:phiber at phiber.com>> wrote:
>
>> OK, so who is "SANYAL" at node 1.550? If you'd like an account
on
>> my RSTS/E system, all you need do is ask. I'm one of those sys
>> admins who actually reads his event logs. :)
>>
>> Regards,
>> Mark
>>
>
8:20 p.m.
Hi,
This is the sort of information I'm after (see attachment). A basic area connectivity
map.
X is just the same area connectivity
Y means there's direct evidence of area adjacency
R means there's indirect evidence, ie. a->b implies b->a but I can't see the
area list from b
? means 'maybe' somewhere here if only I could see from another node
So area 1 (row) is adjacent to itself (X) and areas 2,3,5,7,8,14,19,28,30,39,42,59 and 62
(Y)
Keith
PS. I sent the map as a screen image of my putty terminal because of non-fixed-width
characters etc..
Keith
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of
Johnny Billquist
Sent: 12 August 2018 14:12
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] My RSTS/E system...
Hi.
On 2018-08-12 14:16, Keith Halewood wrote:
Hi,
Regarding the mapping, you may have noticed the odd NML (I think) originating from here.
I've been parsing the output of areas, circuit/node/area adjacency and then the
script, such as it is, hops around and attempts the 'next stage' of discovery via
tell <node of interest> etc..
NML is properly called, as a protocol, NICE. Network Information and Control Exchange, or
something like that.
Accessing information through that does not normally generate any logging information in
RSX, and does not bother me. But as I mentioned below, Cisco routers, for example, does
not implement this protocol, so you can't explore things beyond those points easily.
It has its obvious limitations - a snapshot of
currently connected, lowest cost adjacency (nodes and areas) but of course if a
'tell' is rebuffed by a node, then I can only infer.
By exploring adjacent nodes and known circuits, you'd get a more complete picture, as
it will also show you connections which are not the lowest cost paths.
However, as I said, it will only give a partial picture anyway. I also found out the other
day that it don't seem like RSTS/E implements it either, or maybe it depends on
version and maybe it's optional.
Not sure how much Tops-10 supports either. And it might be even more complex/limited with
odd implementations, like the Linux hack.
Johnny
Regards,
Keith
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Johnny Billquist
Sent: 12 August 2018 10:25
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] My RSTS/E system...
On 2018-08-12 04:55, Mark Abene wrote:
--
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
Honestly mapping the whole network seems a little
redundant, since
Johnny already does that and the information is reasonably up to date
on his web site.
Well, that's not really true. I do not map, or try to keep some kind of map of
HECnet. I have my nodename database, which is entirely voluntary to register nodes in, and
I know that not all nodes on HECnet are in there.
In addition, this does not give much clue about how things are connected, and for some
machines, nothing more than the owner, name and number is registered.
That said, I do not think it is realistic to automatically try to map out HECnet anyway,
so I think that any such attempts should be thought about a second time, and probably be
abandoned.
There are several problems with trying any kind of mapping. The first is that there are
no proper protocol that is suitable. NICE would be the obvious first choice, but for
example Cisco routers do not provide NICE at all. And so, you can not traverse and follow
connections that way.
There are no other way of just exploring what connections exist, so then we instead have
to resort to an exhaustive search of all node numbers, using all kind of protocols a
machine *might* answer to, which will trigger all kind of logging events and possibly
security systems getting activated, which is not good.
Some kind of voluntary system is the only acceptable option I think. If people want to,
that could be a way. Possibly using FAL to explore and find other nodes, but it would have
to be based on lists of machines to probe, which would need to be manually kept up to
date.
Similar things have been attempted in the past, with mixed to poor results, I would say.
Johnny
-Mark
On Sat, Aug 11, 2018 at 7:41 AM, Supratim Sanyal <supratim at riseup.net
<mailto:supratim at riseup.net>> wrote:
Hi Mark,
I have DCL script generating this web page once a week - perhaps you
see this pinging your system? Or maybe I was looking for a guest
account many months ago for some reason I can?t remember.
http://sanyalnet-openvms-vax.freeddns.org:82/falserver/hecnet-status.
html
<http://sanyalnet-openvms-vax.freeddns.org:82/falserver/hecnet-status.
html>
Supratim Sanyal
Germantown, MD
On Aug 11, 2018, at 12:15 AM, Mark Abene <phiber at phiber.com
<mailto:phiber at phiber.com>> wrote:
OK, so who is "SANYAL" at node
1.550? If you'd like an account on
my RSTS/E system, all you need do is ask. I'm one of those sys
admins who actually reads his event logs.? :)
Regards,
Mark
9:28 p.m.
On Aug 12, 2018, at 9:12 AM, Johnny Billquist <bqt
at softjar.se> wrote:
Hi.
DECnet/E definitely implements NICE, has from the beginning (i.e., from when DECnet/E 2.0
which is the Phase III release was first shipped).
However, it need not be enabled as a known object. And if enabled, it may or may not
accept connections without access control variables (PPN/password). If not, you'll
get a reject indicating either no such object or bad access control. However, if the
connection is accepted you should find a full implementation.
Of course mapping information exists only in routers; if the node you're talking to is
an endnode it will only tell you who the adjacent designated router is (or the adjacent
nodes, on point to point circuits).
paul
...
By exploring adjacent nodes and known circuits, you'd get a more complete picture, as
it will also show you connections which are not the lowest cost paths.
However, as I said, it will only give a partial picture anyway. I also found out the
other day that it don't seem like RSTS/E implements it either, or maybe it depends on
version and maybe it's optional.
10:22 p.m.
On 2018-08-12 21:28, Paul Koning wrote:
In this case not enabled then, I think. Thanks for clarifying that it
exists. I only did a reflection based on trying to look at an RSTS/E
node just the other day that did not give me anything.
.ncp tell marduk sho exec
NCP -- Show failed, Listener connect failed, network resources
And I did verify that it's an up and running RSTS/E system. V9.6
according to information I have.
Might also be some other kind of problem somewhere that I haven't
figured out. System also isn't talking CTERM, but did answer when I
tried some RSTS/E specific terminal protocol.
NFT/FAL also failed with network resources error.
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
On Aug 12, 2018, at 9:12 AM, Johnny Billquist
<bqt at softjar.se> wrote:
Hi.
DECnet/E definitely implements NICE, has from the beginning (i.e., from when DECnet/E 2.0
which is the Phase III release was first shipped).
However, it need not be enabled as a known object. And if enabled, it may or may not
accept connections without access control variables (PPN/password). If not, you'll
get a reject indicating either no such object or bad access control. However, if the
connection is accepted you should find a full implementation.
Of course mapping information exists only in routers; if the node you're talking to
is an endnode it will only tell you who the adjacent designated router is (or the adjacent
nodes, on point to point circuits). ...
By exploring adjacent nodes and known circuits, you'd get a more complete picture, as
it will also show you connections which are not the lowest cost paths.
However, as I said, it will only give a partial picture anyway. I also found out the
other day that it don't seem like RSTS/E implements it either, or maybe it depends on
version and maybe it's optional.
10:30 p.m.
On Aug 12, 2018, at 4:22 PM, Johnny Billquist <bqt
at softjar.se> wrote:
On 2018-08-12 21:28, Paul Koning wrote:
In this case not enabled then, I think. Thanks for clarifying that it exists. I only did
a reflection based on trying to look at an RSTS/E node just the other day that did not
give me anything.
.ncp tell marduk sho exec
NCP -- Show failed, Listener connect failed, network resources
If it's not enabled I'd expect an error. Network resources is a bit odd.
Possibly there is a default account defined but that account doesn't exist, or is
configured as "no network connections allowed".
On Aug
12, 2018, at 9:12 AM, Johnny Billquist <bqt at softjar.se> wrote:
Hi.
DECnet/E definitely implements NICE, has from
the beginning (i.e., from when DECnet/E 2.0 which is the Phase III release was first
shipped).
However, it need not be enabled as a known object. And if enabled, it may or may not
accept connections without access control variables (PPN/password). If not, you'll
get a reject indicating either no such object or bad access control. However, if the
connection is accepted you should find a full implementation.
Of course mapping information exists only in routers; if the node you're talking to
is an endnode it will only tell you who the adjacent designated router is (or the adjacent
nodes, on point to point circuits). ...
By exploring adjacent nodes and known circuits, you'd get a more complete picture, as
it will also show you connections which are not the lowest cost paths.
However, as I said, it will only give a partial picture anyway. I also found out the
other day that it don't seem like RSTS/E implements it either, or maybe it depends on
version and maybe it's optional. And I did verify that it's an up and running
RSTS/E system. V9.6 according to information I have.
Might also be some other kind of problem somewhere that I haven't figured out. System
also isn't talking CTERM, but did answer when I tried some RSTS/E specific terminal
protocol.
RSTS/E doesn't support CTERM, only the older OS-specific procotol. That doesn't
involve DECnet credential checking (instead you get a RSTS login prompt).
paul
11:24 p.m.
On 2018-08-12 22:30, Paul Koning wrote:
Agreed that it's a bit surprising error. I have not tried looking deeper
into it. Maybe I should. Do you have any RSTS/E system online I can try
talking to just to make sure it's nothing more general?
I believe
I concluded as much. :-)
However, CTERM will/would only lead you to a login prompt as well.
The RSTS/E specific remote terminal application under RSX have some bug,
though. When it finishes, it crashes the RSX system. Definitely a
problem I need to fix.
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
On Aug 12, 2018, at 4:22 PM, Johnny Billquist
<bqt at softjar.se> wrote:
On 2018-08-12 21:28, Paul Koning wrote:
In this case not enabled then, I think. Thanks for clarifying that it exists. I only did
a reflection based on trying to look at an RSTS/E node just the other day that did not
give me anything.
.ncp tell marduk sho exec
NCP -- Show failed, Listener connect failed, network resources
If it's not enabled I'd expect an error. Network resources is a bit odd.
Possibly there is a default account defined but that account doesn't exist, or is
configured as "no network connections allowed". On Aug
12, 2018, at 9:12 AM, Johnny Billquist <bqt at softjar.se> wrote:
Hi.
> ...
By exploring adjacent nodes and known circuits, you'd get a more complete picture, as
it will also show you connections which are not the lowest cost paths.
However, as I said, it will only give a partial picture anyway. I also found out the
other day that it don't seem like RSTS/E implements it either, or maybe it depends on
version and maybe it's optional.
DECnet/E definitely implements NICE, has from
the beginning (i.e., from when DECnet/E 2.0 which is the Phase III release was first
shipped).
However, it need not be enabled as a known object. And if enabled, it may or may not
accept connections without access control variables (PPN/password). If not, you'll
get a reject indicating either no such object or bad access control. However, if the
connection is accepted you should find a full implementation.
Of course mapping information exists only in routers; if the node you're talking to
is an endnode it will only tell you who the adjacent designated router is (or the adjacent
nodes, on point to point circuits). And I did
verify that it's an up and running RSTS/E system. V9.6 according to information I
have.
Might also be some other kind of problem somewhere that I haven't figured out. System
also isn't talking CTERM, but did answer when I tried some RSTS/E specific terminal
protocol.
RSTS/E doesn't support CTERM, only the older OS-specific procotol. That doesn't
involve DECnet credential checking (instead you get a RSTS login prompt).
11:32 p.m.
When I use set host on vms to login to the little rsts/e box, I have to:
Set host/app=rt
To connect to rterm and not cterm. It works quite well.
On 12 Aug 2018, at 22:24, Johnny Billquist <bqt at
softjar.se> wrote:
On 2018-08-12 22:30, Paul Koning wrote:
Agreed that it's a bit surprising error. I have not tried looking deeper into it.
Maybe I should. Do you have any RSTS/E system online I can try talking to just to make
sure it's nothing more general?
I believe I concluded as much. :-)
However, CTERM will/would only lead you to a login prompt as well.
The RSTS/E specific remote terminal application under RSX have some bug, though. When it
finishes, it crashes the RSX system. Definitely a problem I need to fix.
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
On Aug
12, 2018, at 4:22 PM, Johnny Billquist <bqt at softjar.se> wrote:
On 2018-08-12 21:28, Paul Koning wrote:
If it's not
enabled I'd expect an error. Network resources is a bit odd. Possibly there is a
default account defined but that account doesn't exist, or is configured as "no
network connections allowed". > On Aug 12, 2018, at 9:12 AM, Johnny Billquist
<bqt at softjar.se> wrote:
>
> Hi.
>
>> ...
>
> By exploring adjacent nodes and known circuits, you'd get a more complete
picture, as it will also show you connections which are not the lowest cost paths.
>
> However, as I said, it will only give a partial picture anyway. I also found out the
other day that it don't seem like RSTS/E implements it either, or maybe it depends on
version and maybe it's optional.
DECnet/E definitely implements NICE, has from the beginning (i.e., from when DECnet/E 2.0
which is the Phase III release was first shipped).
However, it need not be enabled as a known object. And if enabled, it may or may not
accept connections without access control variables (PPN/password). If not, you'll
get a reject indicating either no such object or bad access control. However, if the
connection is accepted you should find a full implementation.
Of course mapping information exists only in routers; if the node you're talking to
is an endnode it will only tell you who the adjacent designated router is (or the adjacent
nodes, on point to point circuits).
In this case not enabled then, I think. Thanks for clarifying that it exists. I only did
a reflection based on trying to look at an RSTS/E node just the other day that did not
give me anything.
.ncp tell marduk sho exec
NCP -- Show failed, Listener connect failed, network resources And I did
verify that it's an up and running RSTS/E system. V9.6 according to information I
have.
Might also be some other kind of problem somewhere that I haven't figured out. System
also isn't talking CTERM, but did answer when I tried some RSTS/E specific terminal
protocol.
RSTS/E doesn't support CTERM, only the older OS-specific procotol.
That doesn't involve DECnet credential checking (instead you get a RSTS login prompt).
11:49 p.m.
PLUTO:: is available for testing.
-Steve Davidson
Sent from my iPhone
On Aug 12, 2018, at 17:32, Keith Halewood
<Keith.Halewood at pitbulluk.org> wrote:
When I use set host on vms to login to the little rsts/e box, I have to:
Set host/app=rt
To connect to rterm and not cterm. It works quite well.
> On 12 Aug 2018, at 22:24, Johnny Billquist <bqt at softjar.se> wrote:
>
> On 2018-08-12 22:30, Paul Koning wrote:
>>> On Aug 12, 2018, at 4:22 PM, Johnny Billquist <bqt at softjar.se>
wrote:
>>>
>>> On 2018-08-12 21:28, Paul Koning wrote:
>>>>> On Aug 12, 2018, at 9:12 AM, Johnny Billquist <bqt at
softjar.se> wrote:
>>>>>
>>>>> Hi.
>>>>>
>>>>>> ...
>>>>>
>>>>> By exploring adjacent nodes and known circuits, you'd get a more
complete picture, as it will also show you connections which are not the lowest cost
paths.
>>>>>
>>>>> However, as I said, it will only give a partial picture anyway. I
also found out the other day that it don't seem like RSTS/E implements it either, or
maybe it depends on version and maybe it's optional.
>>>> DECnet/E definitely implements NICE, has from the beginning (i.e., from
when DECnet/E 2.0 which is the Phase III release was first shipped).
>>>> However, it need not be enabled as a known object. And if enabled, it
may or may not accept connections without access control variables (PPN/password). If
not, you'll get a reject indicating either no such object or bad access control.
However, if the connection is accepted you should find a full implementation.
>>>> Of course mapping information exists only in routers; if the node
you're talking to is an endnode it will only tell you who the adjacent designated
router is (or the adjacent nodes, on point to point circuits).
>>>
>>> In this case not enabled then, I think. Thanks for clarifying that it exists.
I only did a reflection based on trying to look at an RSTS/E node just the other day that
did not give me anything.
>>>
>>> .ncp tell marduk sho exec
>>> NCP -- Show failed, Listener connect failed, network resources
>> If it's not enabled I'd expect an error. Network resources is a bit odd.
Possibly there is a default account defined but that account doesn't exist, or is
configured as "no network connections allowed".
>
> Agreed that it's a bit surprising error. I have not tried looking deeper into it.
Maybe I should. Do you have any RSTS/E system online I can try talking to just to make
sure it's nothing more general?
>
>>> And I did verify that it's an up and running RSTS/E system. V9.6
according to information I have.
>>>
>>> Might also be some other kind of problem somewhere that I haven't figured
out. System also isn't talking CTERM, but did answer when I tried some RSTS/E specific
terminal protocol.
>> RSTS/E doesn't support CTERM, only the older OS-specific procotol. That
doesn't involve DECnet credential checking (instead you get a RSTS login prompt).
> I believe I concluded as much. :-)
> However, CTERM will/would only lead you to a login prompt as well.
>
> The RSTS/E specific remote terminal application under RSX have some bug, though. When
it finishes, it crashes the RSX system. Definitely a problem I need to fix.
>
> 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
13 Aug
13 Aug
2:08 a.m.
Cool. Thanks for leading me to it. And that machine I can talk to from
MIM without problems, so it's something specific to that machine it appears.
Johnny
On 2018-08-12 23:49, Steve Davidson wrote:
PLUTO:: is available for testing.
-Steve Davidson
Sent from my iPhone
--
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
On Aug 12, 2018, at 17:32, Keith Halewood
<Keith.Halewood at pitbulluk.org> wrote:
When I use set host on vms to login to the little rsts/e box, I have to:
Set host/app=rt
To connect to rterm and not cterm. It works quite well.
> On 12 Aug 2018, at 22:24, Johnny Billquist <bqt at softjar.se> wrote:
>
> On 2018-08-12 22:30, Paul Koning wrote:
>>> On Aug 12, 2018, at 4:22 PM, Johnny Billquist <bqt at softjar.se>
wrote:
>>>
>>> On 2018-08-12 21:28, Paul Koning wrote:
>>>>> On Aug 12, 2018, at 9:12 AM, Johnny Billquist <bqt at
softjar.se> wrote:
>>>>>
>>>>> Hi.
>>>>>
>>>>>> ...
>>>>>
>>>>> By exploring adjacent nodes and known circuits, you'd get a more
complete picture, as it will also show you connections which are not the lowest cost
paths.
>>>>>
>>>>> However, as I said, it will only give a partial picture anyway. I
also found out the other day that it don't seem like RSTS/E implements it either, or
maybe it depends on version and maybe it's optional.
>>>> DECnet/E definitely implements NICE, has from the beginning (i.e., from
when DECnet/E 2.0 which is the Phase III release was first shipped).
>>>> However, it need not be enabled as a known object. And if enabled, it
may or may not accept connections without access control variables (PPN/password). If
not, you'll get a reject indicating either no such object or bad access control.
However, if the connection is accepted you should find a full implementation.
>>>> Of course mapping information exists only in routers; if the node
you're talking to is an endnode it will only tell you who the adjacent designated
router is (or the adjacent nodes, on point to point circuits).
>>>
>>> In this case not enabled then, I think. Thanks for clarifying that it exists.
I only did a reflection based on trying to look at an RSTS/E node just the other day that
did not give me anything.
>>>
>>> .ncp tell marduk sho exec
>>> NCP -- Show failed, Listener connect failed, network resources
>> If it's not enabled I'd expect an error. Network resources is a bit odd.
Possibly there is a default account defined but that account doesn't exist, or is
configured as "no network connections allowed".
>
> Agreed that it's a bit surprising error. I have not tried looking deeper into it.
Maybe I should. Do you have any RSTS/E system online I can try talking to just to make
sure it's nothing more general?
>
>>> And I did verify that it's an up and running RSTS/E system. V9.6
according to information I have.
>>>
>>> Might also be some other kind of problem somewhere that I haven't figured
out. System also isn't talking CTERM, but did answer when I tried some RSTS/E specific
terminal protocol.
>> RSTS/E doesn't support CTERM, only the older OS-specific procotol. That
doesn't involve DECnet credential checking (instead you get a RSTS login prompt).
> I believe I concluded as much. :-)
> However, CTERM will/would only lead you to a login prompt as well.
>
> The RSTS/E specific remote terminal application under RSX have some bug, though. When
it finishes, it crashes the RSX system. Definitely a problem I need to fix.
>
> 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
2:11 a.m.
By the way, Steve. What version of RSTS/E?
I noticed another "odd" thing here.
.set /host=pluto
NCT -- CTERM is not available on host
NCT -- Using RMT
RMT -- Remote Host incompatibility error
.
Sigh. Seems like I have a few more bugs in RSX I should look at.
Johnny
On 2018-08-13 02:08, Johnny Billquist wrote:
Cool. Thanks for leading me to it. And that machine I
can talk to from
MIM without problems, so it's something specific to that machine it
appears.
? Johnny
On 2018-08-12 23:49, Steve Davidson wrote:
--
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
PLUTO:: is available for testing.
-Steve Davidson
Sent from my iPhone
On Aug 12, 2018, at 17:32, Keith Halewood
<Keith.Halewood at pitbulluk.org> wrote:
When I use set host on vms to login to the little rsts/e box, I have to:
Set host/app=rt
To connect to rterm and not cterm. It works quite well.
> On 12 Aug 2018, at 22:24, Johnny Billquist <bqt at softjar.se> wrote:
>
> On 2018-08-12 22:30, Paul Koning wrote:
>>> On Aug 12, 2018, at 4:22 PM, Johnny Billquist <bqt at softjar.se>
wrote:
>>>
>>> On 2018-08-12 21:28, Paul Koning wrote:
>>>>> On Aug 12, 2018, at 9:12 AM, Johnny Billquist <bqt at
softjar.se>
>>>>> wrote:
>>>>>
>>>>> Hi.
>>>>>
>>>>>> ...
>>>>>
>>>>> By exploring adjacent nodes and known circuits, you'd get a more
>>>>> complete picture, as it will also show you connections which are
>>>>> not the lowest cost paths.
>>>>>
>>>>> However, as I said, it will only give a partial picture anyway.
>>>>> I also found out the other day that it don't seem like RSTS/E
>>>>> implements it either, or maybe it depends on version and maybe
>>>>> it's optional.
>>>> DECnet/E definitely implements NICE, has from the beginning
>>>> (i.e., from when DECnet/E 2.0 which is the Phase III release was
>>>> first shipped).
>>>> However, it need not be enabled as a known object.? And if
>>>> enabled, it may or may not accept connections without access
>>>> control variables (PPN/password).? If not, you'll get a reject
>>>> indicating either no such object or bad access control.? However,
>>>> if the connection is accepted you should find a full implementation.
>>>> Of course mapping information exists only in routers; if the node
>>>> you're talking to is an endnode it will only tell you who the
>>>> adjacent designated router is (or the adjacent nodes, on point to
>>>> point circuits).
>>>
>>> In this case not enabled then, I think. Thanks for clarifying that
>>> it exists. I only did a reflection based on trying to look at an
>>> RSTS/E node just the other day that did not give me anything.
>>>
>>> .ncp tell marduk sho exec
>>> NCP -- Show failed, Listener connect failed, network resources
>> If it's not enabled I'd expect an error.? Network resources is a
>> bit odd.? Possibly there is a default account defined but that
>> account doesn't exist, or is configured as "no network connections
>> allowed".
>
> Agreed that it's a bit surprising error. I have not tried looking
> deeper into it. Maybe I should. Do you have any RSTS/E system online
> I can try talking to just to make sure it's nothing more general?
>
>>> And I did verify that it's an up and running RSTS/E system. V9.6
>>> according to information I have.
>>>
>>> Might also be some other kind of problem somewhere that I haven't
>>> figured out. System also isn't talking CTERM, but did answer when
>>> I tried some RSTS/E specific terminal protocol.
>> RSTS/E doesn't support CTERM, only the older OS-specific procotol.
>> That doesn't involve DECnet credential checking (instead you get a
>> RSTS login prompt).
> I believe I concluded as much. :-)
> However, CTERM will/would only lead you to a login prompt as well.
>
> The RSTS/E specific remote terminal application under RSX have some
> bug, though. When it finishes, it crashes the RSX system. Definitely
> a problem I need to fix.
>
> 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
3:54 a.m.
PLUTO:: is running V10.1L.
I think you have an account. I will verify and get back to you.
-Steve
Sent from my iPhone
On Aug 12, 2018, at 20:11, Johnny Billquist <bqt at
softjar.se> wrote:
By the way, Steve. What version of RSTS/E?
I noticed another "odd" thing here.
.set /host=pluto
NCT -- CTERM is not available on host
NCT -- Using RMT
RMT -- Remote Host incompatibility error
.
Sigh. Seems like I have a few more bugs in RSX I should look at.
Johnny
On 2018-08-13 02:08, Johnny Billquist wrote:
Cool. Thanks for leading me to it. And that machine I can talk to from MIM without
problems, so it's something specific to that machine it appears.
Johnny
> On 2018-08-12 23:49, Steve Davidson wrote:
> PLUTO:: is available for testing.
>
> -Steve Davidson
>
> Sent from my iPhone
>
>> On Aug 12, 2018, at 17:32, Keith Halewood <Keith.Halewood at pitbulluk.org>
wrote:
>>
>> When I use set host on vms to login to the little rsts/e box, I have to:
>>
>> Set host/app=rt
>>
>> To connect to rterm and not cterm. It works quite well.
>>
>>> On 12 Aug 2018, at 22:24, Johnny Billquist <bqt at softjar.se> wrote:
>>>
>>> On 2018-08-12 22:30, Paul Koning wrote:
>>>>> On Aug 12, 2018, at 4:22 PM, Johnny Billquist <bqt at
softjar.se> wrote:
>>>>>
>>>>> On 2018-08-12 21:28, Paul Koning wrote:
>>>>>>> On Aug 12, 2018, at 9:12 AM, Johnny Billquist <bqt at
softjar.se> wrote:
>>>>>>>
>>>>>>> Hi.
>>>>>>>
>>>>>>>> ...
>>>>>>>
>>>>>>> By exploring adjacent nodes and known circuits, you'd get
a more complete picture, as it will also show you connections which are not the lowest
cost paths.
>>>>>>>
>>>>>>> However, as I said, it will only give a partial picture
anyway. I also found out the other day that it don't seem like RSTS/E implements it
either, or maybe it depends on version and maybe it's optional.
>>>>>> DECnet/E definitely implements NICE, has from the beginning
(i.e., from when DECnet/E 2.0 which is the Phase III release was first shipped).
>>>>>> However, it need not be enabled as a known object. And if
enabled, it may or may not accept connections without access control variables
(PPN/password). If not, you'll get a reject indicating either no such object or bad
access control. However, if the connection is accepted you should find a full
implementation.
>>>>>> Of course mapping information exists only in routers; if the node
you're talking to is an endnode it will only tell you who the adjacent designated
router is (or the adjacent nodes, on point to point circuits).
>>>>>
>>>>> In this case not enabled then, I think. Thanks for clarifying that it
exists. I only did a reflection based on trying to look at an RSTS/E node just the other
day that did not give me anything.
>>>>>
>>>>> .ncp tell marduk sho exec
>>>>> NCP -- Show failed, Listener connect failed, network resources
>>>> If it's not enabled I'd expect an error. Network resources is a
bit odd. Possibly there is a default account defined but that account doesn't exist,
or is configured as "no network connections allowed".
>>>
>>> Agreed that it's a bit surprising error. I have not tried looking deeper
into it. Maybe I should. Do you have any RSTS/E system online I can try talking to just to
make sure it's nothing more general?
>>>
>>>>> And I did verify that it's an up and running RSTS/E system. V9.6
according to information I have.
>>>>>
>>>>> Might also be some other kind of problem somewhere that I haven't
figured out. System also isn't talking CTERM, but did answer when I tried some RSTS/E
specific terminal protocol.
>>>> RSTS/E doesn't support CTERM, only the older OS-specific procotol.
That doesn't involve DECnet credential checking (instead you get a RSTS login
prompt).
>>> I believe I concluded as much. :-)
>>> However, CTERM will/would only lead you to a login prompt as well.
>>>
>>> The RSTS/E specific remote terminal application under RSX have some bug,
though. When it finishes, it crashes the RSX system. Definitely a problem I need to fix.
>>>
>>> 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
>
--
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
4:12 p.m.
On Aug 12, 2018, at 8:11 PM, Johnny Billquist <bqt
at softjar.se> wrote:
By the way, Steve. What version of RSTS/E?
I noticed another "odd" thing here.
.set /host=pluto
NCT -- CTERM is not available on host
NCT -- Using RMT
RMT -- Remote Host incompatibility error
The first message from the responding node contains OS and protocol identifiers. The
protocol identifiers, if I read the RSTS client correctly, are RSTS, RSX, VMS, and TOPS-20
protocols respectively (for 1 and up). TOPS-20 is also used by RT-11; I forgot what
Ultrix uses, either RSTS or TOPS-20 protocol I think.
If you run the "official" network terminal client on RSTS, it will give you a
very similar message when connecting to non-RSTS because only the RSTS protocol was
officially supported. But the "netuns" client supports all four. I have a
summary of all four protocols somewhere which I used to extend the DECnet/Linux client; or
you could use that code as a reference implementation if you need one.
paul
14 Aug
14 Aug
10:30 a.m.
On 2018-08-13 16:12, Paul Koning wrote:
Thanks for the clarifications. I have never looked closer at this older
protocol itself. But just like RSTS/E, the RSX DECnet distribution
provides a bunch of unsupported tools. And there too are a programs to
connect to other operating systems. But in RSX, it's a different tool
for each type of OS to connect to.
So you have a program called RRS to connect to RSTS/E systems, and a
program called HOST to connect to TOPS-20.
RVT for connections to VMS.
(And RMT is the program for RSX to RSX communication.)
So I don't really need some reference implementation. The code already
exists, but I suspect it has rotted some over the years, so I need to
fix it.
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
On Aug 12, 2018, at 8:11 PM, Johnny Billquist
<bqt at softjar.se> wrote:
By the way, Steve. What version of RSTS/E?
I noticed another "odd" thing here.
.set /host=pluto
NCT -- CTERM is not available on host
NCT -- Using RMT
RMT -- Remote Host incompatibility error
The first message from the responding node contains OS and protocol identifiers. The
protocol identifiers, if I read the RSTS client correctly, are RSTS, RSX, VMS, and TOPS-20
protocols respectively (for 1 and up). TOPS-20 is also used by RT-11; I forgot what
Ultrix uses, either RSTS or TOPS-20 protocol I think.
If you run the "official" network terminal client on RSTS, it will give you a
very similar message when connecting to non-RSTS because only the RSTS protocol was
officially supported. But the "netuns" client supports all four. I have a
summary of all four protocols somewhere which I used to extend the DECnet/Linux client; or
you could use that code as a reference implementation if you need one.
2 Sep
2 Sep
2:37 p.m.
Hi all. I thought I'd just make a final report on this story.
This turned out to be a combination of two issues.
1) There is a bug in the RSX kernel, which can cause crashed by any
program, if they just do the right (wrong) thing. I've known about this
problem for quite a while, and it has been fixed in my non-released
RSX-11M-PLUS V5.0. So if that ever goes out, this problem is no more.
2) There was a bug in the program to connect to RSTS/E from RSX
explicitly, which triggered the #1 bug. This bug I have now fixed as
well, so the program works fine, even on older versions of RSX. When
that bug was introduced, I have no idea. I would assume that it wasn't
there from the start, or I would have expected that DEC would have noticed.
Anyway, all is good. And if someone wants to, they can fetch the fixed
RRS program from MIM::DU:[5,54]RRS.TSK
Johnny
On 2018-08-14 10:30, Johnny Billquist wrote:
On 2018-08-13 16:12, Paul Koning wrote:
Thanks for the clarifications. I have never looked closer at this older
protocol itself. But just like RSTS/E, the RSX DECnet distribution
provides a bunch of unsupported tools. And there too are a programs to
connect to other operating systems. But in RSX, it's a different tool
for each type of OS to connect to.
So you have a program called RRS to connect to RSTS/E systems, and a
program called HOST to connect to TOPS-20.
RVT for connections to VMS.
(And RMT is the program for RSX to RSX communication.)
So I don't really need some reference implementation. The code already
exists, but I suspect it has rotted some over the years, so I need to
fix it.
? 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
On Aug 12, 2018, at 8:11 PM, Johnny Billquist
<bqt at softjar.se> wrote:
By the way, Steve. What version of RSTS/E?
I noticed another "odd" thing here.
.set /host=pluto
NCT -- CTERM is not available on host
NCT -- Using RMT
RMT -- Remote Host incompatibility error
The first message from the responding node contains OS and protocol
identifiers.? The protocol identifiers, if I read the RSTS client
correctly, are RSTS, RSX, VMS, and TOPS-20 protocols respectively (for
1 and up).? TOPS-20 is also used by RT-11; I forgot what Ultrix uses,
either RSTS or TOPS-20 protocol I think.
If you run the "official" network terminal client on RSTS, it will
give you a very similar message when connecting to non-RSTS because
only the RSTS protocol was officially supported.? But the "netuns"
client supports all four.? I have a summary of all four protocols
somewhere which I used to extend the DECnet/Linux client; or you could
use that code as a reference implementation if you need one.
13 Aug
13 Aug
4:14 p.m.
On Aug 12, 2018, at 8:11 PM, Johnny Billquist <bqt
at softjar.se> wrote:
By the way, Steve. What version of RSTS/E?
I noticed another "odd" thing here.
.set /host=pluto
NCT -- CTERM is not available on host
NCT -- Using RMT
RMT -- Remote Host incompatibility error
FWIW, I don't believe any changes in the RSTS rterm protocol were made in a very long
time, if ever. Certainly I can't imagine that V9.x vs. V10.x would make any
difference.
paul
2:06 a.m.
Um... Yes... And for RSX there is a program called RRS, which is used to
connect to RSTS/E systems. Crashes the RSX system at program exit, like
I said...
Johnny
On 2018-08-12 23:32, Keith Halewood wrote:
When I use set host on vms to login to the little
rsts/e box, I have to:
Set host/app=rt
To connect to rterm and not cterm. It works quite well.
> On 12 Aug 2018, at 22:24, Johnny Billquist <bqt at softjar.se> wrote:
>
> On 2018-08-12 22:30, Paul Koning wrote:
>>> On Aug 12, 2018, at 4:22 PM, Johnny Billquist <bqt at softjar.se>
wrote:
>>>
>>> On 2018-08-12 21:28, Paul Koning wrote:
>>>>> On Aug 12, 2018, at 9:12 AM, Johnny Billquist <bqt at
softjar.se> wrote:
>>>>>
>>>>> Hi.
>>>>>
>>>>>> ...
>>>>>
>>>>> By exploring adjacent nodes and known circuits, you'd get a more
complete picture, as it will also show you connections which are not the lowest cost
paths.
>>>>>
>>>>> However, as I said, it will only give a partial picture anyway. I
also found out the other day that it don't seem like RSTS/E implements it either, or
maybe it depends on version and maybe it's optional.
>>>> DECnet/E definitely implements NICE, has from the beginning (i.e., from
when DECnet/E 2.0 which is the Phase III release was first shipped).
>>>> However, it need not be enabled as a known object. And if enabled, it
may or may not accept connections without access control variables (PPN/password). If
not, you'll get a reject indicating either no such object or bad access control.
However, if the connection is accepted you should find a full implementation.
>>>> Of course mapping information exists only in routers; if the node
you're talking to is an endnode it will only tell you who the adjacent designated
router is (or the adjacent nodes, on point to point circuits).
>>>
>>> In this case not enabled then, I think. Thanks for clarifying that it exists.
I only did a reflection based on trying to look at an RSTS/E node just the other day that
did not give me anything.
>>>
>>> .ncp tell marduk sho exec
>>> NCP -- Show failed, Listener connect failed, network resources
>> If it's not enabled I'd expect an error. Network resources is a bit odd.
Possibly there is a default account defined but that account doesn't exist, or is
configured as "no network connections allowed".
>
> Agreed that it's a bit surprising error. I have not tried looking deeper into it.
Maybe I should. Do you have any RSTS/E system online I can try talking to just to make
sure it's nothing more general?
>
>>> And I did verify that it's an up and running RSTS/E system. V9.6
according to information I have.
>>>
>>> Might also be some other kind of problem somewhere that I haven't figured
out. System also isn't talking CTERM, but did answer when I tried some RSTS/E specific
terminal protocol.
>> RSTS/E doesn't support CTERM, only the older OS-specific procotol. That
doesn't involve DECnet credential checking (instead you get a RSTS login prompt).
> I believe I concluded as much. :-)
> However, CTERM will/would only lead you to a login prompt as well.
>
> The RSTS/E specific remote terminal application under RSX have some bug, though. When
it finishes, it crashes the RSX system. Definitely a problem I need to fix.
>
> 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
--
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
14 Aug
14 Aug
1:40 p.m.
I either use set host/app=rtem or set host/lat to get to PLUTO::.
-Steve
On Aug 12, 2018, at 17:32, Keith Halewood
<Keith.Halewood at pitbulluk.org> wrote:
When I use set host on vms to login to the little rsts/e box, I have to:
Set host/app=rt
To connect to rterm and not cterm. It works quite well.
> On 12 Aug 2018, at 22:24, Johnny Billquist <bqt at softjar.se> wrote:
>
> On 2018-08-12 22:30, Paul Koning wrote:
>>> On Aug 12, 2018, at 4:22 PM, Johnny Billquist <bqt at softjar.se>
wrote:
>>>
>>> On 2018-08-12 21:28, Paul Koning wrote:
>>>>> On Aug 12, 2018, at 9:12 AM, Johnny Billquist <bqt at
softjar.se> wrote:
>>>>>
>>>>> Hi.
>>>>>
>>>>>> ...
>>>>>
>>>>> By exploring adjacent nodes and known circuits, you'd get a more
complete picture, as it will also show you connections which are not the lowest cost
paths.
>>>>>
>>>>> However, as I said, it will only give a partial picture anyway. I
also found out the other day that it don't seem like RSTS/E implements it either, or
maybe it depends on version and maybe it's optional.
>>>> DECnet/E definitely implements NICE, has from the beginning (i.e., from
when DECnet/E 2.0 which is the Phase III release was first shipped).
>>>> However, it need not be enabled as a known object. And if enabled, it
may or may not accept connections without access control variables (PPN/password). If
not, you'll get a reject indicating either no such object or bad access control.
However, if the connection is accepted you should find a full implementation.
>>>> Of course mapping information exists only in routers; if the node
you're talking to is an endnode it will only tell you who the adjacent designated
router is (or the adjacent nodes, on point to point circuits).
>>>
>>> In this case not enabled then, I think. Thanks for clarifying that it exists.
I only did a reflection based on trying to look at an RSTS/E node just the other day that
did not give me anything.
>>>
>>> .ncp tell marduk sho exec
>>> NCP -- Show failed, Listener connect failed, network resources
>> If it's not enabled I'd expect an error. Network resources is a bit odd.
Possibly there is a default account defined but that account doesn't exist, or is
configured as "no network connections allowed".
>
> Agreed that it's a bit surprising error. I have not tried looking deeper into it.
Maybe I should. Do you have any RSTS/E system online I can try talking to just to make
sure it's nothing more general?
>
>>> And I did verify that it's an up and running RSTS/E system. V9.6
according to information I have.
>>>
>>> Might also be some other kind of problem somewhere that I haven't figured
out. System also isn't talking CTERM, but did answer when I tried some RSTS/E specific
terminal protocol.
>> RSTS/E doesn't support CTERM, only the older OS-specific procotol. That
doesn't involve DECnet credential checking (instead you get a RSTS login prompt).
> I believe I concluded as much. :-)
> However, CTERM will/would only lead you to a login prompt as well.
>
> The RSTS/E specific remote terminal application under RSX have some bug, though. When
it finishes, it crashes the RSX system. Definitely a problem I need to fix.
>
> 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
13 Aug
13 Aug
7:45 a.m.
This is what I saw on my end:
Event type 34.0, Object spawned
Occurred 29-Jul-31 13:19:43.4 on node 61.151 (MARDUK)
Source node = 1.13 (MIM)
Source process = 0 0 0 BILLQUIST
Destination process = 19
User = 61,1
Password = ...
Event type 34.0, Object spawned
Occurred 29-Jul-31 13:22:33.4 on node 61.151 (MARDUK)
Source node = 1.13 (MIM)
Source process = 0 0 0 BILLQUIST
Destination process = 17
User = 61,1
Password = ...
Event type 34.1, Object spawn failure
Occurred 29-Jul-31 17:10:42.9 on node 61.151 (MARDUK)
Reason: Unknown Object identification
Source node = 1.13 (MIM)
Source process = 0 NCT
Destination process = 42
Event type 34.0, Object spawned
Occurred 29-Jul-31 17:10:43.8 on node 61.151 (MARDUK)
Source node = 1.13 (MIM)
Source process = 0 0 0 BILLQUIST
Destination process = 23
User = 1,2
Password = ...
Incidentally there is no PPN of 61,1 on my system (RSTS/E V9.6).
-Mark
On Sun, Aug 12, 2018 at 2:24 PM, Johnny Billquist <bqt at softjar.se> wrote:
On 2018-08-12 22:30, Paul Koning wrote:
I believe I concluded as much. :-)
However, CTERM will/would only lead you to a login prompt as well.
The RSTS/E specific remote terminal application under RSX have some bug,
though. When it finishes, it crashes the RSX system. Definitely a problem I
need to fix.
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
On Aug 12, 2018, at 4:22 PM, Johnny Billquist <bqt at softjar.se> wrote:
Agreed that it's a bit surprising error. I have not tried looking deeper
into it. Maybe I should. Do you have any RSTS/E system online I can try
talking to just to make sure it's nothing more general?
And I did verify that it's an up and running RSTS/E system. V9.6 according
On 2018-08-12 21:28, Paul Koning wrote:
If it's not enabled I'd expect an error. Network resources is a bit
odd. Possibly there is a default account defined but that account doesn't
exist, or is configured as "no network connections allowed".
On Aug 12, 2018, at 9:12 AM, Johnny Billquist
<bqt at softjar.se> wrote:
>
> Hi.
>
> ...
>>
>
> By exploring adjacent nodes and known circuits, you'd get a more
> complete picture, as it will also show you connections which are not the
> lowest cost paths.
>
> However, as I said, it will only give a partial picture anyway. I also
> found out the other day that it don't seem like RSTS/E implements it
> either, or maybe it depends on version and maybe it's optional.
>
DECnet/E definitely implements NICE, has from the beginning (i.e., from
when DECnet/E 2.0 which is the Phase III release was first shipped).
However, it need not be enabled as a known object. And if enabled, it
may or may not accept connections without access control variables
(PPN/password). If not, you'll get a reject indicating either no such
object or bad access control. However, if the connection is accepted you
should find a full implementation.
Of course mapping information exists only in routers; if the node
you're talking to is an endnode it will only tell you who the adjacent
designated router is (or the adjacent nodes, on point to point circuits).
In this case not enabled then, I think. Thanks for clarifying that it
exists. I only did a reflection based on trying to look at an RSTS/E node
just the other day that did not give me anything.
.ncp tell marduk sho exec
NCP -- Show failed, Listener connect failed, network resources
to
information I have.
Might also be some other kind of problem somewhere that I haven't
figured out. System also isn't talking CTERM, but did answer when I tried
some RSTS/E specific terminal protocol.
RSTS/E doesn't support CTERM, only the older OS-specific procotol. That
doesn't involve DECnet credential checking (instead you get a RSTS login
prompt).
11:56 a.m.
Interesting stuff actually.
Let me comment each one with what I understand...
On 2018-08-13 07:45, Mark Abene wrote:
This is what I saw on my end:
Event type 34.0, Object spawned
Occurred 29-Jul-31 13:19:43.4 on node 61.151 (MARDUK)
Source node = 1.13 (MIM)
Source process = 0 0 0 BILLQUIST
Destination process = 19
User = 61,1
Password = ...
This would be NICE, which is object 19. I do not get any response when I
try to talk NICE to MARDUK. I'm also not providing any authentication
information, so it would seem 61,1 is the default account, or something,
that DECnet on your machine is using.
I'm kindof wondering why I'm not getting any response to NICE requests.
But, as noted before, I do get an network resources error. If I had an
account, it could be interesting to try authenticating myself and see if
that helped. Especially if 61,1 don't even exist as an account on MARDUK.
Event type 34.0, Object spawned
Occurred 29-Jul-31 13:22:33.4 on node 61.151 (MARDUK)
Source node = 1.13 (MIM)
Source process = 0 0 0 BILLQUIST
Destination process = 17
User = 61,1
Password = ...
And this is FAL. Same kind of error on my side. Same story as well. I do
not provide any user authenitication. So maybe it is a problem because
61,1 don't exist.
Event type 34.1, Object spawn failure
Occurred 29-Jul-31 17:10:42.9 on node 61.151 (MARDUK)
Reason: Unknown Object identification
Source node = 1.13 (MIM)
Source process = 0 NCT
Destination process = 42
Object 42 is CTERM, if I remember and see right. So no surprise that you
see that error then, as Paul pointed out that RSTS/E don't support CTERM.
Event type 34.0, Object spawned
Occurred 29-Jul-31 17:10:43.8 on node 61.151 (MARDUK)
Source node = 1.13 (MIM)
Source process = 0 0 0 BILLQUIST
Destination process = 23
User = 1,2
Password = ...
Object 23 is the predecessor of CTERM. I'm not entirely sure of the name
of that protocol. Anyway, I never logged in. Using the normal RSX
program for connecting gives me a protocol error. Using the RSTS/E
specific program did allow me to connect, but did crash RSX afterwards.
But I never logged in. But I guess the user here is just under which the
server itself would be running, and not anything I provided.
Incidentally there is no PPN of 61,1 on my system
(RSTS/E V9.6).
It would be interesting to find out why it is trying to run all those
services under that PPN then.
Johnny
-Mark
On Sun, Aug 12, 2018 at 2:24 PM, Johnny Billquist <bqt at softjar.se
<mailto:bqt at softjar.se>> wrote:
On 2018-08-12 22:30, Paul Koning wrote:
On Aug 12, 2018, at 4:22 PM, Johnny Billquist
<bqt at softjar.se <mailto:bqt at softjar.se>> wrote:
On 2018-08-12 21:28, Paul Koning wrote:
On Aug 12, 2018, at 9:12 AM, Johnny Billquist
<bqt at softjar.se <mailto:bqt at softjar.se>> wrote:
Hi.
...
By exploring adjacent nodes and known circuits,
you'd get a more complete picture, as it will also
show you connections which are not the lowest cost
paths.
However, as I said, it will only give a partial
picture anyway. I also found out the other day that
it don't seem like RSTS/E implements it either, or
maybe it depends on version and maybe it's optional.
DECnet/E definitely implements NICE, has from the
beginning (i.e., from when DECnet/E 2.0 which is the
Phase III release was first shipped).
However, it need not be enabled as a known object.? And
if enabled, it may or may not accept connections without
access control variables (PPN/password).? If not, you'll
get a reject indicating either no such object or bad
access control.? However, if the connection is accepted
you should find a full implementation.
Of course mapping information exists only in routers; if
the node you're talking to is an endnode it will only
tell you who the adjacent designated router is (or the
adjacent nodes, on point to point circuits).
In this case not enabled then, I think. Thanks for
clarifying that it exists. I only did a reflection based on
trying to look at an RSTS/E node just the other day that did
not give me anything.
.ncp tell marduk sho exec
NCP -- Show failed, Listener connect failed, network resources
If it's not enabled I'd expect an error.? Network resources is a
bit odd.? Possibly there is a default account defined but that
account doesn't exist, or is configured as "no network
connections allowed".
Agreed that it's a bit surprising error. I have not tried looking
deeper into it. Maybe I should. Do you have any RSTS/E system online
I can try talking to just to make sure it's nothing more general?
And I did verify that it's an up and running RSTS/E system.
V9.6 according to information I have.
Might also be some other kind of problem somewhere that I
haven't figured out. System also isn't talking CTERM, but
did answer when I tried some RSTS/E specific terminal protocol.
RSTS/E doesn't support CTERM, only the older OS-specific
procotol.? That doesn't involve DECnet credential checking
(instead you get a RSTS login prompt).
I believe I concluded as much. :-)
However, CTERM will/would only lead you to a login prompt as well.
The RSTS/E specific remote terminal application under RSX have some
bug, though. When it finishes, it crashes the RSX system. Definitely
a problem I need to fix.
? Johnny
--
Johnny Billquist? ? ? ? ? ? ? ? ? || "I'm on a bus
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ||? on a psychedelic trip
email: bqt at softjar.se <mailto:bqt at softjar.se>? ? ? ? ? ? ?||
Reading murder books
pdp is alive!? ? ? ? ? ? ? ? ? ? ?||? tryin' to stay hip" - B. Idol
--
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
4:06 p.m.
On Aug 13, 2018, at 5:56 AM, Johnny Billquist <bqt
at softjar.se> wrote:
Interesting stuff actually.
Let me comment each one with what I understand...
On 2018-08-13 07:45, Mark Abene wrote:
Clearly an attempt to connect using a nonexistent PPN should fail, and I would expect it
to fail prior to spawning the object ("fork" in Unix terminology). However, see
below.
This is what I saw on my end:
Event type 34.0, Object spawned
Occurred 29-Jul-31 13:19:43.4 on node 61.151 (MARDUK)
Source node = 1.13 (MIM)
Source process = 0 0 0 BILLQUIST
Destination process = 19
User = 61,1
Password = ...
This would be NICE, which is object 19. I do not get any response when I try to talk NICE
to MARDUK. I'm also not providing any authentication information, so it would seem
61,1 is the default account, or something, that DECnet on your machine is using.
I'm kindof wondering why I'm not getting any response to NICE requests. But, as
noted before, I do get an network resources error. If I had an account, it could be
interesting to try authenticating myself and see if that helped. Especially if 61,1
don't even exist as an account on MARDUK. ...
Event type 34.0, Object spawned
Occurred 29-Jul-31 17:10:43.8 on node 61.151 (MARDUK)
Source node = 1.13 (MIM)
Source process = 0 0 0 BILLQUIST
Destination process = 23
User = 1,2
Password = ...
Object 23 is the predecessor of CTERM. I'm not entirely sure of the name of that
protocol. Anyway, I never logged in. Using the normal RSX program for connecting gives me
a protocol error. Using the RSTS/E specific program did allow me to connect, but did crash
RSX afterwards. But I never logged in. But I guess the user here is just under which the
server itself would be running, and not anything I provided. 
12 Aug
12 Aug
11:41 p.m.
You may remember my attempts to map the network. I ran into these issues
exactly. It was a fun exercise but ultimately wasn't very realistic.
On Sun, Aug 12, 2018, 05:25 Johnny Billquist <bqt at softjar.se> wrote:
On 2018-08-12 04:55, Mark Abene wrote:
Honestly mapping the whole network seems a little
redundant, since
Johnny already does that and the information is reasonably up to date on
his web site.
Well, that's not really true. I do not map, or try to keep some kind of
map of HECnet. I have my nodename database, which is entirely voluntary
to register nodes in, and I know that not all nodes on HECnet are in there.
In addition, this does not give much clue about how things are
connected, and for some machines, nothing more than the owner, name and
number is registered.
That said, I do not think it is realistic to automatically try to map
out HECnet anyway, so I think that any such attempts should be thought
about a second time, and probably be abandoned.
There are several problems with trying any kind of mapping. The first is
that there are no proper protocol that is suitable. NICE would be the
obvious first choice, but for example Cisco routers do not provide NICE
at all. And so, you can not traverse and follow connections that way.
There are no other way of just exploring what connections exist, so then
we instead have to resort to an exhaustive search of all node numbers,
using all kind of protocols a machine *might* answer to, which will
trigger all kind of logging events and possibly security systems getting
activated, which is not good.
Some kind of voluntary system is the only acceptable option I think. If
people want to, that could be a way. Possibly using FAL to explore and
find other nodes, but it would have to be based on lists of machines to
probe, which would need to be manually kept up to date.
Similar things have been attempted in the past, with mixed to poor
results, I would say.
Johnny
-Mark
On Sat, Aug 11, 2018 at 7:41 AM, Supratim Sanyal <supratim at riseup.net
<mailto:supratim at riseup.net>> wrote:
Hi Mark,
I have DCL script generating this web page once a week - perhaps you
see this pinging your system? Or maybe I was looking for a guest
account many months ago for some reason I can?t remember.
http://sanyalnet-openvms-vax.freeddns.org:82/falserver/hecnet-status.html
<
http://sanyalnet-openvms-vax.freeddns.org:82/falserver/hecnet-status.html&g…
Supratim Sanyal
Germantown, MD
On Aug 11, 2018, at 12:15 AM, Mark Abene <phiber at phiber.com
<mailto:phiber at phiber.com>> wrote:
--
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
OK, so who is "SANYAL" at node
1.550? If you'd like an account on
my RSTS/E system, all you need do is ask. I'm one of those sys
admins who actually reads his event logs. :)
Regards,
Mark
2086
days inactive
2108
days old
28 comments
8 participants
participants (8)
-
bqt＠softjar.se -
john＠forecast.name -
Keith.Halewood＠pitbulluk.org -
paulkoning＠comcast.net -
phiber＠phiber.com -
steve＠davidson.net -
supratim＠riseup.net -
wonko＠4amlunch.net