-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Rob Jarratt
Sent: Monday, November 19, 2012 17:57
To: hecnet at Update.UU.SE
Cc: 'Stuart Martin'
Subject: RE: [HECnet] Joining hecnet
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
On Behalf Of Johnny Billquist
Sent: 19 November 2012 20:00
To: hecnet at Update.UU.SE
Cc: Stuart Martin
Subject: Re: [HECnet] Joining hecnet
On 2012-11-19 19:15, Stuart Martin wrote:
On 19 November 2012 18:07, Jerome Ibanes <jibanes at gmail.com
<mailto:jibanes at gmail.com>> wrote:
Hello,
I have an openvms 7.3-2/vax and 8.4/alpha
workstations I would
like
to
attach to the hecnet network. I have a static IP and
the bridge
setup,
although I imagine I would need a hecnet node-name
and number at
this
point.
hi folks.
"me too": I've got an alphaserver with OpenVMS 8.4 ready to roll.
I've got Rob Jarratt's router running on a spare linux box
(raspberry pi, since you asked) because I don't have a static IP.
The router code's not configured yet.
I'm a DECnet newbie, so would appreciate some abbreviated hecnet
directions if any exist (and if not, a pointer to just go
away and
read the DECnet manuals is equally welcome).
I'm in the UK. Is hecnet organised by geographic region?
Like already answered, HECnet is not organized that way.
As for connecting, if you have Jarratt's code up and running, you
might
want
to try and hook up with him?
Other questions to figure out is if you are going in a new area, or
connecting
into an existing one.
This matters both since if you are using an existing area,
you need to
use
the
same area as the next person you connect to.
If you go for your own area, you instead need an area
router on your
side, and a connection to another area router.
And then we have the question about node names, which is
more loosely
regulated. It's pretty much a question of picking names not
already in
use.
Having a dynamic IP address is a cause for some problems.
Let's see if
Jarratt's router will handle it well.
Johnny
The point about the router I wrote is that if you have a
dynamic IP address it needs the *peer* to use it. That is
because it periodically queries DNS (in a non-blocking
manner) for your IP address. Clearly there will be a period
after an IP address change when the router will send packets
to the wrong address, but the poll period can be set to
whatever period you wish.
The router will interoperate with the bridge, I run it here
and I don't think anyone on HECnet notices a difference other
than that it does not implement other protocols, so you can't
SET HOST to it for example. So there is no specific need to
peer with me, but I am happy to do so, if you want to peer
with me give me your DNS name and port number, mine is
jarratt.dyndns.org:4713 (one limitation I ought to fix is the
need for a separate port for each peer). Note that since I
connect to the rest of HECnet via Johnny, and he is not using
the router, I could lose connectivity to HECnet if my IP
address changes, because I too have a dynamic IP address, but
luckily my ISP does not make it change often.
The router works as an area router so you might need to have
your own area.
It can also work as a non-area router, and this configuration
has not been tested quite as much.
Regards
Rob
Currently, we have two (2) Multinet Tunnel Routers that can deal with
Dynamic IP Addresses. One is in the US (SG1::) , and the other is in
the UK (GORVAX::). If you are running Multinet then the other end just
does the magic. The polling interval is configurable so downtime can be
minimized. No special configuration is required on your part. Contact
me directly if you wish to go this route.
Regards,
-Steve
From: Dave McGuire <mcguire at neurotica.com>
It's just such an amazingly bad match for that type of hardware
architecture. *shudder*
Yeah we had it at RPI and it was insanely slow. Sometimes it would drop
you during login because it couldn't process your username/password within
the 60-second timeout. And the software BS didn't help. The C compiler
was High-C and it had all kinds of bugs including choking on its own
#include files.
Another side of the same mainframe ran MTS (from UMich) and a lot of people
never got over the culture shock, but it sure ran like a bat outta hell!
So it wasn't a slow computer, unless they horribly misconfigured the VM
AIX/370 was in, I guess.
John Wilson
D Bit
P.S. I wrote the ROM half of PD.SYS for E11's new PDT-11/150 emulation and
now I'm working on the PDT-11/130 (TU58 with mutated DLV11) version for
good measure ... but slightly sidetracked attempting Terak stuff. I guess
this release is going to be all about the weird LSI-11-based micros!
On 11/19/2012 08:40 PM, Gregg Levine wrote:
Well I could use a copy of AIX370....
If you could, you'd be the first! What a waste of a perfectly good mainframe.
I have to agree. I love UNIX, but running anything other than MVS on
something like that, or maybe VM, is just a sin.
Hello!
It ran under VM/370 and sadly had only one customer. Which is revolting.
It's just such an amazingly bad match for that type of hardware
architecture. *shudder*
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On Mon, Nov 19, 2012 at 8:38 PM, Dave McGuire <mcguire at neurotica.com> wrote:
On 11/19/2012 08:30 PM, John Wilson wrote:
From: Gregg Levine <gregg.drwho8 at gmail.com>
Well I could use a copy of AIX370....
If you could, you'd be the first! What a waste of a perfectly good mainframe.
I have to agree. I love UNIX, but running anything other than MVS on
something like that, or maybe VM, is just a sin.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
Hello!
It ran under VM/370 and sadly had only one customer. Which is revolting.
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
On 11/19/2012 08:38 PM, Dave McGuire wrote:
On 11/19/2012 08:30 PM, John Wilson wrote:
From: Gregg Levine <gregg.drwho8 at gmail.com>
Well I could use a copy of AIX370....
If you could, you'd be the first! What a waste of a perfectly good mainframe.
I have to agree. I love UNIX, but running anything other than MVS on
something like that, or maybe VM, is just a sin.
(that's not to say I wouldn't like to play with it, though.. ;))
--
Dave McGuire, AK4HZ
New Kensington, PA
On 11/19/2012 08:30 PM, John Wilson wrote:
From: Gregg Levine <gregg.drwho8 at gmail.com>
Well I could use a copy of AIX370....
If you could, you'd be the first! What a waste of a perfectly good mainframe.
I have to agree. I love UNIX, but running anything other than MVS on
something like that, or maybe VM, is just a sin.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
From: Gregg Levine <gregg.drwho8 at gmail.com>
Well I could use a copy of AIX370....
If you could, you'd be the first! What a waste of a perfectly good mainframe.
John Wilson
D Bit
-----Original Message-----
From: Johnny Billquist [mailto:bqt at softjar.se]
Sent: 19 November 2012 23:15
To: hecnet at Update.UU.SE
Cc: Rob Jarratt; 'Stuart Martin'
Subject: Re: [HECnet] Joining hecnet
On 2012-11-19 23:56, Rob Jarratt wrote:
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-
hecnet at Update.UU.SE]
On Behalf Of Johnny Billquist
Sent: 19 November 2012 20:00
To: hecnet at Update.UU.SE
Cc: Stuart Martin
Subject: Re: [HECnet] Joining hecnet
On 2012-11-19 19:15, Stuart Martin wrote:
On 19 November 2012 18:07, Jerome Ibanes <jibanes at gmail.com
<mailto:jibanes at gmail.com>> wrote:
Hello,
I have an openvms 7.3-2/vax and 8.4/alpha workstations I would
like
to
attach to the hecnet network. I have a static IP and the bridge
setup,
although I imagine I would need a hecnet node-name and number
at
this
point.
hi folks.
"me too": I've got an alphaserver with OpenVMS 8.4 ready to roll.
I've got Rob Jarratt's router running on a spare linux box
(raspberry pi, since you asked) because I don't have a static IP.
The router code's not configured yet.
I'm a DECnet newbie, so would appreciate some abbreviated hecnet
directions if any exist (and if not, a pointer to just go away and
read the DECnet manuals is equally welcome).
I'm in the UK. Is hecnet organised by geographic region?
Like already answered, HECnet is not organized that way.
As for connecting, if you have Jarratt's code up and running, you
might
want
to try and hook up with him?
Other questions to figure out is if you are going in a new area, or
connecting
into an existing one.
This matters both since if you are using an existing area, you need
to use
the
same area as the next person you connect to.
If you go for your own area, you instead need an area router on your
side, and a connection to another area router.
And then we have the question about node names, which is more loosely
regulated. It's pretty much a question of picking names not already
in
use.
Having a dynamic IP address is a cause for some problems. Let's see
if Jarratt's router will handle it well.
Johnny
The point about the router I wrote is that if you have a dynamic IP
address it needs the *peer* to use it. That is because it periodically
queries DNS (in a non-blocking manner) for your IP address. Clearly
there will be a period after an IP address change when the router will
send packets to the wrong address, but the poll period can be set to
whatever period you wish.
The router will interoperate with the bridge, I run it here and I
don't think anyone on HECnet notices a difference other than that it
does not implement other protocols, so you can't SET HOST to it for
example. So there is no specific need to peer with me, but I am happy
to do so, if you want to peer with me give me your DNS name and port
number, mine is
jarratt.dyndns.org:4713 (one limitation I ought to fix is the need for
a separate port for each peer). Note that since I connect to the rest
of HECnet via Johnny, and he is not using the router, I could lose
connectivity to HECnet if my IP address changes, because I too have a
dynamic IP address, but luckily my ISP does not make it change often.
Right. But if Stuart have a dynamic IP, then I think it would make sense
to
have him connected to you, as that means his change in address (if it were
to happen) would not be as much of a problem.
Like I said, I don't mind at all if Stuart wants to connect through me.
Stuart send me the details. Once I get them it will take me a few minutes to
set up the port forward and restart the router, but I am out most evenings
this week, so it may take a little while to get around to it.
The router works as an area router so you might need to have your own
area.
It can also work as a non-area router, and this configuration has not
been tested quite as much.
That should pretty much just mean he can choose to use his own area, or be
in the same area as the other end. Shouldn't make a difference.
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 2012-11-19 23:56, Rob Jarratt wrote:
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
On Behalf Of Johnny Billquist
Sent: 19 November 2012 20:00
To: hecnet at Update.UU.SE
Cc: Stuart Martin
Subject: Re: [HECnet] Joining hecnet
On 2012-11-19 19:15, Stuart Martin wrote:
On 19 November 2012 18:07, Jerome Ibanes <jibanes at gmail.com
<mailto:jibanes at gmail.com>> wrote:
Hello,
I have an openvms 7.3-2/vax and 8.4/alpha workstations I would like
to
attach to the hecnet network. I have a static IP and the bridge
setup,
although I imagine I would need a hecnet node-name and number at
this
point.
hi folks.
"me too": I've got an alphaserver with OpenVMS 8.4 ready to roll. I've
got Rob Jarratt's router running on a spare linux box (raspberry pi,
since you asked) because I don't have a static IP. The router code's
not configured yet.
I'm a DECnet newbie, so would appreciate some abbreviated hecnet
directions if any exist (and if not, a pointer to just go away and
read the DECnet manuals is equally welcome).
I'm in the UK. Is hecnet organised by geographic region?
Like already answered, HECnet is not organized that way.
As for connecting, if you have Jarratt's code up and running, you might
want
to try and hook up with him?
Other questions to figure out is if you are going in a new area, or
connecting
into an existing one.
This matters both since if you are using an existing area, you need to use
the
same area as the next person you connect to.
If you go for your own area, you instead need an area router on your side,
and a connection to another area router.
And then we have the question about node names, which is more loosely
regulated. It's pretty much a question of picking names not already in
use.
Having a dynamic IP address is a cause for some problems. Let's see if
Jarratt's router will handle it well.
Johnny
The point about the router I wrote is that if you have a dynamic IP address
it needs the *peer* to use it. That is because it periodically queries DNS
(in a non-blocking manner) for your IP address. Clearly there will be a
period after an IP address change when the router will send packets to the
wrong address, but the poll period can be set to whatever period you wish.
The router will interoperate with the bridge, I run it here and I don't
think anyone on HECnet notices a difference other than that it does not
implement other protocols, so you can't SET HOST to it for example. So there
is no specific need to peer with me, but I am happy to do so, if you want to
peer with me give me your DNS name and port number, mine is
jarratt.dyndns.org:4713 (one limitation I ought to fix is the need for a
separate port for each peer). Note that since I connect to the rest of
HECnet via Johnny, and he is not using the router, I could lose connectivity
to HECnet if my IP address changes, because I too have a dynamic IP address,
but luckily my ISP does not make it change often.
Right. But if Stuart have a dynamic IP, then I think it would make sense to have him connected to you, as that means his change in address (if it were to happen) would not be as much of a problem.
The router works as an area router so you might need to have your own area.
It can also work as a non-area router, and this configuration has not been
tested quite as much.
That should pretty much just mean he can choose to use his own area, or be in the same area as the other end. Shouldn't make a difference.
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
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
On Behalf Of Johnny Billquist
Sent: 19 November 2012 20:00
To: hecnet at Update.UU.SE
Cc: Stuart Martin
Subject: Re: [HECnet] Joining hecnet
On 2012-11-19 19:15, Stuart Martin wrote:
On 19 November 2012 18:07, Jerome Ibanes <jibanes at gmail.com
<mailto:jibanes at gmail.com>> wrote:
Hello,
I have an openvms 7.3-2/vax and 8.4/alpha workstations I would like
to
attach to the hecnet network. I have a static IP and the bridge
setup,
although I imagine I would need a hecnet node-name and number at
this
point.
hi folks.
"me too": I've got an alphaserver with OpenVMS 8.4 ready to roll. I've
got Rob Jarratt's router running on a spare linux box (raspberry pi,
since you asked) because I don't have a static IP. The router code's
not configured yet.
I'm a DECnet newbie, so would appreciate some abbreviated hecnet
directions if any exist (and if not, a pointer to just go away and
read the DECnet manuals is equally welcome).
I'm in the UK. Is hecnet organised by geographic region?
Like already answered, HECnet is not organized that way.
As for connecting, if you have Jarratt's code up and running, you might
want
to try and hook up with him?
Other questions to figure out is if you are going in a new area, or
connecting
into an existing one.
This matters both since if you are using an existing area, you need to use
the
same area as the next person you connect to.
If you go for your own area, you instead need an area router on your side,
and a connection to another area router.
And then we have the question about node names, which is more loosely
regulated. It's pretty much a question of picking names not already in
use.
Having a dynamic IP address is a cause for some problems. Let's see if
Jarratt's router will handle it well.
Johnny
The point about the router I wrote is that if you have a dynamic IP address
it needs the *peer* to use it. That is because it periodically queries DNS
(in a non-blocking manner) for your IP address. Clearly there will be a
period after an IP address change when the router will send packets to the
wrong address, but the poll period can be set to whatever period you wish.
The router will interoperate with the bridge, I run it here and I don't
think anyone on HECnet notices a difference other than that it does not
implement other protocols, so you can't SET HOST to it for example. So there
is no specific need to peer with me, but I am happy to do so, if you want to
peer with me give me your DNS name and port number, mine is
jarratt.dyndns.org:4713 (one limitation I ought to fix is the need for a
separate port for each peer). Note that since I connect to the rest of
HECnet via Johnny, and he is not using the router, I could lose connectivity
to HECnet if my IP address changes, because I too have a dynamic IP address,
but luckily my ISP does not make it change often.
The router works as an area router so you might need to have your own area.
It can also work as a non-area router, and this configuration has not been
tested quite as much.
Regards
Rob
