HECnet January 2013

hecnet@lists.dfupdate.se

40 participants
1313 discussions

Sync serial bridging over Ethernet, was Re: [HECnet] Multi-floor household (DECnet) routing help needed

by jg＠jordi.guillaumes.name

El 22/01/2013, a les 11:43, Mark Benson <md.benson at gmail.com> va escriure: Also, how does iTerm2 in in Mac OS X come out? I'm installing it from ports now... By the way... how do you configure putty to be identified as a vt200 from VMS? All I get is VT102... Jordi Guillaumes i Pons jg at jordi.guillaumes.name HECnet: BITXOV::JGUILLAUMES

11 years, 10 months

Sync serial bridging over Ethernet, was Re: [HECnet] Multi-floor household (DECnet) routing help needed

by md.benson＠gmail.com

Approaching this from a position of significant ignorance, How do things like PowerTerm (included in HP Pathworks) and AnzioWin stack up? Also, how does iTerm2 in in Mac OS X come out? I'm just curious as I use those primarily. -- Mark Benson http://markbenson.org/blog http://twitter.com/MDBenson

11 years, 10 months

Sync serial bridging over Ethernet, was Re: [HECnet] Multi-floor household (DECnet) routing help needed

by jg＠jordi.guillaumes.name

El 21/01/2013, a les 21:49, Dave McGuire <mcguire at neurotica.com> va escriure: On 01/21/2013 03:09 PM, Brian Schenkenberger, VAXman- wrote: PuTTY has been ported to Linux too? WTF? WHY?! For one, VTxxx compatibility. Unless one really understands the Xresources and how to move the appropriate fonts from VMS to Linux, build the fontdir, reset the font cache and update the font path, PuTTY is a right-out-of-the- box VTxxx emulation. WRT terminal emulators, I use ZOC (http://www.emtec.com/zoc/) both in macOs and windows, and EVEN in linux (under wine). I have been using it since the OS/2 times, and it works really well emulating both VT10X and VT220, including the keypad stuff. Yes, its shareware and it costs some bucks, but IMO it is worth it. Jordi Guillaumes i Pons jg at jordi.guillaumes.name HECnet: BITXOV::JGUILLAUMES

11 years, 10 months

HECnet Area Request

by bqt＠softjar.se

On 2013-01-21 23:43, Dave McGuire wrote: On 01/21/2013 05:42 PM, Johnny Billquist wrote: Just as a summary. The *RTR nodes known: 1.1023 A1RTR 5.1023 A5RTR 9.1023 A9RTR 11.1023 A11RTR 42.1023 A42RTR 44.1023 A44RTR 54.100 A54RTR 61.1023 A61RTR Just as an FYI. And no, people do not need to follow this naming scheme. It's not really making any difference. It sure is cleaning up the namespace! Something funny with the nodenames on MIM right now. I've seen this once before, and don't really know what is causing it. If you list all known nodes, lots of them are missing. However, if you list all nodes in one area, all will show up, even when they aren't shown in the list of all known nodes. I suspect some kind of odd bug in RSX. I'll investigate, but meanwhile, you can always grab MIM::US:[DECNET]FIX.CMD, which is just a command file that defines all nodes (except for MIM::) as NCP commands. Johnny -- Johnny Billquist || "I'm on a bus || on a psychedelic trip email: bqt at softjar.se || Reading murder books pdp is alive! || tryin' to stay hip" - B. Idol

11 years, 10 months

HECnet Area Request

by mcguire＠neurotica.com

On 01/21/2013 05:55 PM, Ian McLaughlin wrote: Note to people who have tunnels terminating here: I'll be renumbering my Cisco from 61.1 to 61.1023 at some point soon, likely tonight. You may experience some weirdness for a little while. As long as the terminating IP address for the tunnel doesn't change, then I don't think this will make a difference, other than the link going down and up, right? We'll see! ;) -Dave -- Dave McGuire, AK4HZ New Kensington, PA

11 years, 10 months

HECnet Area Request

by bqt＠softjar.se

On 2013-01-21 23:55, Ian McLaughlin wrote: On 2013-01-21, at 2:43 PM, Dave McGuire <mcguire at neurotica.com> wrote: Note to people who have tunnels terminating here: I'll be renumbering my Cisco from 61.1 to 61.1023 at some point soon, likely tonight. You may experience some weirdness for a little while. As long as the terminating IP address for the tunnel doesn't change, then I don't think this will make a difference, other than the link going down and up, right? Correct. And you get a new (other) adjacency, obviously... Johnny -- Johnny Billquist || "I'm on a bus || on a psychedelic trip email: bqt at softjar.se || Reading murder books pdp is alive! || tryin' to stay hip" - B. Idol

11 years, 10 months

HECnet Area Request

by ian＠platinum.net

On 2013-01-21, at 2:43 PM, Dave McGuire <mcguire at neurotica.com> wrote: Note to people who have tunnels terminating here: I'll be renumbering my Cisco from 61.1 to 61.1023 at some point soon, likely tonight. You may experience some weirdness for a little while. As long as the terminating IP address for the tunnel doesn't change, then I don't think this will make a difference, other than the link going down and up, right? Ian

11 years, 10 months

HECnet Area Request

by b4＠gewt.net

On 21 Jan 2013, at 17:43, Dave McGuire <mcguire at neurotica.com> wrote: On 01/21/2013 05:42 PM, Johnny Billquist wrote: Just as a summary. The *RTR nodes known: 1.1023 A1RTR 5.1023 A5RTR 9.1023 A9RTR 11.1023 A11RTR 42.1023 A42RTR 44.1023 A44RTR 54.100 A54RTR 61.1023 A61RTR Just as an FYI. And no, people do not need to follow this naming scheme. It's not really making any difference. It sure is cleaning up the namespace! Definitely. :) -Dave -- Dave McGuire, AK4HZ New Kensington, PA

11 years, 10 months

HECnet Area Request

by b4＠gewt.net

On 21 Jan 2013, at 17:43, Dave McGuire <mcguire at neurotica.com> wrote: On 01/21/2013 05:40 PM, Johnny Billquist wrote: A17RTR:: would work... :) Hey, that's a good scheme. I will likely do that as well. Several areas already do that. :-) Excellent. :-) Would you please remove "GW" at 61.1 and add "A61RTR" as 61.1023? Done. Thanks! Note to people who have tunnels terminating here: I'll be renumbering my Cisco from 61.1 to 61.1023 at some point soon, likely tonight. You may experience some weirdness for a little while. Okay. I'll keep an eye out. ;) -Dave -- Dave McGuire, AK4HZ New Kensington, PA

11 years, 10 months

HECnet Area Request

by mcguire＠neurotica.com

On 01/21/2013 05:42 PM, Johnny Billquist wrote: Just as a summary. The *RTR nodes known: 1.1023 A1RTR 5.1023 A5RTR 9.1023 A9RTR 11.1023 A11RTR 42.1023 A42RTR 44.1023 A44RTR 54.100 A54RTR 61.1023 A61RTR Just as an FYI. And no, people do not need to follow this naming scheme. It's not really making any difference. It sure is cleaning up the namespace! -Dave -- Dave McGuire, AK4HZ New Kensington, PA

11 years, 10 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet January 2013