HECnet

hecnet@lists.dfupdate.se

3 participants
15583 discussions

GORVAX MULTINET tunnel and CHIMPY's bridge are moving IPs soon

by sampsa＠mac.com

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

17 years, 2 months

DECnet on KLH10

by phiber＠phiber.com

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...

17 years, 2 months

DECnet on KLH10

by healyzh＠aracnet.com

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

17 years, 2 months

DECnet on KLH10

by phiber＠phiber.com

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...

17 years, 2 months

DECnet on KLH10

by phiber＠phiber.com

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

17 years, 2 months

Bridge

by ploopster＠gmail.com

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

17 years, 2 months

Node rename

by christine.caulfield＠googlemail.com

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

17 years, 2 months

DECnet on KLH10

by bqt＠softjar.se

17 years, 2 months

Node rename

by bqt＠softjar.se

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.

17 years, 2 months

Node rename

by Christine.Caulfield＠googlemail.com

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

17 years, 2 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet