On Fri, 10 May 2013, Robert Jarratt wrote:
-----Original Message-----
From: Cory Smelosky [mailto:b4 at gewt.net]
Sent: 10 May 2013 07:28
To: Robert Jarratt
Cc: simh; hecnet
Subject: Re: [HECnet] TOPS20 4.1 DECnet Progress
On Wed, 8 May 2013, Robert Jarratt wrote:
Making progress:
$OPR
OPR>ENTER NCP
NCP>SHOW STATUS KNOWN LINES
NCP>
22:25:11 NCP request # 2 [SHOW STATUS KNOWN LINES]
Status as of 8-May-2013 22:25:12
Line ID State Adjacent Node
KDP_0_0 On
KDP_0_1 On
Function completed successfully
NCP>
J
Regards
Rob
I wonder if it would be possible to apply what you've done with TOPS-20 to
TOPS-10.
Once I get it working on TOPS-20 then we can try TOPS-10. My own efforts to
install DECnet on TOPS-10 have not gone well so far though, it fails to link
after MONGEN.
That was the same problem I was having.
Regards
Rob
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
-----Original Message-----
From: Cory Smelosky [mailto:b4 at gewt.net]
Sent: 10 May 2013 07:28
To: Robert Jarratt
Cc: simh; hecnet
Subject: Re: [HECnet] TOPS20 4.1 DECnet Progress
On Wed, 8 May 2013, Robert Jarratt wrote:
Making progress:
$OPR
OPR>ENTER NCP
NCP>SHOW STATUS KNOWN LINES
NCP>
22:25:11 NCP request # 2 [SHOW STATUS KNOWN LINES]
Status as of 8-May-2013 22:25:12
Line ID State Adjacent Node
KDP_0_0 On
KDP_0_1 On
Function completed successfully
NCP>
J
Regards
Rob
I wonder if it would be possible to apply what you've done with TOPS-20 to
TOPS-10.
Once I get it working on TOPS-20 then we can try TOPS-10. My own efforts to
install DECnet on TOPS-10 have not gone well so far though, it fails to link
after MONGEN.
Regards
Rob
On Wed, 8 May 2013, Robert Jarratt wrote:
Making progress:
$OPR
OPR>ENTER NCP
NCP>SHOW STATUS KNOWN LINES
NCP>
22:25:11 NCP request # 2 [SHOW STATUS KNOWN LINES]
Status as of 8-May-2013 22:25:12
Line ID State Adjacent Node
KDP_0_0 On
KDP_0_1 On
Function completed successfully
NCP>
J
Regards
Rob
I wonder if it would be possible to apply what you've done with TOPS-20 to TOPS-10.
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments_______________________________________________
Simh mailing list
Simh at trailing-edge.comhttp://mailman.trailing-edge.com/mailman/listinfo/simh
On 2013-05-09 03:40, Cory Smelosky wrote:
On Wed, 9 May 2013, Steve Davidson wrote:
Area 32 used to be reserved for the "event" area. Those nodes have been
moved to area 13 to pay homage to DECUS. DECUS used area 13 for all
machines. All of the nodes in area 13 are named after colors - just
like it was done at DECUS. Area 13 is no longer reserved for DECservers
- they are now part of each of our individual networks.
Ahhhh. That would explain it.
Well... Area 32 used to be "reserved", yes. I don't remember that I had any nodenames in the database for area 32, but maybe I did. But I can't recall...
As for DECservers, people might have registered their names with me or not. Wouldn't really make much sense to register them (and if you use RSX for example, there is absolutely no point in setting up the DECservers in DECnet at all, just waste node numbers).
Johnny
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Johnny Billquist
Sent: Wednesday, May 08, 2013 6:52 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Area Request
On 2013-05-08 23:55, Cory Smelosky wrote:
On Wed, 8 May 2013, Dennis Boone wrote:
Isn't ROUTING IV level 2 router? EXEC TYPE is defined as that...or
it
should be anyway.
Yeah, Cory wants Area IV.
Okay. I got him connected now.
Excellent.
It seems there are already nodes defined for area 32. Was it
previously
assigned to someone?
Uh? I don't have any nodes in area 32. Where did you get those?
Also, Please set 32.1 to "FDR", Johnny!
Done.
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
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
--
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 May 8, 2013, at 4:43 PM, Bob Armstrong wrote:
I vaguely remember reading that there's simh support for it, but I don't
see it. =20
=20
I don't think there's any specific simh support for a Multinet port, but
you can of course run Multinet "thru" simh (i.e. install Multinet on a si=
mh
VAX/VMS system and tunnel DECnet thru the simh emulated Ethernet
controller). =20
=20
I assume you're asking about a simh invention that talks to a remote
Multinet VAX/VMS system on the simh host side and pretends to be some oth=
er
device (like a DMR/DUP/DMV/whatever) on the simulated side - I've never s=
een
anything like that.
=20
DECnet/Linux can supposedly emulate a Multinet tunnel. Is that what
you're thinking of? But in that case you're running DECnet on the Linux
host and simh has nothing to do with it.
I want to learn how to make my DECnet speak Multinet. Rob mentioned wantin=
g to do the same for his "user mode router". So it would be another DECnet=
datalink. Point to point or Ethernet-like?
Yes, I saw the DECnet/Linux code. It's rather puzzling because it seems to=
tie into a tun/tap device -- so it expects Ethernet behavior. But then it=
converts to short headers, which suggests point to point behavior. Which =
is it? The data headers are only a tiny part of the difference between the=
two datalink flavors...
paul
Multinet is a PTP driver, it can speak UDP or TCP and there was a message
a year sgo or so here on th meailinglist from the people at TGV that did it
explaining the details.
-P
On Wed, 9 May 2013, Brian Hechinger wrote:
That brings back some memories (the color thing).
When I was at PSU many moons ago one of the places I worked was the
"Crayola Lab" which was a lab full of DECstations running Ultrix.
Each machine was named after a color (crayon) and the xdm login screen
background was set to that color.
It was a neat room when no one was there and all the systems were at
their login screens.
That would've DEFINITELY been neat.
I wish I still had a picture of that.
I wish you did too!
-brian
On 5/8/2013 9:37 PM, Steve Davidson wrote:
Area 32 used to be reserved for the "event" area. Those nodes have been
moved to area 13 to pay homage to DECUS. DECUS used area 13 for all
machines. All of the nodes in area 13 are named after colors - just
like it was done at DECUS. Area 13 is no longer reserved for DECservers
- they are now part of each of our individual networks.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Johnny Billquist
Sent: Wednesday, May 08, 2013 6:52 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Area Request
On 2013-05-08 23:55, Cory Smelosky wrote:
On Wed, 8 May 2013, Dennis Boone wrote:
Isn't ROUTING IV level 2 router? EXEC TYPE is defined as that...or
it
should be anyway.
Yeah, Cory wants Area IV.
Okay. I got him connected now.
Excellent.
It seems there are already nodes defined for area 32. Was it
previously
assigned to someone?
Uh? I don't have any nodes in area 32. Where did you get those?
Also, Please set 32.1 to "FDR", Johnny!
Done.
Johnny
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
That brings back some memories (the color thing).
When I was at PSU many moons ago one of the places I worked was the "Crayola Lab" which was a lab full of DECstations running Ultrix.
Each machine was named after a color (crayon) and the xdm login screen background was set to that color.
It was a neat room when no one was there and all the systems were at their login screens.
I wish I still had a picture of that.
-brian
On 5/8/2013 9:37 PM, Steve Davidson wrote:
Area 32 used to be reserved for the "event" area. Those nodes have been
moved to area 13 to pay homage to DECUS. DECUS used area 13 for all
machines. All of the nodes in area 13 are named after colors - just
like it was done at DECUS. Area 13 is no longer reserved for DECservers
- they are now part of each of our individual networks.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Johnny Billquist
Sent: Wednesday, May 08, 2013 6:52 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Area Request
On 2013-05-08 23:55, Cory Smelosky wrote:
On Wed, 8 May 2013, Dennis Boone wrote:
Isn't ROUTING IV level 2 router? EXEC TYPE is defined as that...or
it
should be anyway.
Yeah, Cory wants Area IV.
Okay. I got him connected now.
Excellent.
It seems there are already nodes defined for area 32. Was it
previously
assigned to someone?
Uh? I don't have any nodes in area 32. Where did you get those?
Also, Please set 32.1 to "FDR", Johnny!
Done.
Johnny
On Wed, 9 May 2013, Steve Davidson wrote:
Area 32 used to be reserved for the "event" area. Those nodes have been
moved to area 13 to pay homage to DECUS. DECUS used area 13 for all
machines. All of the nodes in area 13 are named after colors - just
like it was done at DECUS. Area 13 is no longer reserved for DECservers
- they are now part of each of our individual networks.
Ahhhh. That would explain it.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Johnny Billquist
Sent: Wednesday, May 08, 2013 6:52 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Area Request
On 2013-05-08 23:55, Cory Smelosky wrote:
On Wed, 8 May 2013, Dennis Boone wrote:
Isn't ROUTING IV level 2 router? EXEC TYPE is defined as that...or
it
should be anyway.
Yeah, Cory wants Area IV.
Okay. I got him connected now.
Excellent.
It seems there are already nodes defined for area 32. Was it
previously
assigned to someone?
Uh? I don't have any nodes in area 32. Where did you get those?
Also, Please set 32.1 to "FDR", Johnny!
Done.
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
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
Area 32 used to be reserved for the "event" area. Those nodes have been
moved to area 13 to pay homage to DECUS. DECUS used area 13 for all
machines. All of the nodes in area 13 are named after colors - just
like it was done at DECUS. Area 13 is no longer reserved for DECservers
- they are now part of each of our individual networks.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Johnny Billquist
Sent: Wednesday, May 08, 2013 6:52 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Area Request
On 2013-05-08 23:55, Cory Smelosky wrote:
On Wed, 8 May 2013, Dennis Boone wrote:
Isn't ROUTING IV level 2 router? EXEC TYPE is defined as that...or
it
should be anyway.
Yeah, Cory wants Area IV.
Okay. I got him connected now.
Excellent.
It seems there are already nodes defined for area 32. Was it
previously
assigned to someone?
Uh? I don't have any nodes in area 32. Where did you get those?
Also, Please set 32.1 to "FDR", Johnny!
Done.
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 May 8, 2013, at 6:15 PM, Bob Armstrong wrote:
I think I figured it out. The DECnet/Linux code is in dnprogs, file
multinet.c
... the multinet stuff hooks into the Ethernet machinery (via a tun/tap
port).
This just begs the question - can I run multinet.c as a stand alone
program? Suppose I had a Linux machine, ran simh, connected the virtual
QNA/UNA to a tun/tap device, connected multinet.c to the same device, could
I then talk to a remote VMS node?
Quite a hack, but it might be useful ...
Bob
It looks that way. Check out the code, it's part of the dnprogs package. Just one file.
paul
