On Wed, 20 Aug 2008, Bob Armstrong wrote:
The first step is to download and install Multinet -
http://www.process.com/openvms/hobbyist.html
Speaking of Multinet, I've got my Hobbyist License and /register'ed it and /load'ed it. Got the savesets in a directory ready to install, but I thought of something - probably should do this from the console, and in addition - pardon this question but will installing Multinet "upgrade" me from HP TCP/IP or will it work in conjunction? I've never been on this side of OpenVMS before, normally I just run the system that's already been prepared for me on the application side ... :-/
Cheers,
Fred
John Floren [slawmaster at gmail.com] wrote:
I'd be interested in connecting my Alphastation with Multinet, if
possible. I've got cable internet and all my machines are behind a
router... pointers and directions would be appreciated!
We don't have a guide to doing this; perhaps if I talk you thru it you'll write one for us.
The first step is to download and install Multinet -
http://www.process.com/openvms/hobbyist.html
Bob
http://www.avanthar.com:8080/nodes/
seems to not be working to list currently active HECnet nodes.
My area router is down, and as I am getting ready to move, I think it will
be a minimum of 2-4 weeks before I get it back online. It went down due to
"screaming bearings". It is a VAXstation 4000/vlc, and I'll likely look
into ways to quiet it down and set things up so I can swap in either a
VAXstation 4000/60 or /90.
Though I should see if it has sat long enough to quiet down... As crazy as
it might sound, it fixed itself the last time.
Zane
On Wed, 2008-08-20 08:16:57 Johnny Billquist wrote:
Hmm. Is this the same machine as is running the bridge?
Johnny
Yes, is that a problem?
Could very well be. The problem is that the bridge program cannot
exactly feed the ethernet input on the same machine as it is running,
nor hear data sent out on the ethernet port of the same machine. That
is, unless the hardware will do this for you. Some hardware do, but most
don't. So you don't see your own data, which makes it impossible for my
bridge program to handle the machine it itself is running on.
Johnny
I think I separated the bridge and linuxDECnet dnetd
onto separate NICs so they can see each other...
dnetinfo shows:
The next hop to the nearest area router is node 0.0
Node Cost Hops Next hop to node
1.10 4 1 if0 -> 1.266
1.500 kahea 0 0 lo -> 1.500 kahea
but I don't seem to see any neighbors, so maybe still not right.
--
"(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
On Mon, Aug 18, 2008 at 12:10 PM, Bob Armstrong <bob at jfcl.com> wrote:
Fred wrote:
that is runinng DECNet over IP
that could allow me onto the network.
There are several ways to do DECnet over IP, including Multinet, Johnny's
bridge program, certain models of Cisco routers, and Linux DECnet, plus
maybe more that I don't know about. Unfortunately none of them are really
compatible, so you'll have to say which one you want to use before we can
help.
If you're using Multinet, then I'll be glad to connect you.
BTW, I notice your "dyndns" address - most of these aren't really usable
unless you have a static IP. All these connection methods are based on
actual IPs and not DNS entries, so anytime your dynamic IP changed the guy
at the other end of your tunnel would have to reconfigure your connection.
That gets old pretty fast.
Bob
I'd be interested in connecting my Alphastation with Multinet, if
possible. I've got cable internet and all my machines are behind a
router... pointers and directions would be appreciated!
John
--
Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn
http://www.avanthar.com:8080/nodes/
seems to not be working to list currently active HECnet nodes.
--
"(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
On Wed, 2008-08-20 08:16:57 Johnny Billquist wrote:
Angela Kahealani wrote:
On Wed, 2008-08-20 08:00:35 Johnny Billquist wrote:
Angela Kahealani wrote:
So, obviously my iptables ain't blocking DECnet,
so it's a mystery why I can only see:
pc:/etc# cat /proc/net/decnet_neigh
Addr Flags State Use Blksize Dev
1.500 --- 40 01 0001498 eth0
1.10 --- 40 01 0016434 lo
Aloha, Angela
Hmm. Is this the same machine as is running the bridge?
Johnny
Yes, is that a problem?
Could very well be. The problem is that the bridge program cannot
exactly feed the ethernet input on the same machine as it is running,
nor hear data sent out on the ethernet port of the same machine. That
is, unless the hardware will do this for you. Some hardware do, but most
don't. So you don't see your own data, which makes it impossible for my
bridge program to handle the machine it itself is running on.
Johnny
I have a router on the LAN, so could it all be configured
to use that to bounce packets right back?
I take it most internet routers aren't going to route UDP/700?
which is why the bridge program vs sending raw DECNET UCP/700?
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
Address Name Machine Location
1.400 GORVAX SIMH-VAX London
1.401 CHIMPY AlphaServer 800 London
1.402 CHIMP AlphaServer 4100 (Probably Kirkkonummi, Finland, not active right now)
Sampsa
On 20 Aug 2008, at 18:50, Bob Armstrong wrote:
Here s an updated node listing with some of the recent additions. If any
are missing or incorrect, let me know the details and I ll update the list.
http://www.sparetimegizmos.com/Downloads/DCN%20Node%20List.pdf
Bob
Angela Kahealani wrote:
On Wed, 2008-08-20 08:00:35 Johnny Billquist wrote:
Angela Kahealani wrote:
So, obviously my iptables ain't blocking DECnet,
so it's a mystery why I can only see:
pc:/etc# cat /proc/net/decnet_neigh
Addr Flags State Use Blksize Dev
1.500 --- 40 01 0001498 eth0
1.10 --- 40 01 0016434 lo
Aloha, Angela
Hmm. Is this the same machine as is running the bridge?
Johnny
Yes, is that a problem?
Could very well be. The problem is that the bridge program cannot exactly feed the ethernet input on the same machine as it is running, nor hear data sent out on the ethernet port of the same machine. That is, unless the hardware will do this for you. Some hardware do, but most don't. So you don't see your own data, which makes it impossible for my bridge program to handle the machine it itself is running on.
Johnny
