HECnet

hecnet@lists.dfupdate.se

7 participants
15562 discussions

subnet info, was Re: [HECnet] _PROVISIONAL_ map of HECnet, courtesy largely of Brian H.

by sampsa＠mac.com

Fair enough, I'll run my Beirut network in area 8.. sampsa On 8 Jan 2013, at 16:24, Johnny Billquist <bqt at softjar.se> wrote: I'm probably going to come back and make more comments on this later... However, a couple of points and responses right now... Eve today, areas do not correspond to adminstrative control that much. There are areas which have several different people responsible for different machines, and atleast I have "sub-delegated" parts of area 1 from time to time. Yes, we will be running out of areas eventually. Based on the current growth, I'd guess a couple of years at most, and then we're out. Areas should be used for administrative reasons, and relate less to any geographical constraints. DECnet areas work perfectly fine spanning large distances. "Sub-letting" areas should definitely be a valid approach. Each user in one area can still have their own area router, and their own connections to the rest of HECnet, as long as they also have interconnects within the area. Data mining is difficult, since there are different systems, with different possibilities of extracting it, and in different formats. A centralized repository of data is nice in many ways, but it is a headache to manage. That said, I could be convinced of setting something semi-automatic up. A reasonable way would be for people to give me machines to poll, and then I'd setup an automated process to poll those machines for files in a specific format. I can then create a database out of that, and make it available through the web, as well as over DECnet, and also as a summarized file. Anything would be pretty easy if we just have the data collected. I already have something of a start for this in the form of my database of nodes in HECnet. I'd need to extend it with more fields, but that would be pretty easy. It's all in Datatrieve today, and that should be accessible over DECnet right now (even though I seem to remember that VMS hosts had some problems with that). I'm already extracting information from that database for the hecnet web-page on MIM (accessible as Madame). So, if we can just decide on what we want, and how to make the information available, I'll sit down and write the code to fix it. Johnny On 2013-01-08 06:45, Cory Smelosky wrote: On 8 Jan 2013, at 00:25, Dave McGuire <mcguire at neurotica.com> wrote: On 01/07/2013 09:57 PM, Ian McLaughlin wrote: Yeah more and more of us are using Ciscos to do this. We really need to find a way around this issue that doesn't involve manual maintenance of routing info. Perhaps an agreed-upon entry in INFO.TXT ? That's still manually managed, but it's managed by the individual link owners. Well Brian raised the good point of "on which host?" ...I think the problem here is that INFO.TXT really looks like, to me as a relative HECnet n00b, a per-"domain" file...but there's no clear delineation of administrative domains here. We've been using areas, but we're running out of those, and there's no consistency in the node numbering within each area. We could all agree to have "an info node" with a particular node number within each area, but that won't work when we start having multiple administrative domains within a single area. Johnny talked about exactly this just today, in the context of Sampsa's relocation. Dividing lines between regions of administrative control will not correspond to area numbers for much longer, its sounds like. Yeah, I've been noticing that...I've up-to-now used a specific "info node" approach...but it DOES get a bit wonky when I divide my stuff, or skip a node number or re-use a node number. (On a semi-related note...I might implement personal node-number schemes: separating PDP-11 sims from DEC-20 sims from VMS sims from physical hardware and so on.) Perhaps a centralized database that maintains per-NODE info, not per-AREA info. Then that database could have a field that denotes the point of administrative control that is responsible for each node. Centralising the NODE info could solve a lot of problems and make data mining easier. ;) I'd also like basic (Geographic location(s) (see below for further comments), owner, that kind of stuff) per-area info to be defined in this central database. (To be honest, I'd then break it down in to sub, and sub sub areas but at times I can go a bit overboard with creating subcategories...I doubt anyone other than myself would like breaking down their areas /that/ much.) Then, some mechanism (either automated, manual, whatever) would then populate that database. Perhaps there could be several population mechanisms...a program that runs under VMS, RSX, RSTS/E, or whatever, and something over IP for everything else. A web interface to the database would also be nice. How would it be done? Flatfile and having Johnny or someone add all node info by hand? ;) -Dave -- Dave McGuire, AK4HZ New Kensington, PA

12 years, 5 months

HECnet performance....

by ian＠platinum.net

