I'll be out today, but I'll change it for you when I get back tonight.
Bob
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf
Of Sampsa Laine
Sent: Saturday, September 13, 2008 3:43 AM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] GORVAX MULTINET tunnel and CHIMPY's bridge are moving
IPs soon
Argh,
My DNS wasn't set up correctly so the IP addresses in my previous
message were all wrong:
- CHIMPY's bridge remains on 78.86.123.26 port 4711/UDP
- GORVAX's MULTINET tunnel has been moved to 78.86.123.31, port
700/UDP
Sampsa
PS: The original address for GORVAX's MULTINET tunnel will work as
well until I confirm everyone can connect to the new address.
On 13 Sep 2008, at 11:36, Sampsa Laine wrote:
Well it would impolite to just turn off the old tunnel wouldn't it,
so I've left both port redirections on for now :)
Can you try try to speak to GORVAX's new address in which case I can
turn off the port forward on the old one.
Sampsa
On 13 Sep 2008, at 04:17, Bob Armstrong wrote:
- GORVAX's tunnel will be on port 700/UDP on address 78.86.120.236
(gvax.sampsa.com).
Are you sure? LEGATO appears to be talking to GORVAX now, on
78.86.123.26.
Bob
Argh,
My DNS wasn't set up correctly so the IP addresses in my previous message were all wrong:
- CHIMPY's bridge remains on 78.86.123.26 port 4711/UDP
- GORVAX's MULTINET tunnel has been moved to 78.86.123.31, port 700/UDP
Sampsa
PS: The original address for GORVAX's MULTINET tunnel will work as well until I confirm everyone can connect to the new address.
On 13 Sep 2008, at 11:36, Sampsa Laine wrote:
Well it would impolite to just turn off the old tunnel wouldn't it, so I've left both port redirections on for now :)
Can you try try to speak to GORVAX's new address in which case I can turn off the port forward on the old one.
Sampsa
On 13 Sep 2008, at 04:17, Bob Armstrong wrote:
- GORVAX's tunnel will be on port 700/UDP on address 78.86.120.236
(gvax.sampsa.com).
Are you sure? LEGATO appears to be talking to GORVAX now, on
78.86.123.26.
Bob
Well it would impolite to just turn off the old tunnel wouldn't it, so I've left both port redirections on for now :)
Can you try try to speak to GORVAX's new address in which case I can turn off the port forward on the old one.
Sampsa
On 13 Sep 2008, at 04:17, Bob Armstrong wrote:
- GORVAX's tunnel will be on port 700/UDP on address 78.86.120.236
(gvax.sampsa.com).
Are you sure? LEGATO appears to be talking to GORVAX now, on
78.86.123.26.
Bob
- GORVAX's tunnel will be on port 700/UDP on address 78.86.120.236
(gvax.sampsa.com).
Are you sure? LEGATO appears to be talking to GORVAX now, on
78.86.123.26.
Bob
Gentlemen,
I've finally figured out how to make more use of my range of static IPs so GORVAX and CHIMPY will be changing IP addresses:
- CHIMPY's bridge will be on port 4711/UDP on address 78.86.123.29 (chimpy.sampsa.com)
- GORVAX's tunnel will be on port 700/UDP on address 78.86.120.236 (gvax.sampsa.com).
Sorry about any inconvenience.
Sampsa
I wanted to be doing a netstat -ani, (-g only shows multicast for
ipv4/6), but the result is the same. None of the DECnet multicast
addresses are being added, most notably (and absolutely necessary) are:
ab:0:0:3:0:0 - type 6003 - for DECnet Phase IV end node Hello packets
from each host, and
ab:0:0:4:0:0 - type 6003 - for DECnet Phase IV router Hello packets from
the router.
I've tried adding these with both enaddr from KLH10 and FreeBSD's
built-in "mtest", but both return errors. This seems to be a
FreeBSD-specific problem which so far I'm unable to find the reason for.
Mark
Mark Abene wrote:
Mark Abene wrote:
I've actually made a new discovery... looking at "netstat -g", I'm
seeing that none of the multicast addresses exist that DECnet uses and
requires! This would explain why I don't see any DECnet traffic at all.
I compiled KLH10's enaddr utility in an attempt to add the multicast
addresses manually, and I get failures for all attempts...
"SIOCADDMULTI failed - Can't assign requested address". My server's
kernel wasn't built with multicast routing enabled, which is not a
default. I'm wondering if this is the cause of the error. I'm going to
do some further testing.
Regards
Mark
Well I was mistaken about the multicast routing, that's only for doing
DVMRP with mrouted (MBONE, etc). Local LAN multicast should work "out
of the box" on FreeBSD. Still trying to track down why this is failing,
since it's my primary candidate for DECnet not working...
Mark Abene wrote:
Is anyone on here successfully using DECnet in TOPS-20 with the KLH10
emulator? I'm using a dedicated bridged-tap interface in FreeBSD, and
DECnet is certainly enabled in TOPS-20, but there is absolutely no
DECnet traffic on the wire. None can be seen with tcpdump. I find this
very odd. IP connectivity works fine, and I can see LAT traffic, but no
DECnet. Any suggestions?
Well, I can only say that we have one KLH10 system (PAMINA::) running
here. Works fine. But it's running on a Linux box, and also have a
dedicated physical interface.
No ideas why it don't work for you.
Johnny
Personally I've always recommended Linux/x86 and a dedicated interface for
KLH10. For SIMH I just run on whatever is handy, but I've never gotten
networking going with SIMH (I've used real PDP-11 hardware or E11 instead).
As I recall I've had DECnet running with TOPS-10 7.04 on KLH10, and TCP/IP
for TOPS-20. At the time I was messing with it I wasn't really using
DECnet, just LAT and TCP/IP. Plus I'm not sure, but I don't believe DECnet
was an option for TOPS-20 at that time. LAT is real nice since if you have
a DECserver and terminals, you can easily use a real terminal with KLH10.
Zane
Zane
Mark Abene wrote:
I've actually made a new discovery... looking at "netstat -g", I'm
seeing that none of the multicast addresses exist that DECnet uses and
requires! This would explain why I don't see any DECnet traffic at all.
I compiled KLH10's enaddr utility in an attempt to add the multicast
addresses manually, and I get failures for all attempts...
"SIOCADDMULTI failed - Can't assign requested address". My server's
kernel wasn't built with multicast routing enabled, which is not a
default. I'm wondering if this is the cause of the error. I'm going to
do some further testing.
Regards
Mark
Well I was mistaken about the multicast routing, that's only for doing
DVMRP with mrouted (MBONE, etc). Local LAN multicast should work "out
of the box" on FreeBSD. Still trying to track down why this is failing,
since it's my primary candidate for DECnet not working...
Mike Shields wrote:
Mark -
I have a TOPS-20 setup on KLH10, running on a Solaris host wtih a dedicated
ethernet card for the KLH10 instance.
I'd try to help you but I honestly don't know how to configure DECnet on
TOPS-20. My goal is to get DECnet working,
At a minimum, you simply need to add the following to your system config
file (depending on your TOPS-20 version, SYSTEM:7-1-CONFIG.CMD or
similar)...
NODE MYNODE 1.123
ETHERNET 0 DECNET
DECNET ROUTER-ENDNODE
Replace "MYNODE" with your 6-letter nodename, and "1.123" with your node
number. The "0" (zero) for ETHERNET may need to be adjusted if you have
more than one network interface, but "0" is correct for the first NI0
interface. I'm fairly certain the third directive indicates that you're
an end node and are not effecting any DECnet routing yourself.
and one of the reasons I put a dedicated ethernet card in was that I read
DECnet changes the MAC address to some
specific value corresponding with the node number. For some reason I didn't
think that'd work very well with bridging/tap.
(Though it may work just fine, it was just a gut feel)
It works just fine actually. Problem at least on FreeBSD is that the
bridge ceases to function if any of the bridged interface's MAC
addresses changes without simply cycling the bridge down and up again.
Because of this I disabled the MAC address change in KLH10 and do it
manually.
Well, anyways, let me know if you want to collaborate on getting both our
systems working.
Mike
I've actually made a new discovery... looking at "netstat -g", I'm
seeing that none of the multicast addresses exist that DECnet uses and
requires! This would explain why I don't see any DECnet traffic at all.
I compiled KLH10's enaddr utility in an attempt to add the multicast
addresses manually, and I get failures for all attempts...
"SIOCADDMULTI failed - Can't assign requested address". My server's
kernel wasn't built with multicast routing enabled, which is not a
default. I'm wondering if this is the cause of the error. I'm going to
do some further testing.
Regards
Mark
I'm probably going to be running an exhibit this weekend where I connect a VAX to hecnet. I will need to set up a node temporarily with the bridge. Can I peer with someone? It would be great if you can assign me a node number in your area temporarily. Thanks.
Peace... Sridhar
Johnny Billquist wrote:
Bob Armstrong wrote:
I made this change on LEGATO too.
Not that it matters, but LEGATO thinks the adjacent node on the
circuit is
3.34, ROOSTA. From your numbering system, this must be some kind of
VAX or
Alpha.
.ncp tell roosta sho exec
Node summary as of 12-SEP-08 10:57:27
Executor node = 3.34 (ROOSTA)
State = On, Identification = DECnet for OpenVMS VAX V7.2
:-)
That's one of the reasons I wrote NML for Linux.
Incidentally, that now works on big-endian systems too. I found the bug :)
--
Chrissie
Mark Abene wrote:
Is anyone on here successfully using DECnet in TOPS-20 with the KLH10
emulator? I'm using a dedicated bridged-tap interface in FreeBSD, and
DECnet is certainly enabled in TOPS-20, but there is absolutely no
DECnet traffic on the wire. None can be seen with tcpdump. I find this
very odd. IP connectivity works fine, and I can see LAT traffic, but no
DECnet. Any suggestions?
Well, I can only say that we have one KLH10 system (PAMINA::) running here. Works fine. But it's running on a Linux box, and also have a dedicated physical interface.
No ideas why it don't work for you.
Johnny
Bob Armstrong wrote:
I made this change on LEGATO too.
Not that it matters, but LEGATO thinks the adjacent node on the circuit is
3.34, ROOSTA. From your numbering system, this must be some kind of VAX or
Alpha.
.ncp tell roosta sho exec
Node summary as of 12-SEP-08 10:57:27
Executor node = 3.34 (ROOSTA)
State = On, Identification = DECnet for OpenVMS VAX V7.2
:-)
Johnny
Bob
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf
Of Christine Caulfield
Sent: Thursday, September 11, 2008 5:31 AM
To: hecnet at Update.UU.SE
Subject: [HECnet] Node rename
I'm going to be a pest now, sorry.
My old node ZAPHOD died over a year ago. However I now have a new node
so I'm reusing the name.
This next bit might sound slightly anal but bear with me. The old Zaphod
was an Alpha so it had a node number 3.33. The new one is
a macmini running Linux (and I hope to replace fentib) so has a node
number of 3.55.
My numbering scheme (as if you cared) goes
01-19 PCs
20-30 hmm, I forget now. I'm sure I had some once though.
30-39 DEC systems
40-49 HP systems
50-59 Apple systems
60-69 Sun systems
So, anyway the point is that can you please renumber ZAPHOD from 3.33 to
3.55. Sorry.
Bob Armstrong wrote:
I made this change on LEGATO too.
Not that it matters, but LEGATO thinks the adjacent node on the circuit is
3.34, ROOSTA. From your numbering system, this must be some kind of VAX or
Alpha.
Yes it's a VAX.
Well, actually it's a simh 'vax'. My real ones are too noisy and/or hot
to run in the summer so I though it would be more reliable to have it
run this way. At least I can keep it going all the time now :)
--
Chrissie
Is anyone on here successfully using DECnet in TOPS-20 with the KLH10
emulator? I'm using a dedicated bridged-tap interface in FreeBSD, and
DECnet is certainly enabled in TOPS-20, but there is absolutely no
DECnet traffic on the wire. None can be seen with tcpdump. I find this
very odd. IP connectivity works fine, and I can see LAT traffic, but no
DECnet. Any suggestions?
Regards,
Mark
I made this change on LEGATO too.
Not that it matters, but LEGATO thinks the adjacent node on the circuit is
3.34, ROOSTA. From your numbering system, this must be some kind of VAX or
Alpha.
Bob
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf
Of Christine Caulfield
Sent: Thursday, September 11, 2008 5:31 AM
To: hecnet at Update.UU.SE
Subject: [HECnet] Node rename
I'm going to be a pest now, sorry.
My old node ZAPHOD died over a year ago. However I now have a new node
so I'm reusing the name.
This next bit might sound slightly anal but bear with me. The old Zaphod
was an Alpha so it had a node number 3.33. The new one is
a macmini running Linux (and I hope to replace fentib) so has a node
number of 3.55.
My numbering scheme (as if you cared) goes
01-19 PCs
20-30 hmm, I forget now. I'm sure I had some once though.
30-39 DEC systems
40-49 HP systems
50-59 Apple systems
60-69 Sun systems
So, anyway the point is that can you please renumber ZAPHOD from 3.33 to
3.55. Sorry.
--
Chrissie
Christine Caulfield wrote:
I'm going to be a pest now, sorry.
My old node ZAPHOD died over a year ago. However I now have a new node
so I'm reusing the name.
This next bit might sound slightly anal but bear with me. The old Zaphod
was an Alpha so it had a node number 3.33. The new one is
a macmini running Linux (and I hope to replace fentib) so has a node
number of 3.55.
My numbering scheme (as if you cared) goes
01-19 PCs
20-30 hmm, I forget now. I'm sure I had some once though.
30-39 DEC systems
40-49 HP systems
50-59 Apple systems
60-69 Sun systems
So, anyway the point is that can you please renumber ZAPHOD from 3.33 to
3.55. Sorry.
No problemo. :-)
I've done it on MIM now.
Johnny
I think I've found a solution for the infamous SMG bug on releases for which
actually HP does not (still) provide a patch: I've discovered that the
official published patch for OpenVMS VAX V7.3 works apparently flawlessy even
on V7.2 and maybe also on older releases like V7.1 and so on.
Obviously it cannot be installed via VMSINSTAL because the kit does check for
the correct version and release, but it's always possibile to extract the new
SMGSHR.EXE file from the kit and put it in place. To be safe, I've copied it
to the specific portion of my system root (e.g. DKA0:[SYS0.SYSLIB]) instead of
the better common one, but I do not have a cluster and SYS$SHARE does point to
both locations, so I've achieved the same result. After that I've just typed
INSTALL REPLACE SYS$SHARE:SMGSHR.EXE/OPEN/HEADER/SHARED and that's it!
I've done the same for my OpenVMS Alpha V7.2 system by using the V7.3-2 patch,
but in that case a newer release is temporarily needed to extract SMGSHR.EXE
from the PCSI kit because it's in the new compressed form that's not supported
by V7.2 (I do not know when it was introduced, I used a V8.2 to extract).
In the next few days, if I'll see that everything works without any problems,
maybe I'll rename the original SMGSHR.EXE file and replace it with the new one
so to have just one of it and in the right place.
Hope this helps!
G.
I'm going to be a pest now, sorry.
My old node ZAPHOD died over a year ago. However I now have a new node
so I'm reusing the name.
This next bit might sound slightly anal but bear with me. The old Zaphod
was an Alpha so it had a node number 3.33. The new one is
a macmini running Linux (and I hope to replace fentib) so has a node
number of 3.55.
My numbering scheme (as if you cared) goes
01-19 PCs
20-30 hmm, I forget now. I'm sure I had some once though.
30-39 DEC systems
40-49 HP systems
50-59 Apple systems
60-69 Sun systems
So, anyway the point is that can you please renumber ZAPHOD from 3.33 to
3.55. Sorry.
--
Chrissie
I'm very pleased to announce the new dnprogs release. With not one, not
two, but FOUR new programs - you lucky people :-)
The first two were contributed by Philipp 'ph3-der-loewe' Schafft and
consist of two command-line utilities:
dnetstat is a version of netstat for DECnet, it reformats the /proc file
output in a more user-friendly manner.
dnetcat is a DECnet version of netcat, an invaluable utility for all
network nerds. Philipp has offered to update the wiki to show how to use
this utility to run SSH over DECnet!
And finally, I have also been busy. I have done something I said I'd
write years ago and that's an Network Management Listener program. Yes,
finally you can go into NCP on a VMS or RSX system (yes, I tested it on
RSX, thanks Johnny) and type in "TELL LINUX SHOW ADJACENT NODES". It
only supports a subset of commands at the moment, but I will probably
add more. It currently will do:
SHOW/LIST KNOWN NODES
SHOW ADJACENT NODES
SHOW EXEC CHAR
To make this work you'll need to add a new line to dnetd.conf - see the
sample file shipped with the package for the details.
There's also a client side version of that, well partly. dncopynodes
allows a Linux user to pull a node list off a remote VMS or RSX system
and build up a full decnet.conf file. It will fill in the current exec
details too so that the file it generates can simply be copied to /etc.
WARNING ... DO NOT do 'dncopynodes > /etc/decnet.conf' as it will
overwrite the file before it gets a chance to use it to make the initial
connection!
http://sourceforge.net/project/showfiles.php?group_id=4993&package_id=5032&…
--
Chrissie
It looks like I'll be going off-line next weekend, probably either the 6th or 7th. I don't know how long PDXVAX and MONK will be down. I don't even know when I'll be back back on the Internet. We just found out that we're moving yesterday and that we're to move on the 6th and 7th (we thought it was the middle of September). Worse, I'm trying to get our phone and internet access sorted out as I was told this morning that FIOS is the only option (I should be able to get DSL), which means I need a Verizon business line to continue getting the level of service I've had. That will cost over twice what I'm paying now. I suspect this is such short notice that no mater what happens I'm going to be without phone and Internet service for a while.
This hasn't been a good day.
Zane
--
| Zane H. Healy | UNIX Systems Administrator |
| healyzh at aracnet.com (primary) | OpenVMS Enthusiast |
| MONK::HEALYZH (DECnet) | Classic Computer Collector |
+----------------------------------+----------------------------+
| Empire of the Petal Throne and Traveller Role Playing, |
| PDP-10 Emulation and Zane's Computer Museum. |
| http://www.aracnet.com/~healyzh/ |
On Thu, 28 Aug 2008, Zane H. Healy wrote:
How long has your node been online? I just updated the list of known nodes on MONK. How about trying again?
Perhaps a week or two?
I'll reply to my test post and see what happens ...
Fred
At 8:34 AM -0400 8/28/08, Fred wrote:
On Wed, 27 Aug 2008, Zane H. Healy wrote:
Notes> open/nonotebook MONK::TEST
It started working once I did this. I don't claim to understand.
Also, I just upgraded to "HP Notes T2.6" on MONK.
I'm wondering if the upgrade somehow fixed it.
It did not seem to. Trust me, I did a lot of testing last night from PDXVAX.
Tried the open/nonotebook monk::test - worked!
Out of curiousity, I then tried to open an entry I had already added yesterday - that previously showed an error. Worked!
That was the result I had from PDXVAX, except I already had all of the notes conferences under my account there. I simply had to do the
open/nonotebook monk::test
and then everything worked, and the /nonotebook option was no longer needed. The one thing I don't know is what would have happened if I'd used that option when talking to "DEC Notes V2.5" prior to the upgrade.
I was able to successfully post into the TEST conference, although my node shows up as decimal, not the actualy node name ... :-/
How long has your node been online? I just updated the list of known nodes on MONK. How about trying again?
Zane
--
| Zane H. Healy | UNIX Systems Administrator |
| healyzh at aracnet.com (primary) | OpenVMS Enthusiast |
| MONK::HEALYZH (DECnet) | Classic Computer Collector |
+----------------------------------+----------------------------+
| Empire of the Petal Throne and Traveller Role Playing, |
| PDP-10 Emulation and Zane's Computer Museum. |
| http://www.aracnet.com/~healyzh/ |
On Wed, 27 Aug 2008, Zane H. Healy wrote:
Notes> open/nonotebook MONK::TEST
It started working once I did this. I don't claim to understand.
Also, I just upgraded to "HP Notes T2.6" on MONK.
I'm wondering if the upgrade somehow fixed it.
Tried the open/nonotebook monk::test - worked!
Out of curiousity, I then tried to open an entry I had already added yesterday - that previously showed an error. Worked!
I was able to successfully post into the TEST conference, although my node shows up as decimal, not the actualy node name ... :-/
Fred
Fred,
Try this.
Notes> open/nonotebook MONK::TEST
It started working once I did this. I don't claim to understand.
Also, I just upgraded to "HP Notes T2.6" on MONK.
Zane
--
| Zane H. Healy | UNIX Systems Administrator |
| healyzh at aracnet.com (primary) | OpenVMS Enthusiast |
| MONK::HEALYZH (DECnet) | Classic Computer Collector |
+----------------------------------+----------------------------+
| Empire of the Petal Throne and Traveller Role Playing, |
| PDP-10 Emulation and Zane's Computer Museum. |
| http://www.aracnet.com/~healyzh/ |