HECnet

hecnet@lists.dfupdate.se

15586 discussions

_PROVISIONAL_ map of HECnet, courtesy largely of Brian H.

by ian＠platinum.net

The problem with ssh is it's "out of band" as far as hecnet is concerned. It would be nice if the discovery was purely decnet. Ian Sent from my iPhone On 2013-01-07, at 9:25 PM, Dave McGuire <mcguire at neurotica.com> wrote: On 01/07/2013 09:57 PM, Ian McLaughlin wrote: The "SHOW DECNET NEIGHBOR" and "SHOW DECNET ROUTE" commands are both non-priviledged. Perhaps we could allow a 'trusted' network mapping daemon the ability to get a remote console on the Cisco and execute and parse these commands? I think all of us with Ciscos are running new enough firmware to support SSH. We could set up public keys for the automated data retrieval. That would be easy and relatively secure. -Dave -- Dave McGuire, AK4HZ New Kensington, PA --- Filter service subscribers can train this email as spam or not-spam here: http://my.email-as.net/spamham/cgi-bin/learn.pl?messageid=E03B65D4595311E28…

12 years, 11 months

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

by b4＠gewt.net

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, 11 months

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

by mcguire＠neurotica.com

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. 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. 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. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

12 years, 11 months

_PROVISIONAL_ map of HECnet, courtesy largely of Brian H.

by mcguire＠neurotica.com

On 01/07/2013 09:57 PM, Ian McLaughlin wrote: The "SHOW DECNET NEIGHBOR" and "SHOW DECNET ROUTE" commands are both non-priviledged. Perhaps we could allow a 'trusted' network mapping daemon the ability to get a remote console on the Cisco and execute and parse these commands? I think all of us with Ciscos are running new enough firmware to support SSH. We could set up public keys for the automated data retrieval. That would be easy and relatively secure. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

12 years, 11 months

_PROVISIONAL_ map of HECnet, courtesy largely of Brian H.

by mcguire＠neurotica.com

On 01/07/2013 11:58 PM, Gregg Levine wrote: Okay good. Actually Ian I expected that. That was aimed at Dave, who's sitting in the middle of a snowman storm of problems. Me? No, not so much, everything's pretty much good here. A few niggling issues but I'll work them out. Huh. Then how come you're surrounded by the snowmen that an old friend had already destroyed, and with clumsy help no less...... Well, that's jut what they do. You of all people should know that. It's in their BLOOD, man! -Dave -- Dave McGuire, AK4HZ New Kensington, PA

12 years, 11 months

_PROVISIONAL_ map of HECnet, courtesy largely of Brian H.

by gregg.drwho8＠gmail.com

On Mon, Jan 7, 2013 at 11:32 PM, Dave McGuire <mcguire at neurotica.com> wrote: On 01/07/2013 10:03 PM, Gregg Levine wrote: Okay good. Actually Ian I expected that. That was aimed at Dave, who's sitting in the middle of a snowman storm of problems. Me? No, not so much, everything's pretty much good here. A few niggling issues but I'll work them out. -Dave -- Dave McGuire, AK4HZ New Kensington, PA Hello! Huh. Then how come you're surrounded by the snowmen that an old friend had already destroyed, and with clumsy help no less...... ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again."

12 years, 11 months

_PROVISIONAL_ map of HECnet, courtesy largely of Brian H.

by mcguire＠neurotica.com

On 01/07/2013 10:03 PM, Gregg Levine wrote: Okay good. Actually Ian I expected that. That was aimed at Dave, who's sitting in the middle of a snowman storm of problems. Me? No, not so much, everything's pretty much good here. A few niggling issues but I'll work them out. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

12 years, 11 months

_PROVISIONAL_ map of HECnet, courtesy largely of Brian H.

by mcguire＠neurotica.com

On 01/07/2013 09:58 PM, Gregg Levine wrote: Define how close to current is your router's operating system? 12.3(22) Oh and there's a box in your place with my name on it, it, ah, wants to come home. I'm gettin' there. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

12 years, 11 months

_PROVISIONAL_ map of HECnet, courtesy largely of Brian H.

by b4＠gewt.net

On 7 Jan 2013, at 22:29, Ian McLaughlin <ian at platinum.net> wrote: On 2013-01-07, at 7:16 PM, Brian Hechinger <wonko at 4amlunch.net> wrote: On 1/7/2013 10:09 PM, Cory Smelosky wrote: Now that it's ambiguous, all of you.;) I like hearing how people have configured their networks and wired them in with all their stuff. My network is very scary, but here's the path from the outside world to my DEC machines: Mine is a bit less scary, but it's still crazy. ;) Cable modem -> Astaro firewall -> Apple Airport -> Apple Airport Express -> Cisco 7206VXR -> 10Mbps ethernet switch with 10base2 connector -> DECrepeater90C -> many VAXen ;) DSL (yes, DSL) modem -> HT P4 running pfSense (considering moving this to a VM where all my other stuff runs, would give me more runtime on the UPS but would create a single point of failure) -> gigE switch for core stuff and personal systems -> 50ft ethernet cable running across a few rooms to a 100mbit switch where my DEC systems will live. My HECnet routing involves a layer 2 OpenVPN and a simh instance on my VPS... The two Airport devices give me a wireless bridge in to my garage, where the VAXen live. Ian

12 years, 11 months

_PROVISIONAL_ map of HECnet, courtesy largely of Brian H.

by ian＠platinum.net

On 2013-01-07, at 7:16 PM, Brian Hechinger <wonko at 4amlunch.net> wrote: On 1/7/2013 10:09 PM, Cory Smelosky wrote: Now that it's ambiguous, all of you.;) I like hearing how people have configured their networks and wired them in with all their stuff. My network is very scary, but here's the path from the outside world to my DEC machines: Cable modem -> Astaro firewall -> Apple Airport -> Apple Airport Express -> Cisco 7206VXR -> 10Mbps ethernet switch with 10base2 connector -> DECrepeater90C -> many VAXen ;) The two Airport devices give me a wireless bridge in to my garage, where the VAXen live. Ian

12 years, 11 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet