Tim,
I need to check tomorrow. The IP you have for me is correct.
I have recently rebuilt my router config so there is no firewall, there are some primitive access lists and these may be hampering things.
Mark
On 25 May 2014, at 17:26, Tim Sneddon <tim at sneddon.id.au> wrote:
On Mon, May 26, 2014 at 12:00 AM, Mark Darvill <mark.darvill at mac.com> wrote:
Brian,
Have seen the latest configs have been pushed through.
My router seems to be up
cmrtr01#show decnet neigh
Net Node Interface MAC address Flags
0 9.1023 Tunnel52 0000.0000.0000 A
Hi Mark,
I can't see your network on my router:
a12rtr#show decnet neigh
Net Node Interface MAC address Flags
0 9.1023 Tunnel52 0000.0000.0000 A
0 23.1023 Tunnel59 0000.0000.0000 A
0 42.1022 Tunnel51 0000.0000.0000 A
0 52.1023 Tunnel50 0000.0000.0000 A
0 61.1023 Tunnel53 0000.0000.0000 A
0 12.2 FastEthernet0/0 aa00.0400.0230
Are you running a firewall or access lists on incoming connections? The destination IP on my tunnel to you is 81.142.27.37. Is that correct?
Regards, Tim.
My apologies, it's been too long to remember rsx. A netgen is too much work for an experiment.
Background for the request: I had problems running two area routers on the same lan, though just one was simh based. Both were VMS though.
Verzonden vanaf mijn BlackBerry 10-smartphone.
Origineel bericht
Van: Jean-Yves Bernier
Verzonden: zondag 25 mei 2014 18:14
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Same MAC address on different nodes
At 5:52 PM +0200 25/5/14, Hans Vlems wrote:
Mc ncp Def exec type endnode
NCP>SET EXEC TYPE ENDNODE
SET EXEC TYPE ENDNODE>>
NCP -- Set not accepted, invalid parameter value, Type
NCP>HELP SET EXEC
Use the SET EXECUTOR command to create or modify executor node parameters.
The format is:
SET EXECUTOR parameters
Parameter types are ALL or one or more of:
DTE HOST STATE
NODE INCOMING TIMER OUTGOING TIMER
INACTIVITY TIMER RETRANSMIT FACTOR ROUTING TIMER
SEGMENT BUFFER SIZE RECEIVE PASSWORD TRANSMIT PASSWORD
VERIFICATION [STATE] CONFIDENCE TIMER MAXIMUM PATH SPLITS
INCOMING PROXY OUTGOING PROXY
Trying CFE.
CFE
Enter filename: LB:[5,54]CETAB.MAC
CFE>HELP DEF EXEC
Use the DEFINE EXECUTOR command to establish executor node parameters.
The format is:
DEFINE EXECUTOR parameters
Parameter types are:
ADDRESS BROADCAST ROUTING TIMER HOST
IDENTIFICATION MAXIMUM ADDRESS MAXIMUM BROADCAST ENDNODES
MAXIMUM COST MAXIMUM HOPS MAXIMUM LINKS
MAXIMUM NODE COUNTERS NAME ROUTING TIMER
SEGMENT BUFFER SIZE VERIFICATION STATE CONFIDENCE TIMER
INCOMING PROXY OUTGOING PROXY MAXIMUM PATH SPLITS
No way to SET/DEF EXEC ENDNODE.
Both nodes have licenses for DECnet installed?
Did not know DECnet used DRM.
--
Jean-Yves Bernier
On Mon, May 26, 2014 at 12:00 AM, Mark Darvill <mark.darvill at mac.com> wrote:
Brian,
Have seen the latest configs have been pushed through.
My router seems to be up
cmrtr01#show decnet neigh
Net Node Interface MAC address Flags
0 9.1023 Tunnel52 0000.0000.0000 A
Hi Mark,
I can't see your network on my router:
a12rtr#show decnet neigh
Net Node Interface MAC address Flags
0 9.1023 Tunnel52 0000.0000.0000 A
0 23.1023 Tunnel59 0000.0000.0000 A
0 42.1022 Tunnel51 0000.0000.0000 A
0 52.1023 Tunnel50 0000.0000.0000 A
0 61.1023 Tunnel53 0000.0000.0000 A
0 12.2 FastEthernet0/0 aa00.0400.0230
Are you running a firewall or access lists on incoming connections? The destination IP on my tunnel to you is 81.142.27.37. Is that correct?
Regards, Tim.
At 5:52 PM +0200 25/5/14, Hans Vlems wrote:
Mc ncp Def exec type endnode
NCP>SET EXEC TYPE ENDNODE
SET EXEC TYPE ENDNODE>>
NCP -- Set not accepted, invalid parameter value, Type
NCP>HELP SET EXEC
Use the SET EXECUTOR command to create or modify executor node parameters.
The format is:
SET EXECUTOR parameters
Parameter types are ALL or one or more of:
DTE HOST STATE
NODE INCOMING TIMER OUTGOING TIMER
INACTIVITY TIMER RETRANSMIT FACTOR ROUTING TIMER
SEGMENT BUFFER SIZE RECEIVE PASSWORD TRANSMIT PASSWORD
VERIFICATION [STATE] CONFIDENCE TIMER MAXIMUM PATH SPLITS
INCOMING PROXY OUTGOING PROXY
Trying CFE.
CFE
Enter filename: LB:[5,54]CETAB.MAC
CFE>HELP DEF EXEC
Use the DEFINE EXECUTOR command to establish executor node parameters.
The format is:
DEFINE EXECUTOR parameters
Parameter types are:
ADDRESS BROADCAST ROUTING TIMER HOST
IDENTIFICATION MAXIMUM ADDRESS MAXIMUM BROADCAST ENDNODES
MAXIMUM COST MAXIMUM HOPS MAXIMUM LINKS
MAXIMUM NODE COUNTERS NAME ROUTING TIMER
SEGMENT BUFFER SIZE VERIFICATION STATE CONFIDENCE TIMER
INCOMING PROXY OUTGOING PROXY MAXIMUM PATH SPLITS
No way to SET/DEF EXEC ENDNODE.
Both nodes have licenses for DECnet installed?
Did not know DECnet used DRM.
--
Jean-Yves Bernier
Area 44 is missing, my simh node is up.
Verzonden vanaf mijn BlackBerry 10-smartphone.
Van: Mark Darvill
Verzonden: zondag 25 mei 2014 18:00
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Cisco Tunnel Update
Brian,
Have seen the latest configs have been pushed through.
My router seems to be up
cmrtr01#show decnet neigh
Net Node Interface MAC address Flags
0 9.1023 Tunnel52 0000.0000.0000 A
cmrtr01#show decnet route
Area Cost Hops Next Hop to Node Expires Prio
*1 70 3 Tunnel52 -> 9.1023
*3 71 4 Tunnel52 -> 9.1023
*4 70 3 Tunnel52 -> 9.1023
*5 70 3 Tunnel52 -> 9.1023
*7 72 4 Tunnel52 -> 9.1023
*8 70 3 Tunnel52 -> 9.1023
*9 20 1 Tunnel52 -> 9.1023 36 64 A+
*11 70 3 Tunnel52 -> 9.1023
*12 40 2 Tunnel52 -> 9.1023
*18 71 4 Tunnel52 -> 9.1023
*19 70 3 Tunnel52 -> 9.1023
*20 71 4 Tunnel52 -> 9.1023
*22 0 0 (Local) -> 22.100
*23 50 3 Tunnel52 -> 9.1023
*28 70 3 Tunnel52 -> 9.1023
*33 71 4 Tunnel52 -> 9.1023
*42 40 2 Tunnel52 -> 9.1023
*47 70 3 Tunnel52 -> 9.1023
*52 50 3 Tunnel52 -> 9.1023
*59 70 3 Tunnel52 -> 9.1023
*61 30 2 Tunnel52 -> 9.1023
*62 70 3 Tunnel52 -> 9.1023
Node Cost Hops Next Hop to Node Expires Prio
*(Area) 0 0 (Local) -> 22.100
*22.100 0 0 (Local) -> 22.100
Let me know if this doesn t look right or that you can t see me.
Mark
On 24 May 2014, at 14:03, Brian Hechinger <wonko at 4amlunch.net> wrote:
Mark Thomas has joined us in the Cisco tunnel system!
Now I just need to hunt down Mark Darvill and see why his tunnel isn't
working.
Oh, and that Cory guy. His tunnel is still broken. *shakes fist at Cory*
:)
At this point in time we have 7 tunnel members. Yay!
-brian
Brian,
Have seen the latest configs have been pushed through.
My router seems to be up
cmrtr01#show decnet neigh
Net Node Interface MAC address Flags
0 9.1023 Tunnel52 0000.0000.0000 A
cmrtr01#show decnet route
Area Cost Hops Next Hop to Node Expires Prio
*1 70 3 Tunnel52 -> 9.1023
*3 71 4 Tunnel52 -> 9.1023
*4 70 3 Tunnel52 -> 9.1023
*5 70 3 Tunnel52 -> 9.1023
*7 72 4 Tunnel52 -> 9.1023
*8 70 3 Tunnel52 -> 9.1023
*9 20 1 Tunnel52 -> 9.1023 36 64 A+
*11 70 3 Tunnel52 -> 9.1023
*12 40 2 Tunnel52 -> 9.1023
*18 71 4 Tunnel52 -> 9.1023
*19 70 3 Tunnel52 -> 9.1023
*20 71 4 Tunnel52 -> 9.1023
*22 0 0 (Local) -> 22.100
*23 50 3 Tunnel52 -> 9.1023
*28 70 3 Tunnel52 -> 9.1023
*33 71 4 Tunnel52 -> 9.1023
*42 40 2 Tunnel52 -> 9.1023
*47 70 3 Tunnel52 -> 9.1023
*52 50 3 Tunnel52 -> 9.1023
*59 70 3 Tunnel52 -> 9.1023
*61 30 2 Tunnel52 -> 9.1023
*62 70 3 Tunnel52 -> 9.1023
Node Cost Hops Next Hop to Node Expires Prio
*(Area) 0 0 (Local) -> 22.100
*22.100 0 0 (Local) -> 22.100
Let me know if this doesn t look right or that you can t see me.
Mark
On 24 May 2014, at 14:03, Brian Hechinger <wonko at 4amlunch.net> wrote:
Mark Thomas has joined us in the Cisco tunnel system!
Now I just need to hunt down Mark Darvill and see why his tunnel isn't
working.
Oh, and that Cory guy. His tunnel is still broken. *shakes fist at Cory*
:)
At this point in time we have 7 tunnel members. Yay!
-brian
On Sun, May 25, 2014 at 3:06 AM, Brian Hechinger <wonko at 4amlunch.net> wrote:
> On May 24, 2014, at 12:28, Cory Smelosky <b4 at gewt.net> wrote:
>
>>
>> Now I just need to hunt down Mark Darvill and see why his tunnel isn't
>> working.
>>
>> Oh, and that Cory guy. His tunnel is still broken. *shakes fist at Cory*
>
> Hey! I've been busy! And quite frankly I have no idea what the hell is wrong.
I'm super busy with moving to a new house, tidying things up at current job preparing to leave and then starting a new job on the 3rd.
After that I'll have some time and we can mess with it.
In the meantime bug Tim as he's proven to be very knowledgable about such things. :)
Thanks for the mention Brian. Yes, I am happy to help out. I'm not sure what is going on with Cory's tunnel to you, but I certainly have mine working:
a12rtr#show decnet neigh
Net Node Interface MAC address Flags
0 9.1023 Tunnel52 0000.0000.0000 A
I have compared our tunnel configs and they are both the same, so I'm guessing it is a Cory's end.
Cory, let me know if you want some help fixing this, although it seems your up to your eyeballs in it with your 11/23+.
Regards, Tim.
Yes, just try it on one node, the one that is not responding:
Mc ncp Def exec type endnode
Mc ncp set exec state shut
@sys$manager:startnet
Ps 1
You can return to an area router by replacing step 1 with:
Mc ncp Def exec type area
And proceed with steps 2 and 3
Ps2
Both nodes have licenses for DECnet installed?
Verzonden vanaf mijn BlackBerry 10-smartphone.
Origineel bericht
Van: Jean-Yves Bernier
Verzonden: zondag 25 mei 2014 17:45
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Same MAC address on different nodes
At 5:41 PM +0200 25/5/14, Hans Vlems wrote:
What happens if you turn them both into endnotes, or both level 1 routers?
Can I do that without NETGEN?
What version of winpcap do you run?
Linux, yum install libpcap libpcap-devel
--
Jean-Yves Bernier
On Sun, May 25, 2014 at 7:30 AM, Mark G Thomas <Mark at misty.com> wrote:
Hi,
So now I'm connected via GRE tunnels, and assigned a decnet cost
to the local ethernet interface on my router, but I'm not quite
working yet.
1) I ran SYS$MANAGER:NET$CONFIGURE.COM, but something isn't quite right.
This is for DECnet Phase V, you can run Phase V on HECnet (I do), although most people will tell you to use Phase IV. Personally I don't think it makes a huge difference. In the configuration it pays to used the advanced config, like so:
@sys$manager:net$configure advanced
You can accept most of the defaults, but there are a bunch of questions about Phase IV support and DECnet over TCP/IP that do not appear in the basic configuration. If you need any help I'm happy to help out.
2) Once I get DECnet configured and working, what can I connect to?
I know this is real beginner stuff, but in spite of tons of
documentation about OpenVMS and DECnet, I'm not sure where to
go with this.
%%%%%%%%%%% OPCOM 24-MAY-2014 19:18:04.52 %%%%%%%%%%%
Message from user SYSTEM on OWL
Event: Too Few Servers Detected from: Node LOCAL:.OWL DTSS,
at: 2014-05-24-19:18:04.500-04:00Iinf
Number Detected=0,
Number Required=1
eventUid 21450940-E378-11E3-8006-AA000400035C
entityUid 94C48500-E376-11E3-8005-AA000400035C
streamUid 90585140-E376-11E3-8004-AA000400035C
This message is about DEC DTSS, the DECnet Phase V equivalent of NTP. I usually switch it off as it is largely useless. Add the following to SYS$MANAGER:SYLOGICALS.COM:
$ define/system/executive net$disable_dtss true
This will switch it off at system start up.
$ show network
Product: DECNET Node: OWL Address(es): 23.3
Product: TCP/IP Node: owl.ashdown.misty.com Address(es): 10.5.27.13
r2.home>ping owl
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.5.27.13, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
r2.home>ping decnet owl
Type escape sequence to abort.
Sending 5, 100-byte DECnet echos to atg 0 area.node 23.3, timeout is 5 seconds:
Host unreachable+
Host unreachable+
Host unreachable+
Host unreachable+
Host unreachable+
Success rate is 0 percent (0/5)
r2.home>
If Phase IV compatibility has not been enabled then you likely won't be able to ping from the DECnet router. Feel free to contact me if you need any help.
Regards, Tim.
At 5:41 PM +0200 25/5/14, Hans Vlems wrote:
What happens if you turn them both into endnotes, or both level 1 routers?
Can I do that without NETGEN?
What version of winpcap do you run?
Linux, yum install libpcap libpcap-devel
--
Jean-Yves Bernier
What happens if you turn them both into endnotes, or both level 1 routers?
What version of winpcap do you run?
Verzonden vanaf mijn BlackBerry 10-smartphone.
Origineel bericht
Van: Jean-Yves Bernier
Verzonden: zondag 25 mei 2014 17:13
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Same MAC address on different nodes
At 4:39 PM +0200 25/5/14, Hans Vlems wrote:
Would you post the output of :
Of course.
---
Node characteristics as of 30-MAR-82 00:23:45
Executor node = 10.1 (SHARK)
Identification = DECNET AT PESCADOO, Management version = 4.2.0
Host = 10.1 (SHARK), Loop count = 1
Loop length = 40, Loop with = Mixed
Incoming timer = 15, Outgoing timer = 30
NSP version = 4.0.0
Maximum links = 10, Delay factor = 32
Delay weight = 2
Inactivity timer = 30, Retransmit factor = 5
Routing version = 2.0.0, Type = Area
Routing timer = 300
Broadcast routing timer = 40, Maximum address = 1023
Maximum circuits = 1
Maximum cost = 1022
Maximum hops = 10, Maximum visits = 20
Maximum area = 63, Maximum broadcast endnodes = 32
Maximum broadcast routers = 20
Area maximum cost = 1022, Area maximum hops = 10
Incoming proxy = Disabled
Outgoing proxy = Disabled
Segment buffer size = 576
---
Node characteristics as of 30-MAR-82 00:23:31
Executor node = 10.2 (SNAKE)
Identification = DECNET AT PESCADOO, Management version = 4.2.0
Host = 10.2 (SNAKE), Loop count = 1
Loop length = 40, Loop with = Mixed
Incoming timer = 15, Outgoing timer = 30
NSP version = 4.0.0
Maximum links = 10, Delay factor = 32
Delay weight = 2
Inactivity timer = 30, Retransmit factor = 5
Routing version = 2.0.0, Type = Area
Routing timer = 300
Broadcast routing timer = 40, Maximum address = 1023
Maximum circuits = 1
Maximum cost = 1022
Maximum hops = 10, Maximum visits = 20
Maximum area = 63, Maximum broadcast endnodes = 32
Maximum broadcast routers = 20
Area maximum cost = 1022, Area maximum hops = 10
Incoming proxy = Disabled
Outgoing proxy = Disabled
Segment buffer size = 576
--
Jean-Yves Bernier
At 4:59 PM +0200 25/5/14, Johnny Billquist wrote:
I assume they all "work".
However, the speed to complete the commands might differ a lot.
You are right. They all work "past a certain time".
--
Jean-Yves Bernier
On 2014-05-25 16:41, Jean-Yves Bernier wrote:
At 4:05 PM +0200 25/5/14, Johnny Billquist wrote:
Besides playing around, which I admin is awfully fun, the reason for
using DECnet was to transfer big files (tens of megabytes). So I am out
of luck for now, but I haven't said my last word.
Like I said before. I would start by examining various counters on the
machines to get more understanding of what the problem is, and then
try to solve it from there.
I know that different network interface speeds mess things up, for
example, and I have code in my bridge to help get around the problem
if the bridge is sitting between the systems.
I suspect a timing problem.
Yes. Me too. That is why I would check various counters, to identify in more detail where the timing issues are.
How do you explain that:
NFT TI:=REMOTE::FILE
works 9 times over 10, but
NFT FOO=REMOTE::FILE
hangs every time?
The later is faster.
I do not exclude a vector mis-configuration, although the system should
be unusable.
I assume they all "work". However, the speed to complete the commands might differ a lot.
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 Sun, 25 May 2014, Johnny Billquist wrote:
Oh. That is *old*. No surprise if you got some version mismatch error then.
That's what I figured.
I've already used BRU to copy the baseline with a newer DECnet kit on it over to my ra81 image (with proper MAX and HEADERS set!) and I'm nearing completion of the SYSGEN.
Nope. Used a DECserver 200/MC with a 320 hanging off it. Logged in
fine, got directory listing, created a file, logged out...then it crashed.
Probably version related as well.
Yeah.
Oh well. I thought there was some newer DECnet version available on bitsavers. Maybe not, then...
Possible, No idea. If not...it's no big deal. See above.
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On 2014-05-25 16:35, Cory Smelosky wrote:
On Sun, 25 May 2014, Johnny Billquist wrote:
Could be...
Did you do a netgen after building RSX?
Yes.
I used the NETKIT/DECKIT version 3
(http://bitsavers.trailing-edge.com/bits/DEC/pdp11/magtapes/rsx11mplus/BB-M4…
and
http://bitsavers.trailing-edge.com/bits/DEC/pdp11/magtapes/rsx11mplus/BB-AS…
on 4.6)
Oh. That is *old*. No surprise if you got some version mismatch error then.
Also, I hope you are not using the lat programs that someone wrote
under Unix, since they are breaking the protocols in some way. I have
never bothered to find out exactly how, but they do not play nicely
with RSX. A real DECserver works fine, though.
Nope. Used a DECserver 200/MC with a 320 hanging off it. Logged in
fine, got directory listing, created a file, logged out...then it crashed.
Probably version related as well.
Oh well. I thought there was some newer DECnet version available on bitsavers. Maybe not, then...
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
At 4:05 PM +0200 25/5/14, Johnny Billquist wrote:
Besides playing around, which I admin is awfully fun, the reason for
using DECnet was to transfer big files (tens of megabytes). So I am out
of luck for now, but I haven't said my last word.
Like I said before. I would start by examining various counters on the machines to get more understanding of what the problem is, and then try to solve it from there.
I know that different network interface speeds mess things up, for example, and I have code in my bridge to help get around the problem if the bridge is sitting between the systems.
I suspect a timing problem.
How do you explain that:
NFT TI:=REMOTE::FILE
works 9 times over 10, but
NFT FOO=REMOTE::FILE
hangs every time?
The later is faster.
I do not exclude a vector mis-configuration, although the system should be unusable.
--
Jean-Yves Bernier
Would you post the output of :
Mc ncp sho exec char
On both nodes?
( or did I miss that post)
Verzonden vanaf mijn BlackBerry 10-smartphone.
Origineel bericht
Van: Jean-Yves Bernier
Verzonden: zondag 25 mei 2014 15:54
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Same MAC address on different nodes
At 9:26 AM +0200 25/5/14, Johnny Billquist wrote:
You mean "the Hardware address is whatever you set in simh before
starting". CEX will set it to "Physical address" (in DECNET parlance)
which is AA-00-04-00-(1024 x area + node).
Uh... Not really. simh do not actually change the MAC address of the
physical interface.
Of course, simh don't do DECnet. Communication EXecutive does.
The simh interface starts out with 08-00-2B-AA-BB-CC, but that is
changed to AA-00-04-00-01-28 by DECnet when it starts up, at which
point it no longer listens to 08-00-2B-AA-BB-CC. That address is
just kept around as the original hardware address of the simulated
network interface inside simh.
So we have:
Executor node = 10.1 (SHARK)
Physical address = AA-00-04-00-01-28
Line = QNA-0
Hardware address = 08-00-2B-AA-BB-CC
Executor node = 10.2 (SNAKE)
Physical address = AA-00-04-00-02-28
Line = QNA-0
Hardware address = 08-00-2B-AA-BB-CC
We still have the question "when two nodes runs on the same host, is
SET XQ MAC" necessary? In other words, does the "Hardware address"
play any role in DECnet, besides just being kept around?
Since it would be pointless to put the same address, i tried
SET XQ MAC==00:00:01:00:00:01/02, then
Executor node = 10.1 (SHARK)
Physical address = AA-00-04-00-01-28
Line = QNA-0
Hardware address = 00-00-01-00-00-01
Executor node = 10.2 (SNAKE)
Physical address = AA-00-04-00-02-28
Line = QNA-0
Hardware address = 00-00-01-00-00-02
And I see no difference.
So, a NIC may have different MAC addresses depending of the network
stack running. Am I right here?
Sortof. Your machine normally do only have one MAC address, but if
you have DECnet running, it will need to change your MAC address.
All other network protocols on your machine will then also use this
"new" MAC address.
If we would run on bare metal. They don't because simh shields it.
Maybe the "Physical address" is kept just for restoring it at
shutdown?
Well, my system is working 99%, that's not so bad :)
It is working 100%, you just have performance issues...
Besides playing around, which I admin is awfully fun, the reason for
using DECnet was to transfer big files (tens of megabytes). So I am
out of luck for now, but I haven't said my last word.
--
Jean-Yves Bernier
On Sun, 25 May 2014, Johnny Billquist wrote:
As soon as I have a little time, I'll put them all up on MIM::, along with other useful RSX stuff.
Okay!
MOIRA::CSMELOSKY$ set host mandy
%SYSTEM-F-PROTOCOL, network protocol error
MANDY:: being the PDP-11? What is MOIRA::?
Yeah. MOIRA:: is my VAXstation 4000/60.
Hmm. What version of RSX and DECnet did you install?
See other email.
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On Sun, 25 May 2014, Johnny Billquist wrote:
Could be...
Did you do a netgen after building RSX?
Yes.
I used the NETKIT/DECKIT version 3 (http://bitsavers.trailing-edge.com/bits/DEC/pdp11/magtapes/rsx11mplus/BB-M4… and http://bitsavers.trailing-edge.com/bits/DEC/pdp11/magtapes/rsx11mplus/BB-AS… on 4.6)
Also, I hope you are not using the lat programs that someone wrote under Unix, since they are breaking the protocols in some way. I have never bothered to find out exactly how, but they do not play nicely with RSX. A real DECserver works fine, though.
Nope. Used a DECserver 200/MC with a 320 hanging off it. Logged in fine, got directory listing, created a file, logged out...then it crashed.
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On 2014-05-25 16:34, Cory Smelosky wrote:
On Sun, 25 May 2014, Johnny Billquist wrote:
Glad good scans exist! ;)
It used to be that Stromasys had them available, but right now I can't
seem to find the page I used to look at...
I'm sure they're around somewhere.
As soon as I have a little time, I'll put them all up on MIM::, along with other useful RSX stuff.
MOIRA::CSMELOSKY$ set host mandy
%SYSTEM-F-PROTOCOL, network protocol error
MANDY:: being the PDP-11? What is MOIRA::?
Yeah. MOIRA:: is my VAXstation 4000/60.
Hmm. What version of RSX and DECnet did you install?
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 Sun, 25 May 2014, Johnny Billquist wrote:
Glad good scans exist! ;)
It used to be that Stromasys had them available, but right now I can't seem to find the page I used to look at...
I'm sure they're around somewhere.
MOIRA::CSMELOSKY$ set host mandy
%SYSTEM-F-PROTOCOL, network protocol error
MANDY:: being the PDP-11? What is MOIRA::?
Yeah. MOIRA:: is my VAXstation 4000/60.
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On 2014-05-25 16:28, Cory Smelosky wrote:
On Sun, 25 May 2014, Cory Smelosky wrote:
LAT works!
Uhhh. Except it crashes when someone logs out.
10:26:53 Logout user SMELOSKY [300,1] TT11:
CRASH -- CONT WITH SCRATCH MEDIA ON MU000
004251
Confirmed and reproduced. I think my DECnet and RSX-11M+ versions are a
bit mismatched.
Could be...
Did you do a netgen after building RSX?
Also, I hope you are not using the lat programs that someone wrote under Unix, since they are breaking the protocols in some way. I have never bothered to find out exactly how, but they do not play nicely with RSX. A real DECserver works fine, though.
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 2014-05-25 16:06, Cory Smelosky wrote:
On Sun, 25 May 2014, Johnny Billquist wrote:
Yeah. I'm skimming the Manager's guide (which doesn't actually have the
commands. Seriously. There are blank spaces where the command
should be)
I think you've found a scan where anything in red turned invisible.
There are other scans of the manuals that are better.
Glad good scans exist! ;)
It used to be that Stromasys had them available, but right now I can't seem to find the page I used to look at...
However, by default, the system manager account has the password
"SYSTEM" if I remember right. And that leaves you logged in with
privileges...
Yup!
Also: it's up!
Event type 4.15, Adjacency up
Occurred 25-MAY-14 10:04:39 on node 9.4 (MANDY)
Circuit QNA-0
Adjacent node = 9.1023 (A9RTR)
...that does not however mean it WORKS.
MOIRA::CSMELOSKY$ set host mandy
%SYSTEM-F-PROTOCOL, network protocol error
MANDY:: being the PDP-11? What is MOIRA::?
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 Sun, 25 May 2014, Cory Smelosky wrote:
LAT works!
Uhhh. Except it crashes when someone logs out.
10:26:53 Logout user SMELOSKY [300,1] TT11:
CRASH -- CONT WITH SCRATCH MEDIA ON MU000
004251
Confirmed and reproduced. I think my DECnet and RSX-11M+ versions are a bit mismatched.
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
