[HECnet] How do you connect to HECnet?

Steve Davidson jeep at scshome.net
Mon Mar 2 06:30:52 PST 2009


My NetBSD machine runs the two NIC's so that I *can* keep DECnet apart from IP.   I have dedicated LAN's for each protocol here.   Overkill???   Absolutely!   It allows me to duplicate the multiple environments that I may encounter during the course of things.   It sure does make it easier when debugging a network problem/outage.
  
The VAXen have only one NIC and as such run only DECnet (and of course SCS traffic).   IP is relegated to other machines/hardware/paths.   It does take more hardware but in the end it is VERY clean.   The Alpha's, on the other hand,  have multiple NIC's - one for IP, one for DECnet, and one other.
  
-Steve
  


From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Sampsa Laine
Sent: Monday, March 02, 2009 09:16
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] How do you connect to HECnet?


Weirdly enough, I have no problem with running the bridge and SIMH on the same machine - caveat: I am running on OS X.

At the moment, I have the following:

- Gorilla (OS X 10.4.something) running the bridge on interface 0
- GORVAX (SIMH, OpenVMS 7.3, MULTINET) running on interface 0, acting as a router between the bridge and a MULTINET tunnel to the outside
- CHIMPY (running VMS 8.3, TCP/IP services), acting as an end node on the bridged network

So on the main host, there's only one interface and it all works (all = DECNET, I can't get IP traffic from Gorilla to GORVAX).

Sampsa

On 2 Mar 2009, at 09:50, Angela Kahealani wrote:
On Sunday, 2009-03-01 21:50:24 Johnny Billquist wrote:
The one limitation is that it is usually problematic to have the same
machine that is running the bridge also participate as a DECnet node
on the same interface. Because then you need to see all your own
outgoing packets. Not all hardware will do that for you.

So, if you try to run in one machine,
with hardware that can't see its own packets,
then you need 3 interfaces,
1: To talk TCP/IP / UDP for main interface plus UDP side of bridge
2: DECnet side of bridge
3: DECnet speaking software

or

a machine with only one interface running the bridge program, and
a machine with two interfaces, one for TCP/IP/UDP and one DECnet.

Or have I still misunderstood?

Aloha, Angela
-- 
"(I'll) Be Seeing You..."       All information and transactions are
private between the parties, and are non negotiable.     All rights
reserve without prejudice, Angela Kahealani. http://kahealani.com



More information about the Hecnet-list mailing list