Do we have a 'standard' metric for Cisco routers on Hecnet? I've been using 10 for each link so far. How do these devices behave with asymmetrical costs? Ian On 2013-01-08, at 12:01 PM, Peter Lothberg <roll at Stupi.SE> wrote: A few days ago a "TELL 1.13 SHOW KNOWN NODES" from 42.42 BET:: was very = slow. It's probably 4 times faster now. I don't know if I'm passing = through your part of the net to get to Johnny. Seems like you are; NCP>tell mim show node bet 20:55:46 NCP Request # 114 Accepted NCP> 20:55:47 NCP Request # 114; Show Node Summary Completed Node State Active Delay Circuit Next node links 42.42 (BET) 0 4 59.11 (DIMMA) I think we can even make this better... Set up a (cisco) tunnel to 130.238.19.60 (and tell me your side IP address). Set the metric you have on the old tunnel(s) to me to cost 20. Set the cost for the new tunnel to 10. --P --- Filter service subscribers can train this email as spam or not-spam here: http://my.email-as.net/spamham/cgi-bin/learn.pl?messageid=3A1F5A6859CE11E2B…

12 years, 5 months

HECnet performance....

by mcguire＠neurotica.com

On 01/08/2013 09:05 PM, Peter Lothberg wrote: Dave, do you se and improvement/degradation of the cisco-tunnel-to-johhny-bridged-ethernet part of Hecnet? Hi Peter! I thought things seemed a bit snappier when I did a few things yesterday, but I didn't take any measurements, and figured it was just a low-traffic period. Why do you ask? Se my previous post, do the same thing, IP address on your side? My end is set up! The address is 50.73.179.1. I had a small cisco router sent to Uppsala and they installed it on the ethernet there, so now we have a Cisco box acting as area router attached to the magic ethernet at Update. Very nice! Thank you! -Dave -- Dave McGuire, AK4HZ New Kensington, PA

12 years, 5 months

Re: VMS sources

by Paul_Koning＠Dell.com

On Jan 8, 2013, at 3:04 PM, Brian Schenkenberger, VAXman- wrote: Dave McGuire <mcguire at neurotica.com> writes: On 01/08/2013 02:55 PM, Cory Smelosky wrote: >>> I've always wondered about VMS sources: how they are actually distributed >>> today and how much space they take? Is a CD-ROM enough for everything? And in >>> which format are they? Just simple text files in a bunch of directories or >>> there is something fancier such as some cross references and indexes? >> >> They used to make source *listings* available on fiche; I have several >> sets of those. It's a stack of fiche maybe 3-4" thick. > > How old are these "listings"? I haven't looked at them in years, but I think I have at least 5.1 and 5.2, possibly 4.7. But who needs the source listings when you've got access to the poor-man's microfiche? Can't search microfiche, and a fiche reader is a clumsy and hard to use contraption. paul

12 years, 5 months

VMS sources (was: Re: [HECnet] NCP-F-NETIO)

by clemc＠ccc.com

You have to understand, the concept of "Open Source" is not new. Most vendors supplied the source listing, and sometime even the code. There was a fee to copy it all (it was said in the old day it was impossible to write a mag tape anywhere for less than $100). So the fees we really set high enough to keep the idiots away, but low enough that the customers that needed them could get them. Remember a lot of it was in assembler, so it did you little good unless you had the vendors HW. A few things changed that all. First, the practice became less prevalent by the later 1970s primarily because of the Amadhl Corp making and selling a 360/370 clone. Interestingly enough, DEC did not sue CalData because of the SW. It was because they cloned the Unibus AND used the PDP-11 instruction set. Second once writing more and more of the OS in a High Level Language became de rigor, the ability to "steal" SW IP seemed to be more of an issue (although DEC was in good shape because no one but DEC would use BLISS). So around the late 1970s, DEC and most other vendors began to be more protective. On Tue, Jan 8, 2013 at 2:56 PM, Dave McGuire <mcguire at neurotica.com> wrote: On 01/08/2013 02:51 PM, Brian Schenkenberger, VAXman- wrote: > You need to first sign and pay for a source listings license agreement. > Back many years ago, IIRC, it was about $2K. There's then maintenance > that must be paid yearly to get the listings CDs/DVDs when produced. I am nothing short of astonished that it was that cheap! -Dave -- Dave McGuire, AK4HZ New Kensington, PA

12 years, 5 months

HECnet performance....

by roll＠Stupi.SE

