On 2011-11-26 12.05, H Vlems wrote:
I agree with Johnny. The technical problems that are DECnet related, like
duplicate areas and duplicate nodenames are easily solved.
Possibly a lot of work, e.g. I had to move all my machines to another area
and it takes less than 5 minutes per system. Mandatory reboot included.
Incidentally, I documented the required procedures for several operating
systems (VMS, linux and Windows) and when appropriate for both phase IV and
phase V.
So a couple of simple agreements is all that is necessary to merge the two
networks. "Ownership" of area 1 may possibly have ego involved though I
doubt that Johnny would care much.
Right. The biggest concern would perhaps be that MIM is used as (I think) the most central repository of HECnet related information, and as such, it might be a bit unfortunate to move around. But apart from that, any area is as good as any other area. Moving means some work, but it is not complicated.
What I've read about the "enhancements" to the bridge program is yet another
matter. First off, it ain't called bridge for nothing: like any layer 2
bridge the program moves packets between ports and is transparent to both
the content of the datagrams and the functionality of the protocol.
Including DNS like functionality violates that rule.
I also wanted to keep the complexity and overhead down. Otherwise, yes, you could change from UDP to TCP, include SSL, and certificates, to make sure we keep it safe. But that would incur quite some costs both from an administrative point of view, as well as lots more CPU resources to run the bridge, and also more problems in porting it to other systems.
In my opinion, if anyone wants a central name repository for DECnet please
upgrade to DECnet phase V.
Well that, or else continue with the "voluntary" system we have in place now. Which is that I keep a database on MIM, to which all can send in registrations, and anyone can cope the nodename database from MIM to their own machine to get the same view as MIM have.
The actual database I have on MIM is stored in Datatrieve, with some additional information, and then the DECnet nodename database is created from that Datatrieve source.
Which is my way of saying that I'm not too fond of this "enhancement"...
:-)
Johnny
Hans
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Johnny Billquist
Verzonden: zaterdag, november 2011 11:36
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Integrating with the Italian network.
On 2011-11-26 08.43, Angela Kahealani wrote:
On Sat, Nov 26, 2011 at 02:35:17AM -0500, Steve Davidson wrote:
Well here's three reasons:
1) they use DECnet area 1 thus area collision
Yes. That was an unfortunate decision of them.
2) they use some of the names we already use thus name space collision
That is not really a big issue. DECnet do not have a requirement for a
coherent nodename database. Every machine can have its own. I keep a
nodename database on MIM, which people are welcome to register in, for
us to be able to copy and keep a synched version, but anyone on HECnet
can really have their own different database if they want to.
3) and from what I remember, they are entirely dynamic DNS based and
thus had to make major changes to the bridge to even exist.
The changes they made work just fine, BTW...
Yes. That was one reason that I remember, now that you mention it.
-Steve
So, then do they not have a superior solution which could be adopted by
the existing HECNET?
Depends on your definition of "superior". They manage dynamic addresses,
at the cost of either exposing to name resolution hiccups, slowness,
name poisoning, and whatnot, or else a potential for security exposure
if they send, and accept traffic from random nodes in some time window.
The latter reasons are why I do not have such a thing in the bridge in
general. DECnet is not a very secure protocol. Passwords fly through it
in clear text. I am not fond of the possibility of that traffic going to
some random address in general, and even less fond of opening up the
virtual ethernet to any random place to inject traffic.
I'm happy to discuss and explain the problems if people want to, but I
seriously doubt I'll change my mind. I have given it much thought over
the years.
Johnny
I agree with Johnny. The technical problems that are DECnet related, like
duplicate areas and duplicate nodenames are easily solved.
Possibly a lot of work, e.g. I had to move all my machines to another area
and it takes less than 5 minutes per system. Mandatory reboot included.
Incidentally, I documented the required procedures for several operating
systems (VMS, linux and Windows) and when appropriate for both phase IV and
phase V.
So a couple of simple agreements is all that is necessary to merge the two
networks. "Ownership" of area 1 may possibly have ego involved though I
doubt that Johnny would care much.
What I've read about the "enhancements" to the bridge program is yet another
matter. First off, it ain't called bridge for nothing: like any layer 2
bridge the program moves packets between ports and is transparent to both
the content of the datagrams and the functionality of the protocol.
Including DNS like functionality violates that rule.
In my opinion, if anyone wants a central name repository for DECnet please
upgrade to DECnet phase V.
Which is my way of saying that I'm not too fond of this "enhancement"...
Hans
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Johnny Billquist
Verzonden: zaterdag, november 2011 11:36
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Integrating with the Italian network.
On 2011-11-26 08.43, Angela Kahealani wrote:
On Sat, Nov 26, 2011 at 02:35:17AM -0500, Steve Davidson wrote:
Well here's three reasons:
1) they use DECnet area 1 thus area collision
Yes. That was an unfortunate decision of them.
2) they use some of the names we already use thus name space collision
That is not really a big issue. DECnet do not have a requirement for a
coherent nodename database. Every machine can have its own. I keep a
nodename database on MIM, which people are welcome to register in, for
us to be able to copy and keep a synched version, but anyone on HECnet
can really have their own different database if they want to.
3) and from what I remember, they are entirely dynamic DNS based and
thus had to make major changes to the bridge to even exist.
The changes they made work just fine, BTW...
Yes. That was one reason that I remember, now that you mention it.
-Steve
So, then do they not have a superior solution which could be adopted by
the existing HECNET?
Depends on your definition of "superior". They manage dynamic addresses,
at the cost of either exposing to name resolution hiccups, slowness,
name poisoning, and whatnot, or else a potential for security exposure
if they send, and accept traffic from random nodes in some time window.
The latter reasons are why I do not have such a thing in the bridge in
general. DECnet is not a very secure protocol. Passwords fly through it
in clear text. I am not fond of the possibility of that traffic going to
some random address in general, and even less fond of opening up the
virtual ethernet to any random place to inject traffic.
I'm happy to discuss and explain the problems if people want to, but I
seriously doubt I'll change my mind. I have given it much thought over
the years.
Johnny
On 2011-11-26 08.43, Angela Kahealani wrote:
On Sat, Nov 26, 2011 at 02:35:17AM -0500, Steve Davidson wrote:
Well here's three reasons:
1) they use DECnet area 1 thus area collision
Yes. That was an unfortunate decision of them.
2) they use some of the names we already use thus name space collision
That is not really a big issue. DECnet do not have a requirement for a coherent nodename database. Every machine can have its own. I keep a nodename database on MIM, which people are welcome to register in, for us to be able to copy and keep a synched version, but anyone on HECnet can really have their own different database if they want to.
3) and from what I remember, they are entirely dynamic DNS based and
thus had to make major changes to the bridge to even exist.
The changes they made work just fine, BTW...
Yes. That was one reason that I remember, now that you mention it.
-Steve
So, then do they not have a superior solution which could be adopted by
the existing HECNET?
Depends on your definition of "superior". They manage dynamic addresses, at the cost of either exposing to name resolution hiccups, slowness, name poisoning, and whatnot, or else a potential for security exposure if they send, and accept traffic from random nodes in some time window.
The latter reasons are why I do not have such a thing in the bridge in general. DECnet is not a very secure protocol. Passwords fly through it in clear text. I am not fond of the possibility of that traffic going to some random address in general, and even less fond of opening up the virtual ethernet to any random place to inject traffic.
I'm happy to discuss and explain the problems if people want to, but I seriously doubt I'll change my mind. I have given it much thought over the years.
Johnny
On Sat, Nov 26, 2011 at 02:35:17AM -0500, Steve Davidson wrote:
Well here's three reasons:
1) they use DECnet area 1 thus area collision
2) they use some of the names we already use thus name space collision
3) and from what I remember, they are entirely dynamic DNS based and
thus had to make major changes to the bridge to even exist.
The changes they made work just fine, BTW...
-Steve
So, then do they not have a superior solution which could be adopted by
the existing HECNET?
--
Aloha, SL: Celeste Python; InWorldz: Celestial Angela; RL: Angela Kahealani
(I'll) Be Seeing You... All information and transactions are private between
the parties, and are non negotiable. All rights reserve without prejudice by
Angela Kahealani http://www.kahealani.com/kahealani/angela_kahealani.html
Well here's three reasons:
1) they use DECnet area 1 thus area collision
2) they use some of the names we already use thus name space collision
3) and from what I remember, they are entirely dynamic DNS based and
thus had to make major changes to the bridge to even exist.
The changes they made work just fine, BTW...
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Johnny Billquist
Sent: Friday, November 25, 2011 9:25 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Integrating with the Italian network.
On 2011-11-26 03.02, Sampsa Laine wrote:
I've been thinking that it's a bit silly to have two separate hobby
DECNETs, so I figured we should get connected to the Italian net as
well.
Any ideas?
Sure. They are welcome to join anytime. They know it. I've been talking
with them since before they came online, since they asked me for help as
well as permission to use by bridge program (which I think they've also
modified slightly).
Unless I remember wrong, one or two of them are also subscribed here.
I no longer remember the reason they didn't connect from the start, but
I'm pretty sure they had a reason.
Johnny
On 2011-11-26 03.02, Sampsa Laine wrote:
I've been thinking that it's a bit silly to have two separate hobby DECNETs, so I figured we should get connected to the Italian net as well.
Any ideas?
Sure. They are welcome to join anytime. They know it. I've been talking with them since before they came online, since they asked me for help as well as permission to use by bridge program (which I think they've also modified slightly).
Unless I remember wrong, one or two of them are also subscribed here.
I no longer remember the reason they didn't connect from the start, but I'm pretty sure they had a reason.
Johnny
I've been thinking that it's a bit silly to have two separate hobby DECNETs, so I figured we should get connected to the Italian net as well.
Any ideas?
Sampsa
On Tue, 22 Nov 2011, Saku Set l wrote:
Do the 90 and 90A have same PSU?
Nope, they have different part numbers on the power supply and they do not fit (and are not interchangeable). Trust me, I tried. :)
Fred
I don't own a -90 so can't confirm that.
From: Saku Set l <setala at gmail.com>
Sender: owner-hecnet at Update.UU.SE
Date: Tue, 22 Nov 2011 13:11:48 +0200
To: <hecnet at update.uu.se>
ReplyTo: hecnet at Update.UU.SE
Subject: Re: [HECnet] VAXStation 4000/90A power supply fan
Do the 90 and 90A have same PSU?
On Sun, Nov 20, 2011 at 21:19, <hvlems at zonnet.nl> wrote:
No choice but to drill it out. Unless you'd rather buy another p/s.
Hans
-----Original Message-----
From: Fred <fcoffey at misernet.net>
Sender: owner-hecnet at Update.UU.SE
Date: Sun, 20 Nov 2011 14:08:23
To: <hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] VAXStation 4000/90A power supply fan
> On 18/11/11 13:29, hvlems at zonnet.nl wrote:
>> You could try and apply e little graphite powder in the noisy fan bearing,
>> better yet use a molybdenium based lubricant: these do not conduct
>> electricity.
I tried some good old moly lubricant the guys use at the copier shop where
I work - it made a slight difference but not much. The bearing is
obviously shot. The fan is *riveted* into the power supply. What the
heck?
On Fri, 18 Nov 2011, Mark Wickens wrote:
> I'd caution against running it with one fan - I think the point of having two
> is in case one fails, and like hard drives it does occasionally happen.
For now, I am running it with one fan, and it being only 60-65F in the
house (and the computer office) the VAX is not running hot. I removed one
of the drives, since I really wasn't doing anything with it. (it was a
pull from a BA356 canister) Looked half-height to me, although I do have
some smaller in size drives that I may swap in.
At some point I'm going to source new fans and then try to pry the old
ones out. Other than that when I had the power supply apart, no domed
caps, everything is quite clean (and even cleaner when I gave it a date
with the shop air compressor).
I have two 90's (not 90A's) in the closet I could press into service but I
really do not want to trash this 90A for just missing one fan.
Thanks for the responses all.
Fred
----
Lets call it for what it is - "legacy" is a term that people use in a
polite but derogatory manner to imply that the future direction they
prefer is not that which they view as the current direction.
Do the 90 and 90A have same PSU?
On Sun, Nov 20, 2011 at 21:19, <hvlems at zonnet.nl> wrote:
No choice but to drill it out. Unless you'd rather buy another p/s.
Hans
-----Original Message-----
From: Fred <fcoffey at misernet.net>
Sender: owner-hecnet at Update.UU.SE
Date: Sun, 20 Nov 2011 14:08:23
To: <hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] VAXStation 4000/90A power supply fan
> On 18/11/11 13:29, hvlems at zonnet.nl wrote:
>> You could try and apply e little graphite powder in the noisy fan bearing,
>> better yet use a molybdenium based lubricant: these do not conduct
>> electricity.
I tried some good old moly lubricant the guys use at the copier shop where
I work - it made a slight difference but not much. The bearing is
obviously shot. The fan is *riveted* into the power supply. What the
heck?
On Fri, 18 Nov 2011, Mark Wickens wrote:
> I'd caution against running it with one fan - I think the point of having two
> is in case one fails, and like hard drives it does occasionally happen.
For now, I am running it with one fan, and it being only 60-65F in the
house (and the computer office) the VAX is not running hot. I removed one
of the drives, since I really wasn't doing anything with it. (it was a
pull from a BA356 canister) Looked half-height to me, although I do have
some smaller in size drives that I may swap in.
At some point I'm going to source new fans and then try to pry the old
ones out. Other than that when I had the power supply apart, no domed
caps, everything is quite clean (and even cleaner when I gave it a date
with the shop air compressor).
I have two 90's (not 90A's) in the closet I could press into service but I
really do not want to trash this 90A for just missing one fan.
Thanks for the responses all.
Fred
----
Lets call it for what it is - "legacy" is a term that people use in a
polite but derogatory manner to imply that the future direction they
prefer is not that which they view as the current direction.
