HECnet

hecnet@lists.dfupdate.se

15586 discussions

MOP vs. Cisco, was Re: [HECnet] _PROVISIONAL_ map of HECnet, courtesy largely of Brian H.

by b4＠gewt.net

On 9 Jan 2013, at 12:56, Dave McGuire <mcguire at neurotica.com> wrote: On 01/09/2013 12:51 PM, Brian Hechinger wrote: ...and like this from NCP under VMS: NCP> connect node gw physical address <MAC address> via <circuit-name> Note that the MAC address must have its octets delimited by colons under Linux, and hyphens under VMS. NCP>connect node gw physical address AA-00-04-00-01-F4 via ISA-0 Console connected (press CTRL/D when finished) User Access Verification Username: NCP> Uhhh...HOLY CRAP! That works from outside my network?! Is it working because you specified the circuit which gave it a path, or because it gleaned the DECnet area/node address from the (changed-by-DECnet) MAC address? I'm guessing the latter. (Peter?) That was done from EBOLA, sorry to confuse you. Oh. Crap. So, can I get a non-priv account? something standard that we can get others to add would be nice. Yes, maybe username "hecnet"? "Role" accounts are a horrifically bad idea in general, but I think one is called for in this case. Shall we setup shared RADIUS? :-P Uh, no. ;) -Dave -- Dave McGuire, AK4HZ New Kensington, PA I want in on your crazy GRE and DECnet routing setups! ;) I could install vyatta which is linux-based meaning I could /maybe/ build linux-decnet and have it function as an area router. Management could also be done via SNMP, but not to the ease of Cisco. Thoughts? I'd use my current router as-is, but FreeBSD lacks DECnet bits. :(

12 years, 11 months

MOP vs. Cisco, was Re: [HECnet] _PROVISIONAL_ map of HECnet, courtesy largely of Brian H.

by mcguire＠neurotica.com

On 01/09/2013 12:54 PM, Paul_Koning at Dell.com wrote: ...and like this from NCP under VMS: NCP> connect node gw physical address <MAC address> via <circuit-name> Note that the MAC address must have its octets delimited by colons under Linux, and hyphens under VMS. NCP>connect node gw physical address AA-00-04-00-01-F4 via ISA-0 Console connected (press CTRL/D when finished) User Access Verification Username: NCP> Uhhh...HOLY CRAP! That works from outside my network?! Is it working because you specified the circuit which gave it a path, or because it gleaned the DECnet area/node address from the (changed-by-DECnet) MAC address? I'm guessing the latter. (Peter?) It works on any LAN, including across bridges, so the various Internet based bridges we have make this work over some distance. The communication is via MOP remote console packets, which are not routed (just like LAT). The addressing is direct to the MAC address, whatever that happens to be at the destination. If the node you want to talk to supports MAC address aliases, the original address might work, but in any case the DECnet style Ethernet address will work. That was my belief before five minutes ago, when Brian was messing with me and got me all excited. I was certain that MOP was an unroutable, LAN-only protocol like LAT. But then, apparently folks have been booting DECservers via HECnet..? -Dave -- Dave McGuire, AK4HZ New Kensington, PA

12 years, 11 months

MOP vs. Cisco, was Re: [HECnet] _PROVISIONAL_ map of HECnet, courtesy largely of Brian H.

by mcguire＠neurotica.com

On 01/09/2013 12:51 PM, Brian Hechinger wrote: ...and like this from NCP under VMS: NCP> connect node gw physical address <MAC address> via <circuit-name> Note that the MAC address must have its octets delimited by colons under Linux, and hyphens under VMS. NCP>connect node gw physical address AA-00-04-00-01-F4 via ISA-0 Console connected (press CTRL/D when finished) User Access Verification Username: NCP> Uhhh...HOLY CRAP! That works from outside my network?! Is it working because you specified the circuit which gave it a path, or because it gleaned the DECnet area/node address from the (changed-by-DECnet) MAC address? I'm guessing the latter. (Peter?) That was done from EBOLA, sorry to confuse you. Oh. Crap. So, can I get a non-priv account? something standard that we can get others to add would be nice. Yes, maybe username "hecnet"? "Role" accounts are a horrifically bad idea in general, but I think one is called for in this case. Shall we setup shared RADIUS? :-P Uh, no. ;) -Dave -- Dave McGuire, AK4HZ New Kensington, PA

12 years, 11 months

MOP vs. Cisco, was Re: [HECnet] _PROVISIONAL_ map of HECnet, courtesy largely of Brian H.

by Paul_Koning＠Dell.com

On Jan 9, 2013, at 12:50 PM, Dave McGuire wrote: On 01/09/2013 10:49 AM, Brian Hechinger wrote: ...and like this from NCP under VMS: NCP> connect node gw physical address <MAC address> via <circuit-name> Note that the MAC address must have its octets delimited by colons under Linux, and hyphens under VMS. NCP>connect node gw physical address AA-00-04-00-01-F4 via ISA-0 Console connected (press CTRL/D when finished) User Access Verification Username: NCP> Uhhh...HOLY CRAP! That works from outside my network?! Is it working because you specified the circuit which gave it a path, or because it gleaned the DECnet area/node address from the (changed-by-DECnet) MAC address? I'm guessing the latter. (Peter?) It works on any LAN, including across bridges, so the various Internet based bridges we have make this work over some distance. The communication is via MOP remote console packets, which are not routed (just like LAT). The addressing is direct to the MAC address, whatever that happens to be at the destination. If the node you want to talk to supports MAC address aliases, the original address might work, but in any case the DECnet style Ethernet address will work. paul

12 years, 11 months

MOP vs. Cisco, was Re: [HECnet] _PROVISIONAL_ map of HECnet, courtesy largely of Brian H.

by wonko＠4amlunch.net

On 1/9/2013 12:50 PM, Dave McGuire wrote: On 01/09/2013 10:49 AM, Brian Hechinger wrote: ...and like this from NCP under VMS: NCP> connect node gw physical address <MAC address> via <circuit-name> Note that the MAC address must have its octets delimited by colons under Linux, and hyphens under VMS. NCP>connect node gw physical address AA-00-04-00-01-F4 via ISA-0 Console connected (press CTRL/D when finished) User Access Verification Username: NCP> Uhhh...HOLY CRAP! That works from outside my network?! Is it working because you specified the circuit which gave it a path, or because it gleaned the DECnet area/node address from the (changed-by-DECnet) MAC address? I'm guessing the latter. (Peter?) That was done from EBOLA, sorry to confuse you. So, can I get a non-priv account? something standard that we can get others to add would be nice. Yes, maybe username "hecnet"? "Role" accounts are a horrifically bad idea in general, but I think one is called for in this case. Shall we setup shared RADIUS? :-P -brian

12 years, 11 months

MOP vs. Cisco, was Re: [HECnet] _PROVISIONAL_ map of HECnet, courtesy largely of Brian H.

by mcguire＠neurotica.com

On 01/09/2013 10:49 AM, Brian Hechinger wrote: ...and like this from NCP under VMS: NCP> connect node gw physical address <MAC address> via <circuit-name> Note that the MAC address must have its octets delimited by colons under Linux, and hyphens under VMS. NCP>connect node gw physical address AA-00-04-00-01-F4 via ISA-0 Console connected (press CTRL/D when finished) User Access Verification Username: NCP> Uhhh...HOLY CRAP! That works from outside my network?! Is it working because you specified the circuit which gave it a path, or because it gleaned the DECnet area/node address from the (changed-by-DECnet) MAC address? I'm guessing the latter. (Peter?) So, can I get a non-priv account? something standard that we can get others to add would be nice. Yes, maybe username "hecnet"? "Role" accounts are a horrifically bad idea in general, but I think one is called for in this case. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

12 years, 11 months

maintaining data in DNS, was Re: [HECnet] HECnet performance....

by wonko＠4amlunch.net

On 1/9/2013 12:43 PM, Dave McGuire wrote: On 01/09/2013 10:50 AM, Brian Hechinger wrote: Set up a (cisco) tunnel to 130.238.19.60 (and tell me your side IP address). I think it's time to come up with something a little better to track all these. Thoughts? A subdomain under some related domain (perhaps <sub>.hecnet.update.uu.se?) with the tunnel endpoints as A records? The problem here is that it isn't searchable. You need to know the A record name. It would be more useful for me to have it in a db. You could do an AXFR query for the subdomain. ;) You need to setup zone transfer rights for that though, right? Did I ever tell you about how I implemented a linked list in TXT records back in '93? At one time, Digex' nameservers had the menus for all the local carry-out restaurants stored, item by item, in the nameserver. I wrote a little C program to traverse the linked lists and print out the menus. That's disturbing. And awesome. :) -brian

12 years, 11 months

maintaining data in DNS, was Re: [HECnet] HECnet performance....

by b4＠gewt.net

On 9 Jan 2013, at 12:43, Dave McGuire <mcguire at neurotica.com> wrote: On 01/09/2013 10:50 AM, Brian Hechinger wrote: Set up a (cisco) tunnel to 130.238.19.60 (and tell me your side IP address). I think it's time to come up with something a little better to track all these. Thoughts? A subdomain under some related domain (perhaps <sub>.hecnet.update.uu.se?) with the tunnel endpoints as A records? The problem here is that it isn't searchable. You need to know the A record name. It would be more useful for me to have it in a db. You could do an AXFR query for the subdomain. ;) Did I ever tell you about how I implemented a linked list in TXT records back in '93? At one time, Digex' nameservers had the menus for all the local carry-out restaurants stored, item by item, in the nameserver. I wrote a little C program to traverse the linked lists and print out the menus. That sounds like an approach /I/ would try. ;) -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/09/2013 10:08 AM, Cory Smelosky wrote: 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 minin= g easier. ;) ...a wiki..... ...to be perfectly honest, a HECnet wiki isn't too bad of an idea. I like the idea. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

12 years, 11 months

maintaining data in DNS, was Re: [HECnet] HECnet performance....

by mcguire＠neurotica.com

On 01/09/2013 10:50 AM, Brian Hechinger wrote: Set up a (cisco) tunnel to 130.238.19.60 (and tell me your side IP address). I think it's time to come up with something a little better to track all these. Thoughts? A subdomain under some related domain (perhaps <sub>.hecnet.update.uu.se?) with the tunnel endpoints as A records? The problem here is that it isn't searchable. You need to know the A record name. It would be more useful for me to have it in a db. You could do an AXFR query for the subdomain. ;) Did I ever tell you about how I implemented a linked list in TXT records back in '93? At one time, Digex' nameservers had the menus for all the local carry-out restaurants stored, item by item, in the nameserver. I wrote a little C program to traverse the linked lists and print out the menus. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

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