On 01/08/2013 08:48 PM, Peter Lothberg wrote: Dave, do you se and improvement/degradation of the cisco-tunnel-to-johhny-bridged-ethernet part of Hecnet? Hi Peter! I thought things seemed a bit snappier when I did a few things yesterday, but I didn't take any measurements, and figured it was just a low-traffic period. Why do you ask? Se my previous post, do the same thing, IP address on your side? I had a small cisco router sent to Uppsala and they installed it on the ethernet there, so now we have a Cisco box acting as area router attached to the magic ethernet at Update. (And they are not far from me network topology vise, 10G links...) 1 DEC-GW.Stupi.SE (192.108.200.210) 4 msec 0 msec 4 msec 2 BFR5-SRP-13-0.Stupi.NET (194.71.10.30) 4 msec 4 msec 4 msec 3 t1fre-ge-3-2-0.sunet.se (130.242.94.221) 4 msec 4 msec 4 msec 4 m1fre-ae1-v1.sunet.se (130.242.83.45) 4 msec 4 msec 4 msec 5 uu-br1-xe-1-2-0.sunet.se (130.242.85.134) 4 msec 4 msec 4 msec 6 uu-g.sunet.se (193.11.0.234) 4 msec 4 msec 4 msec 7 130.238.6.231 8 msec 8 msec 12 msec 8 Platburk.Update.UU.SE (130.238.19.60) 8 msec * 8 msec --P

12 years, 5 months

HECnet performance....

by ian＠platinum.net

Peter, Thank you. The IP on my side is 174.4.172.207. I will get everything set up on my end in a few hours when I get a chance. Ian On 2013-01-08, at 12:01 PM, Peter Lothberg <roll at Stupi.SE> wrote: A few days ago a "TELL 1.13 SHOW KNOWN NODES" from 42.42 BET:: was very = slow. It's probably 4 times faster now. I don't know if I'm passing = through your part of the net to get to Johnny. Seems like you are; NCP>tell mim show node bet 20:55:46 NCP Request # 114 Accepted NCP> 20:55:47 NCP Request # 114; Show Node Summary Completed Node State Active Delay Circuit Next node links 42.42 (BET) 0 4 59.11 (DIMMA) I think we can even make this better... Set up a (cisco) tunnel to 130.238.19.60 (and tell me your side IP address). Set the metric you have on the old tunnel(s) to me to cost 20. Set the cost for the new tunnel to 10. --P --- Filter service subscribers can train this email as spam or not-spam here: http://my.email-as.net/spamham/cgi-bin/learn.pl?messageid=3A1F5A6859CE11E2B…

12 years, 5 months

Re: VMS sources

by system＠TMESIS.COM

Dave McGuire <mcguire at neurotica.com> writes: On 01/08/2013 02:55 PM, Cory Smelosky wrote: >>> I've always wondered about VMS sources: how they are actually distributed >>> today and how much space they take? Is a CD-ROM enough for everything? And in >>> which format are they? Just simple text files in a bunch of directories or >>> there is something fancier such as some cross references and indexes? >> >> They used to make source *listings* available on fiche; I have several >> sets of those. It's a stack of fiche maybe 3-4" thick. > > How old are these "listings"? I haven't looked at them in years, but I think I have at least 5.1 and 5.2, possibly 4.7. But who needs the source listings when you've got access to the poor-man's microfiche? -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG Well I speak to machines with the voice of humanity.

12 years, 5 months

HECnet performance....

by roll＠Stupi.SE

A few days ago a "TELL 1.13 SHOW KNOWN NODES" from 42.42 BET:: was very = slow. It's probably 4 times faster now. I don't know if I'm passing = through your part of the net to get to Johnny. Seems like you are; NCP>tell mim show node bet 20:55:46 NCP Request # 114 Accepted NCP> 20:55:47 NCP Request # 114; Show Node Summary Completed Node State Active Delay Circuit Next node links 42.42 (BET) 0 4 59.11 (DIMMA) I think we can even make this better... Set up a (cisco) tunnel to 130.238.19.60 (and tell me your side IP address). Set the metric you have on the old tunnel(s) to me to cost 20. Set the cost for the new tunnel to 10. --P

12 years, 5 months

Re: VMS sources

by mcguire＠neurotica.com

On 01/08/2013 02:55 PM, Cory Smelosky wrote: I've always wondered about VMS sources: how they are actually distributed today and how much space they take? Is a CD-ROM enough for everything? And in which format are they? Just simple text files in a bunch of directories or there is something fancier such as some cross references and indexes? They used to make source *listings* available on fiche; I have several sets of those. It's a stack of fiche maybe 3-4" thick. How old are these "listings"? I haven't looked at them in years, but I think I have at least 5.1 and 5.2, possibly 4.7. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

12 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet