On Mon, Jan 21, 2013 at 9:41 AM, Brian Schenkenberger, VAXman-
<system at tmesis.com> wrote:
"John H. Reinhardt" <johnhreinhardt at yahoo.com> writes:
You have a working binary for PuTTY on OS X? I'm forced to use
Windows for work and I use PuTTY every day there. I'd love to have a
copy for my home Macs. Where is it available?
Google MacPorts and PuTTY. You'll have to build it. I did it back when
I was still running 10.4.something on the Mac as an academic exercise.
I don't really use it on Linux either. I'm more content with an xterm
and typing 'ssh ...'. To me, the command line is so much easier than a
GUI for something this simple. It's also easier when setting up various
port ssh-tunnels, IMNSHO.
I only mentioned PuTTY because I know the WEENDOZE camp is command line
challeneged.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
Hello!
I'm not command line challenged.
But I also use PuTTY on both Windows (here) and Linux. I've also built
it for my Slackware Linux system.
This discussion is becoming decidedly strange. The big problem here is
simply making things easier to work with.
However what further progress has been accomplished in sorting out how
to deliver serial over Ethernet directly?
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
"John H. Reinhardt" <johnhreinhardt at yahoo.com> writes:
You have a working binary for PuTTY on OS X? I'm forced to use
Windows for work and I use PuTTY every day there. I'd love to have a
copy for my home Macs. Where is it available?
Google MacPorts and PuTTY. You'll have to build it. I did it back when
I was still running 10.4.something on the Mac as an academic exercise.
I don't really use it on Linux either. I'm more content with an xterm
and typing 'ssh ...'. To me, the command line is so much easier than a
GUI for something this simple. It's also easier when setting up various
port ssh-tunnels, IMNSHO.
I only mentioned PuTTY because I know the WEENDOZE camp is command line
challeneged.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
On 1/21/2013 9:16 AM, Brian Schenkenberger, VAXman- wrote:
Sridhar Ayengar<ploopster at gmail.com> writes:
Dave McGuire wrote:> I've heard it a lot. It's just the Windows
people. "Terminal> programs are EXPENSIVE!" No. Idiots. Go get a
grownup OS and leave> Windows for the videogames.
Off the top of my head, I can name at least two dozen easy-to-install
free terminal emulators for Windows. There are probably a great many
more than that.
Is PuTTY not available for WEENDOZE???
On Mac OS X and Linux, it does a failrly reasonable job of digesting the
VT200 series escape sequences and even does DECSWL and DECDHL correctly.
If you want to test your emulator, telnet to great-escape.tmesis.com and
log in with VTTEST -- no password. It's a captive account that runs the
VTTEST suite.
Brian,
You have a working binary for PuTTY on OS X? I'm forced to use Windows for work and I use PuTTY every day there. I'd love to have a copy for my home Macs. Where is it available?
John
Sridhar Ayengar <ploopster at gmail.com> writes:
Dave McGuire wrote: > I've heard it a lot. It's just the Windows
people. "Terminal > programs are EXPENSIVE!" No. Idiots. Go get a
grownup OS and leave > Windows for the videogames.
Off the top of my head, I can name at least two dozen easy-to-install
free terminal emulators for Windows. There are probably a great many
more than that.
Is PuTTY not available for WEENDOZE???
On Mac OS X and Linux, it does a failrly reasonable job of digesting the
VT200 series escape sequences and even does DECSWL and DECDHL correctly.
If you want to test your emulator, telnet to great-escape.tmesis.com and
log in with VTTEST -- no password. It's a captive account that runs the
VTTEST suite.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
Dave McGuire wrote:
I've heard it a lot. It's just the Windows people. "Terminal
programs are EXPENSIVE!" No. Idiots. Go get a grownup OS and leave
Windows for the videogames.
Off the top of my head, I can name at least two dozen easy-to-install free terminal emulators for Windows. There are probably a great many more than that.
Peace... Sridhar
On 2013-01-21 04:11, John H. Reinhardt wrote:
Re-sending during a lull in the action.
:-)
Sorry I dropped this. The bridge code can be found at http://www.update.uu.se/~bqt/hecnet
Areas were listed by Corey.
Johnny (now catching up...)
On 1/17/2013 8:20 AM, John H. Reinhardt wrote:
Hi Johnny,
My name is John Reinhardt. Long time HECnet lurker, occasional
poster and first time requester here. I'm about actually ready to put
some systems up and I'd like to request a HECnet area to use. Anything
that is free is fine, I don't have any special number desires.
I'm still working out how I will connect. I'm playing with the
virtual Cisco that Ian posted recently. Otherwise I may take a shot
at the bridge and see if I can get it running on my Vyatta
firewall/router.
Where is the latest version of the bridge code?
Regards,
John H. Reinhardt
--
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
Yeah, it was running under Linux, I basically took the Linux sources of the PHONE client and stripped it down to the DIR call, then just ran that over the whole nodelist every 5-10 mins.
Anyway, this latest thing I've built is literally a few .COM files that talk to a server on RHESUS.
sampsa
On 21 Jan 2013, at 08:44, Mark Wickens <mark at wickensonline.co.uk> wrote:
On 18/01/2013 16:06, Johnny Billquist wrote:
On 2013-01-18 07:41, sampsa at mac.com wrote:
Half a year or maybe a year ago. Sampsa was running a program which used PHONE to check who was logged in on various machines. When he tried all machines in area 1, MIM got loads of entries in the log for Sampsa's machine trying to talk with machines that were down.
(I might be remembering things wrong, and I might be mixing things up, but it was not as if MIM crashed or anything because of Sampsa's code, but I asked him to stop, as he was filling up plenty of logs as far as I can remember.)
Yeah, I didn't mean crashed MIM or anything, but caused problems - basically the phone directory just went through the nodelist and did a PHONE DIR to them..If a node was down, the call would fail.
It wasn't a good idea from BQT's side :)
I don't remember all the details now, but I think it was something with the DECnet stack you used which made this worse. I seem to remember trying the same thing myself in various ways I couldn't trigger the logging. Did you run it under Linux, or what was it?
Johnny
I seem to remember it was running under the decnet stack on linux?
On 18/01/2013 16:06, Johnny Billquist wrote:
On 2013-01-18 07:41, sampsa at mac.com wrote:
Half a year or maybe a year ago. Sampsa was running a program which used PHONE to check who was logged in on various machines. When he tried all machines in area 1, MIM got loads of entries in the log for Sampsa's machine trying to talk with machines that were down.
(I might be remembering things wrong, and I might be mixing things up, but it was not as if MIM crashed or anything because of Sampsa's code, but I asked him to stop, as he was filling up plenty of logs as far as I can remember.)
Yeah, I didn't mean crashed MIM or anything, but caused problems - basically the phone directory just went through the nodelist and did a PHONE DIR to them..If a node was down, the call would fail.
It wasn't a good idea from BQT's side :)
I don't remember all the details now, but I think it was something with the DECnet stack you used which made this worse. I seem to remember trying the same thing myself in various ways I couldn't trigger the logging. Did you run it under Linux, or what was it?
Johnny
I seem to remember it was running under the decnet stack on linux?
On 2013-01-20, at 9:05 PM, "John H. Reinhardt" <johnhreinhardt at yahoo.com> wrote:
I'm also playing with the virtual Cisco, but I'm unsure where to place it in my network. A simplistic diagram is here
http://s295.beta.photobucket.com/user/reinhardtjh/media/DataCenter/Network_…
It depends on where in your network you want to put your VAXen. In your diagram, are your VAXen plugged in to the "Local LAN network" ? If so, put your virtual router in this network, and give it a fixed IP address for that subnet. Your virtual router will act as a "router on a stick" - meaning it's got one physical interface. Tunnel traffic will come in via port forwarding from your Vyatta. The virtual router will un-encapsulate the traffic, and route the DECnet traffic back out the same physical interface, where your VAX machines will see it.
Your Vyatta will need to be configured to route GRE traffic (which is the packet type for the tunnel) to your virtual router.
Ian