HECnet

hecnet@lists.dfupdate.se

15556 discussions

by bqt＠softjar.se

Hi, Joe. Your names have been added in the database. :-) No, we do not have a geagraphical view of HECnet. I think one was done several years ago, but if that can be found, it is probably very outdated by now. It would be fun to have a current one, though. Anyone feel like creating it? It would perhaps make sense to use one as the basis for some connection setups. However, it is more difficult than imagined sometimes, because the geographical locations do not necessarily correspond with network connectivity. HECnet is usually more helped by low latency than high bandwidth, and figuring that out all over the place can be tricky. Johnny Joe Ferraro wrote: Johnny, At the present, I'm hitching a ride with Sampsa ... I've taken: 8.501 - WOPR 8.502 - SIOP Do we have a geographical view of the net? Not sure it make a lot of sense for me to forward several thousand miles / km, over to Sampsa... just to return to a "local" machine here in the states... Thanks (and, apologies if its already been queried), Joe

14 years, 9 months

Node update

by jferraro＠gmail.com

Currently in the Louisville, KY area. What makes the most sense regarding the layout of areas (is that even something to consider overall?!?!)? Obviously, right now with the ethernet bridging it seems to make sense... but I'm quite unsure of the failure mode of DECnet. Just wondering if any planning was necessary / made sense overall. Take care, Joe On Tue, Jul 6, 2010 at 10:15 PM, Steve Davidson <davidson at declab.net> wrote: Joe, Where are you (in the states)? -Steve Hollis, New Hampshire > > --001485e8cefcc738be048ac0ba71 > Content-Type: text/plain; charset=ISO-8859-1 > > Johnny, > > At the present, I'm hitching a ride with Sampsa ... > > I've taken: > > 8.501 - WOPR > 8.502 - SIOP > > Do we have a geographical view of the net? Not sure it make a lot of sense > for me to forward several thousand miles / km, over to Sampsa... just to > return to a "local" machine here in the states... > > > Thanks (and, apologies if its already been queried), > > Joe > > --001485e8cefcc738be048ac0ba71 > Content-Type: text/html; charset=ISO-8859-1 > Content-Transfer-Encoding: quoted-printable > > Johnny, At the present, I'm hitching a ride with Sampsa ... = > I've taken: 8.501 - WOPR 8.502 - SIOP Do we have = > a geographical view of the net? Not sure it make a lot of sense for me to f= > orward several thousand miles / km, over to Sampsa... just to return to a &= > quot;local" machine here in the states... > Thanks (and, apologies if its already been queried), Joe > > --001485e8cefcc738be048ac0ba71-- >

14 years, 9 months

Node update

by gregg.drwho8＠gmail.com

On Tue, Jul 6, 2010 at 10:15 PM, Steve Davidson <davidson at declab.net> wrote: Joe, Where are you (in the states)? -Steve Hollis, New Hampshire --001485e8cefcc738be048ac0ba71 Content-Type: text/plain; charset=ISO-8859-1 Johnny, At the present, I'm hitching a ride with Sampsa ... I've taken: 8.501 - WOPR 8.502 - SIOP Do we have a geographical view of the net? Not sure it make a lot of sense for me to forward several thousand miles / km, over to Sampsa... just to return to a "local" machine here in the states... Thanks (and, apologies if its already been queried), Joe --001485e8cefcc738be048ac0ba71 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Johnny, At the present, I'm hitching a ride with Sampsa ... = I've taken: 8.501 - WOPR 8.502 - SIOP Do we have = a geographical view of the net? Not sure it make a lot of sense for me to f= orward several thousand miles / km, over to Sampsa... just to return to a &= quot;local" machine here in the states... Thanks (and, apologies if its already been queried), Joe --001485e8cefcc738be048ac0ba71-- Hello! Especially since I happen to know that the majority of the military's systems for running the deterrent was in fact based on DEC hardware. For example at one point the silos ran PDP-8s and then PDP-11s locally. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again."

14 years, 9 months

Moving MIM

by pontus＠update.uu.se

Hi We will move MIM physically on thursday in order to reorganise our computer room. We should make it without any downtime, but you never know. So if your terminal goes blank on thursday, you know why :) Regards, Pontus.

14 years, 9 months

MIM updated with the latest supported version of NETUPDATE.COM

by davidson＠declab.net

The latest "supported" version of NETUPDATE.COM has been copied over to MIM in the default DECnet directory (MIM::US:[DECNET]). This is the same version that can be found at SGC::[DECNET]. If you are already running edit level 4 (NETUPDATE.COM;4) then you are running the latest version. -Steve

14 years, 9 months

Attaching to hecnet

by bqt＠softjar.se

Hans, I was actually thinking of the IP address, not the DECnet address. But since you provided that in a previous mail in this thread, I'll assume that is still correct, and do the config on my side now. Keep in touch... I suspect we'll have to talk more in a few minutes... Johnny H Vlems wrote: Johnny, here goes: - The UDP port number is 4711. - The machine in question is a VAXstation 4000 model 90A, DECnet address 1.1010, name NIKKEL. The machine will eventually get address 44.11 once I get this working. Hans -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens Johnny Billquist Verzonden: dinsdag, juli 2010 14:15 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet Yes, Hans. It is correct that I have to do something too... I need to add you to my config file. In order for that, I need to know both what machine to add, and what port number you are using. Johnny H Vlems wrote: I think Johnny has to do something at his end to make this work. The bridge software points to port 4711 (TCP right, not UDP) on psilo.update.uu.se I should be able to set host 8592, right? -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens Sampsa Laine Verzonden: maandag, juli 2010 22:01 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet You should probably copy the node database off MIM, there's also a web based node listing tool here: http://rhesus.sampsa.com/cgi-bin/hecnetinfo/hecnetinfo.com Sampsa On 5 Jul 2010, at 20:59, H Vlems wrote: Good news Johnny, the bridge program runs! Now how do I find other nodes in area 1? My own system uses DECnet address 1.1010 The outside ip address of my adsl router is: 87.209.50.192 Hans -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens Johnny Billquist Verzonden: vrijdag, juli 2010 9:36 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet Both sides needs to agree on that, and add it at both ends, or LAT traffic will not pass through... Johnny Steve Davidson wrote: If you are considering the bridge AND you are running LAT then you might want to consider adding LAT to bridge.conf. -Steve Hi. H Vlems wrote: OK, let's try the bridge option first. Could you give me a sample .conf file that I can use? Hmm. Not one that you can use straight away, no. However, it should look something like this: ================ [bridge] local <your ethernet interface name> update psilo.update.uu.se:4711 [decnet] local update ================= And that's it. What your local ethernet name is, I have no idea. My external IP address is: Name: osmium.homeip.net Address: 87.209.50.192 That is something I need for my side of the bridge. In addition, I also need to know what port number you will be using. I assume that a NAT entry is needed on my ADSL router, right? Would that be for port 4711 (as in eau de cologne ??) Yes, 4711 is named after the water from Cologne. :-) (Very oldish hacker folklore that I suspect people nowadays might not know...) And yes, if you have NAT running, you will need to forward traffic between your box, at whatever port you are using, and psilo.update.uu.se:4711. And this is UDP traffic. Johnny Hans -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens Johnny Billquist Verzonden: woensdag, juni 2010 14:16 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet Hi, Hans. H Vlems wrote: OK Johnny, talk to me :-) This is my plan: I intend to modify two systems to try the connection to HECnet. 1) I have a linux system under Fedora 9 that will run the bridge software and an Alpha Server 1200 under VMS V8.3 and DECnet phase IV, address 1.1010. That should work without any strange problems. You'll probably want to connect the bridge to me in that case. Let me know when you are ready to try. 2) a VAXstation 4000 model 90A, running VMS V7.3 and DECnet phase V, in area 44. I'd like to try that connection without the linux system. You need to find someone who can act as the other end in this case. Which I suspect meaning someone running phase V and as an area router. I don't know who might be doing this. Maybe someone who do can speak up. Anyone know if this would be compatible with DECnet over IP as Multinet does it? Option 2 is my preferred situation since it removes a by and large unknown factor from the equation (the linux box). Sure. We just need to identify someone you can connect to. So, what do I need to know and to do to make this work? Someone to connect to... Johnny Hans -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens Johnny Billquist Verzonden: maandag, juni 2010 21:03 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet H Vlems wrote: What I meant with the phase III-IV-V answer is that direct connectivity between a phase V and phase III system won't work. But poor man's routing will work with a phase IV node in between. Functionality of course is limited by the phase III host :-) I wonder if phase III to phase V neccesarily will not work. However, DEC never guaranteed that it will work, nor did they ever try it. But you're absolutely right that very few people will have a phase III system, RT-11 being the most likely candidate? Probably. Or if someone is running some old versions of other systems. I've seen the bridge program, but am not sure how to make the .conf file work. Is it possible to use DECnet address 1.1010 to try and make this work? Yes. 1.1010 is not used by anyone, so that node number would be ok to use to test. But you also need to talk with me (or someone else) with the bridge running, to act as the remote end. Johnny Hans -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens Johnny Billquist Verzonden: maandag, juni 2010 11:02 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet Hi. H Vlems wrote: DECnet phase IV nodes are backwards compatible with phase III. Yes. But the question here was if phase V will interoperate with phase III. I don't know the answer to that one, but on the other hand, I don't think anyone around is running phase III anyway. There are no restrictions in functionality between phase IV nodes and phase V as seen by the unpriviledged user. Area routing may be an issue on Alpha, and of course ncl is more of a pain to remember than ncp ;-) True, as far as that goes. However, I am not sure that a phase V node can operate as a phase IV area router. Someone else pointed out that although DEC claimed that alphas could not be area routers, that information is incorrect, and you can just tell an Alpha VMS phase IV node to be an area router, if you want to. However, DECnet+ is phase V, and all bets are off. :-) And yes, not only are the NCL commands more difficult to remember (atleast for me), the node name management is way more difficult as well. Do anyone know how you copy a nodename database from another machine with DECnet+? Two questions: 1-May I use area 44? Sure. 2-Is there a short guide to set up DECnet over IP to connect to HECnet? Not that I know of. Maybe Mark Wickens have something on hecnet.eu ? My page (http://www.update.uu.se/~bqt/hecnet.html) only have information about the bridge. Johnny Hans -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner- hecnet at Update.UU.SE] Namens Marc Chametzky Verzonden: maandag, juni 2010 0:04 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet DECnet-Plus isn't able to connect, or at least reliably connect to all OS's that can potentially be on HECnet. I forget what all OS's I was having issues with, I know one was RSTS/E v10.1, but I want to say it also included VAX/VMS. Once I *upgraded* my Alpha running OpenVMS to DECnet Phase IV, all these issues went away. These were things as simple as SET HOST. It's probably that DECnet-Plus (Phase V) cannot speak with DECnet Phase III (such as on RSTS/E and TOPS-10/20). That's my guess anyway. Phase V should be able to communicate with VAX/VMS since that's Phase IV, which is the gold standard of DECnet, IMHO. --Marc Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2966 - datum van uitgifte: 06/27/10 08:35:00 Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2968 - datum van uitgifte: 06/28/10 08:37:00 Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2969 - datum van uitgifte: 06/28/10 20:35:00 Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2969 - datum van uitgifte: 06/28/10 20:35:00 Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2975 - datum van uitgifte: 07/01/10 08:35:00 Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2983 - datum van uitgifte: 07/05/10 08:36:00 Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2983 - datum van uitgifte: 07/05/10 08:36:00

14 years, 9 months

Attaching to hecnet

by hvlems＠zonnet.nl

Johnny, here goes: - The UDP port number is 4711. - The machine in question is a VAXstation 4000 model 90A, DECnet address 1.1010, name NIKKEL. The machine will eventually get address 44.11 once I get this working. Hans -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens Johnny Billquist Verzonden: dinsdag, juli 2010 14:15 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet Yes, Hans. It is correct that I have to do something too... I need to add you to my config file. In order for that, I need to know both what machine to add, and what port number you are using. Johnny H Vlems wrote: I think Johnny has to do something at his end to make this work. The bridge software points to port 4711 (TCP right, not UDP) on psilo.update.uu.se I should be able to set host 8592, right? -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens Sampsa Laine Verzonden: maandag, juli 2010 22:01 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet You should probably copy the node database off MIM, there's also a web based node listing tool here: http://rhesus.sampsa.com/cgi-bin/hecnetinfo/hecnetinfo.com Sampsa On 5 Jul 2010, at 20:59, H Vlems wrote: Good news Johnny, the bridge program runs! Now how do I find other nodes in area 1? My own system uses DECnet address 1.1010 The outside ip address of my adsl router is: 87.209.50.192 Hans -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens Johnny Billquist Verzonden: vrijdag, juli 2010 9:36 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet Both sides needs to agree on that, and add it at both ends, or LAT traffic will not pass through... Johnny Steve Davidson wrote: If you are considering the bridge AND you are running LAT then you might want to consider adding LAT to bridge.conf. -Steve Hi. H Vlems wrote: OK, let's try the bridge option first. Could you give me a sample .conf file that I can use? Hmm. Not one that you can use straight away, no. However, it should look something like this: ================ [bridge] local <your ethernet interface name> update psilo.update.uu.se:4711 [decnet] local update ================= And that's it. What your local ethernet name is, I have no idea. My external IP address is: Name: osmium.homeip.net Address: 87.209.50.192 That is something I need for my side of the bridge. In addition, I also need to know what port number you will be using. I assume that a NAT entry is needed on my ADSL router, right? Would that be for port 4711 (as in eau de cologne ??) Yes, 4711 is named after the water from Cologne. :-) (Very oldish hacker folklore that I suspect people nowadays might not know...) And yes, if you have NAT running, you will need to forward traffic between your box, at whatever port you are using, and psilo.update.uu.se:4711. And this is UDP traffic. Johnny Hans -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens Johnny Billquist Verzonden: woensdag, juni 2010 14:16 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet Hi, Hans. H Vlems wrote: OK Johnny, talk to me :-) This is my plan: I intend to modify two systems to try the connection to HECnet. 1) I have a linux system under Fedora 9 that will run the bridge software and an Alpha Server 1200 under VMS V8.3 and DECnet phase IV, address 1.1010. That should work without any strange problems. You'll probably want to connect the bridge to me in that case. Let me know when you are ready to try. 2) a VAXstation 4000 model 90A, running VMS V7.3 and DECnet phase V, in area 44. I'd like to try that connection without the linux system. You need to find someone who can act as the other end in this case. Which I suspect meaning someone running phase V and as an area router. I don't know who might be doing this. Maybe someone who do can speak up. Anyone know if this would be compatible with DECnet over IP as Multinet does it? Option 2 is my preferred situation since it removes a by and large unknown factor from the equation (the linux box). Sure. We just need to identify someone you can connect to. So, what do I need to know and to do to make this work? Someone to connect to... Johnny Hans -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens Johnny Billquist Verzonden: maandag, juni 2010 21:03 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet H Vlems wrote: What I meant with the phase III-IV-V answer is that direct connectivity between a phase V and phase III system won't work. But poor man's routing will work with a phase IV node in between. Functionality of course is limited by the phase III host :-) I wonder if phase III to phase V neccesarily will not work. However, DEC never guaranteed that it will work, nor did they ever try it. But you're absolutely right that very few people will have a phase III system, RT-11 being the most likely candidate? Probably. Or if someone is running some old versions of other systems. I've seen the bridge program, but am not sure how to make the .conf file work. Is it possible to use DECnet address 1.1010 to try and make this work? Yes. 1.1010 is not used by anyone, so that node number would be ok to use to test. But you also need to talk with me (or someone else) with the bridge running, to act as the remote end. Johnny Hans -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens Johnny Billquist Verzonden: maandag, juni 2010 11:02 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet Hi. H Vlems wrote: DECnet phase IV nodes are backwards compatible with phase III. Yes. But the question here was if phase V will interoperate with phase III. I don't know the answer to that one, but on the other hand, I don't think anyone around is running phase III anyway. There are no restrictions in functionality between phase IV nodes and phase V as seen by the unpriviledged user. Area routing may be an issue on Alpha, and of course ncl is more of a pain to remember than ncp ;-) True, as far as that goes. However, I am not sure that a phase V node can operate as a phase IV area router. Someone else pointed out that although DEC claimed that alphas could not be area routers, that information is incorrect, and you can just tell an Alpha VMS phase IV node to be an area router, if you want to. However, DECnet+ is phase V, and all bets are off. :-) And yes, not only are the NCL commands more difficult to remember (atleast for me), the node name management is way more difficult as well. Do anyone know how you copy a nodename database from another machine with DECnet+? Two questions: 1-May I use area 44? Sure. 2-Is there a short guide to set up DECnet over IP to connect to HECnet? Not that I know of. Maybe Mark Wickens have something on hecnet.eu ? My page (http://www.update.uu.se/~bqt/hecnet.html) only have information about the bridge. Johnny Hans -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner- hecnet at Update.UU.SE] Namens Marc Chametzky Verzonden: maandag, juni 2010 0:04 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet DECnet-Plus isn't able to connect, or at least reliably connect to all OS's that can potentially be on HECnet. I forget what all OS's I was having issues with, I know one was RSTS/E v10.1, but I want to say it also included VAX/VMS. Once I *upgraded* my Alpha running OpenVMS to DECnet Phase IV, all these issues went away. These were things as simple as SET HOST. It's probably that DECnet-Plus (Phase V) cannot speak with DECnet Phase III (such as on RSTS/E and TOPS-10/20). That's my guess anyway. Phase V should be able to communicate with VAX/VMS since that's Phase IV, which is the gold standard of DECnet, IMHO. --Marc Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2966 - datum van uitgifte: 06/27/10 08:35:00 Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2968 - datum van uitgifte: 06/28/10 08:37:00 Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2969 - datum van uitgifte: 06/28/10 20:35:00 Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2969 - datum van uitgifte: 06/28/10 20:35:00 Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2975 - datum van uitgifte: 07/01/10 08:35:00 Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2983 - datum van uitgifte: 07/05/10 08:36:00 Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2983 - datum van uitgifte: 07/05/10 08:36:00

14 years, 9 months

Attaching to hecnet

by bqt＠softjar.se

Yes, Hans. It is correct that I have to do something too... I need to add you to my config file. In order for that, I need to know both what machine to add, and what port number you are using. Johnny H Vlems wrote: I think Johnny has to do something at his end to make this work. The bridge software points to port 4711 (TCP right, not UDP) on psilo.update.uu.se I should be able to set host 8592, right? -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens Sampsa Laine Verzonden: maandag, juli 2010 22:01 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet You should probably copy the node database off MIM, there's also a web based node listing tool here: http://rhesus.sampsa.com/cgi-bin/hecnetinfo/hecnetinfo.com Sampsa On 5 Jul 2010, at 20:59, H Vlems wrote: Good news Johnny, the bridge program runs! Now how do I find other nodes in area 1? My own system uses DECnet address 1.1010 The outside ip address of my adsl router is: 87.209.50.192 Hans -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens Johnny Billquist Verzonden: vrijdag, juli 2010 9:36 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet Both sides needs to agree on that, and add it at both ends, or LAT traffic will not pass through... Johnny Steve Davidson wrote: If you are considering the bridge AND you are running LAT then you might want to consider adding LAT to bridge.conf. -Steve Hi. H Vlems wrote: OK, let's try the bridge option first. Could you give me a sample .conf file that I can use? Hmm. Not one that you can use straight away, no. However, it should look something like this: ================ [bridge] local <your ethernet interface name> update psilo.update.uu.se:4711 [decnet] local update ================= And that's it. What your local ethernet name is, I have no idea. My external IP address is: Name: osmium.homeip.net Address: 87.209.50.192 That is something I need for my side of the bridge. In addition, I also need to know what port number you will be using. I assume that a NAT entry is needed on my ADSL router, right? Would that be for port 4711 (as in eau de cologne ??) Yes, 4711 is named after the water from Cologne. :-) (Very oldish hacker folklore that I suspect people nowadays might not know...) And yes, if you have NAT running, you will need to forward traffic between your box, at whatever port you are using, and psilo.update.uu.se:4711. And this is UDP traffic. Johnny Hans -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens Johnny Billquist Verzonden: woensdag, juni 2010 14:16 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet Hi, Hans. H Vlems wrote: OK Johnny, talk to me :-) This is my plan: I intend to modify two systems to try the connection to HECnet. 1) I have a linux system under Fedora 9 that will run the bridge software and an Alpha Server 1200 under VMS V8.3 and DECnet phase IV, address 1.1010. That should work without any strange problems. You'll probably want to connect the bridge to me in that case. Let me know when you are ready to try. 2) a VAXstation 4000 model 90A, running VMS V7.3 and DECnet phase V, in area 44. I'd like to try that connection without the linux system. You need to find someone who can act as the other end in this case. Which I suspect meaning someone running phase V and as an area router. I don't know who might be doing this. Maybe someone who do can speak up. Anyone know if this would be compatible with DECnet over IP as Multinet does it? Option 2 is my preferred situation since it removes a by and large unknown factor from the equation (the linux box). Sure. We just need to identify someone you can connect to. So, what do I need to know and to do to make this work? Someone to connect to... Johnny Hans -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens Johnny Billquist Verzonden: maandag, juni 2010 21:03 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet H Vlems wrote: What I meant with the phase III-IV-V answer is that direct connectivity between a phase V and phase III system won't work. But poor man's routing will work with a phase IV node in between. Functionality of course is limited by the phase III host :-) I wonder if phase III to phase V neccesarily will not work. However, DEC never guaranteed that it will work, nor did they ever try it. But you're absolutely right that very few people will have a phase III system, RT-11 being the most likely candidate? Probably. Or if someone is running some old versions of other systems. I've seen the bridge program, but am not sure how to make the .conf file work. Is it possible to use DECnet address 1.1010 to try and make this work? Yes. 1.1010 is not used by anyone, so that node number would be ok to use to test. But you also need to talk with me (or someone else) with the bridge running, to act as the remote end. Johnny Hans -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens Johnny Billquist Verzonden: maandag, juni 2010 11:02 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet Hi. H Vlems wrote: DECnet phase IV nodes are backwards compatible with phase III. Yes. But the question here was if phase V will interoperate with phase III. I don't know the answer to that one, but on the other hand, I don't think anyone around is running phase III anyway. There are no restrictions in functionality between phase IV nodes and phase V as seen by the unpriviledged user. Area routing may be an issue on Alpha, and of course ncl is more of a pain to remember than ncp ;-) True, as far as that goes. However, I am not sure that a phase V node can operate as a phase IV area router. Someone else pointed out that although DEC claimed that alphas could not be area routers, that information is incorrect, and you can just tell an Alpha VMS phase IV node to be an area router, if you want to. However, DECnet+ is phase V, and all bets are off. :-) And yes, not only are the NCL commands more difficult to remember (atleast for me), the node name management is way more difficult as well. Do anyone know how you copy a nodename database from another machine with DECnet+? Two questions: 1-May I use area 44? Sure. 2-Is there a short guide to set up DECnet over IP to connect to HECnet? Not that I know of. Maybe Mark Wickens have something on hecnet.eu ? My page (http://www.update.uu.se/~bqt/hecnet.html) only have information about the bridge. Johnny Hans -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner- hecnet at Update.UU.SE] Namens Marc Chametzky Verzonden: maandag, juni 2010 0:04 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet DECnet-Plus isn't able to connect, or at least reliably connect to all OS's that can potentially be on HECnet. I forget what all OS's I was having issues with, I know one was RSTS/E v10.1, but I want to say it also included VAX/VMS. Once I *upgraded* my Alpha running OpenVMS to DECnet Phase IV, all these issues went away. These were things as simple as SET HOST. It's probably that DECnet-Plus (Phase V) cannot speak with DECnet Phase III (such as on RSTS/E and TOPS-10/20). That's my guess anyway. Phase V should be able to communicate with VAX/VMS since that's Phase IV, which is the gold standard of DECnet, IMHO. --Marc Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2966 - datum van uitgifte: 06/27/10 08:35:00 Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2968 - datum van uitgifte: 06/28/10 08:37:00 Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2969 - datum van uitgifte: 06/28/10 20:35:00 Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2969 - datum van uitgifte: 06/28/10 20:35:00 Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2975 - datum van uitgifte: 07/01/10 08:35:00 Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2983 - datum van uitgifte: 07/05/10 08:36:00

14 years, 9 months

Attaching to hecnet

by hvlems＠zonnet.nl

I'm reading chapter 8 of the Network Management manual (DECnet plus doc kit). \Hans -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens Sampsa Laine Verzonden: zondag, juni 2010 23:06 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet I've got a SIMH VAX with Decnet+ set up somewhere, so I might be up for trying to get the Decnet+-IP-tunnel thingie going. Sampsa On 27 Jun 2010, at 22:03, Johnny Billquist wrote: Kari Uusim ki wrote: On 27.6.2010 13:44, Mark Wickens wrote: Hi Guys, There is some info on http://hecnet.eu but at the moment it is very targeted to a 'standard' installation. If you end up using a non-standard installation please let me know what you have to do so I can add the info to the website. If you want your own area Johnny is your man - he is busy but will get round to answering your query. I'd be interested to know if it's possible to get the bridge working under tru64 also... Regards, Mark . Well, what is standard and what is not. That is a question of from which point of view you are thinking, isn't it? ;) To some people the DECnet-plus or Multinet with DECnet-over-IP is standard and to others the Cisco tunneling is standard. To the HECnet community the bridge software is standard.

14 years, 9 months

Attaching to hecnet

by hvlems＠zonnet.nl

Err, right you are (red face, Johnny did write that). I corrected that on the adsl router but still no joy. -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens Steve Davidson Verzonden: maandag, juli 2010 22:39 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet UDP is what the bridge makes use of. -Steve I think Johnny has to do something at his end to make this work. The bridge software points to port 4711 (TCP right, not UDP) on psilo.update.uu.se I should be able to set host 8592, right? -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens Sampsa Laine Verzonden: maandag, juli 2010 22:01 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet You should probably copy the node database off MIM, there's also a web based node listing tool here: http://rhesus.sampsa.com/cgi-bin/hecnetinfo/hecnetinfo.com Sampsa On 5 Jul 2010, at 20:59, H Vlems wrote: Good news Johnny, the bridge program runs! Now how do I find other nodes in area 1? My own system uses DECnet address 1.1010 The outside ip address of my adsl router is: 87.209.50.192 Hans -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens Johnny Billquist Verzonden: vrijdag, juli 2010 9:36 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet Both sides needs to agree on that, and add it at both ends, or LAT traffic will not pass through... Johnny Steve Davidson wrote: If you are considering the bridge AND you are running LAT then you might want to consider adding LAT to bridge.conf. -Steve Hi. H Vlems wrote: OK, let's try the bridge option first. Could you give me a sample .conf file that I can use? Hmm. Not one that you can use straight away, no. However, it should look something like this: ================ [bridge] local <your ethernet interface name> update psilo.update.uu.se:4711 [decnet] local update ================= And that's it. What your local ethernet name is, I have no idea. My external IP address is: Name: osmium.homeip.net Address: 87.209.50.192 That is something I need for my side of the bridge. In addition, I also need to know what port number you will be using. I assume that a NAT entry is needed on my ADSL router, right? Would that be for port 4711 (as in eau de cologne ??) Yes, 4711 is named after the water from Cologne. :-) (Very oldish hacker folklore that I suspect people nowadays might not know...) And yes, if you have NAT running, you will need to forward traffic between your box, at whatever port you are using, and psilo.update.uu.se:4711. And this is UDP traffic. Johnny Hans -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens Johnny Billquist Verzonden: woensdag, juni 2010 14:16 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet Hi, Hans. H Vlems wrote: OK Johnny, talk to me :-) This is my plan: I intend to modify two systems to try the connection to HECnet. 1) I have a linux system under Fedora 9 that will run the bridge software and an Alpha Server 1200 under VMS V8.3 and DECnet phase IV, address 1.1010. That should work without any strange problems. You'll probably want to connect the bridge to me in that case. Let me know when you are ready to try. 2) a VAXstation 4000 model 90A, running VMS V7.3 and DECnet phase V, in area 44. I'd like to try that connection without the linux system. You need to find someone who can act as the other end in this case. Which I suspect meaning someone running phase V and as an area router. I don't know who might be doing this. Maybe someone who do can speak up. Anyone know if this would be compatible with DECnet over IP as Multinet does it? Option 2 is my preferred situation since it removes a by and large unknown factor from the equation (the linux box). Sure. We just need to identify someone you can connect to. So, what do I need to know and to do to make this work? Someone to connect to... Johnny Hans -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens Johnny Billquist Verzonden: maandag, juni 2010 21:03 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet H Vlems wrote: What I meant with the phase III-IV-V answer is that direct connectivity between a phase V and phase III system won't work. But poor man's routing will work with a phase IV node in between. Functionality of course is limited by the phase III host :-) I wonder if phase III to phase V neccesarily will not work. However, DEC never guaranteed that it will work, nor did they ever try it. But you're absolutely right that very few people will have a phase III system, RT-11 being the most likely candidate? Probably. Or if someone is running some old versions of other systems. I've seen the bridge program, but am not sure how to make the .conf file work. Is it possible to use DECnet address 1.1010 to try and make this work? Yes. 1.1010 is not used by anyone, so that node number would be ok to use to test. But you also need to talk with me (or someone else) with the bridge running, to act as the remote end. Johnny Hans -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens Johnny Billquist Verzonden: maandag, juni 2010 11:02 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet Hi. H Vlems wrote: DECnet phase IV nodes are backwards compatible with phase III. Yes. But the question here was if phase V will interoperate with phase III. I don't know the answer to that one, but on the other hand, I don't think anyone around is running phase III anyway. There are no restrictions in functionality between phase IV nodes and phase V as seen by the unpriviledged user. Area routing may be an issue on Alpha, and of course ncl is more of a pain to remember than ncp ;-) True, as far as that goes. However, I am not sure that a phase V node can operate as a phase IV area router. Someone else pointed out that although DEC claimed that alphas could not be area routers, that information is incorrect, and you can just tell an Alpha VMS phase IV node to be an area router, if you want to. However, DECnet+ is phase V, and all bets are off. :-) And yes, not only are the NCL commands more difficult to remember (atleast for me), the node name management is way more difficult as well. Do anyone know how you copy a nodename database from another machine with DECnet+? Two questions: 1-May I use area 44? Sure. 2-Is there a short guide to set up DECnet over IP to connect to HECnet? Not that I know of. Maybe Mark Wickens have something on hecnet.eu ? My page (http://www.update.uu.se/~bqt/hecnet.html) only have information about the bridge. Johnny Hans -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner- hecnet at Update.UU.SE] Namens Marc Chametzky Verzonden: maandag, juni 2010 0:04 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Attaching to hecnet DECnet-Plus isn't able to connect, or at least reliably connect to all OS's that can potentially be on HECnet. I forget what all OS's I was having issues with, I know one was RSTS/E v10.1, but I want to say it also included VAX/VMS. Once I *upgraded* my Alpha running OpenVMS to DECnet Phase IV, all these issues went away. These were things as simple as SET HOST. It's probably that DECnet-Plus (Phase V) cannot speak with DECnet Phase III (such as on RSTS/E and TOPS-10/20). That's my guess anyway. Phase V should be able to communicate with VAX/VMS since that's Phase IV, which is the gold standard of DECnet, IMHO. --Marc Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2966 - datum van uitgifte: 06/27/10 08:35:00 Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2968 - datum van uitgifte: 06/28/10 08:37:00 Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2969 - datum van uitgifte: 06/28/10 20:35:00 Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2969 - datum van uitgifte: 06/28/10 20:35:00 Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2975 - datum van uitgifte: 07/01/10 08:35:00 Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2983 - datum van uitgifte: 07/05/10 08:36:00 Geen virus gevonden in het binnenkomende-bericht. Gecontroleerd door AVG - www.avg.com Versie: 9.0.830 / Virusdatabase: 271.1.1/2983 - datum van uitgifte: 07/05/10 08:36:00

14 years, 9 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet