24 Aug
2014
24 Aug
'14
8:52 a.m.
I?ve been meaning to write a response to this thread since it?s an area that fascinates me
and, like a few others, I think I am quite confused on the use of the various tools.
At the moment, the most complex set up consists of the the following:
On a Raspberry Pi I use to keep a screen session open and focused on irssi among other
things, I have tcpser running in an additional screen session.
tcpser is running like so:
tcpser -v 25232 -p 6400 -tSs ?-l 7 ?-i "k0" -s 2400 -N
"/tmp/noanswer.txt" -B "/tmp/busy.txt?
Using the -v command means I?m using VICE. I run VICE emu running in Mac OS X 10.9. VICE
is configured to use RS232 piped out to net cat
"|nc 172.18.1.64 25232? (That IP is the IP o? my Pi.)
In VICE, I use Striketerm 2014 to connect out to BBSs. It works well.
Now, it took me a while and a lot of digging to get this particular setup working and ?
well ? I don?t really understand _why_ it?s working. It?s script-kiddie-ish. I found a
command-line that finally worked. I mean, I can see the pieces and see how that, on a very
superficial level, if the netcat pipe from RS232 in VICE is not working, then StrikeTerm
can?t communicate with tcpser.
But I don?t understand it enough to get other emulators and/or machines to communicate
with tcpser. Why is netcat necessary? Is it possible to get other emulators, like Virtual
][, to speak with tcpser on the Pi? Is it possible to get my IIGS or my IIc Plus to talk
to tcpser?
Or is tcpser even useful for those purposes.
tcpser (and SerialTCP) seem to be bridges between IP and serial communications. tcpser
seems to accept connections from IP and is set up to respond like a Hayes-compatible modem
so that old timey Terminal Programs believe they?re speaking to a modem.
Serial TCP, on the other hand, seems like a client to bridge IP-to-Serial?
I?m willing to do the research and dig more if there are docs for either product. But I
would really like to talk to either Jim, Joe, or anyone in-the-know about how to better
utilize these tools.
On August 19, 2014 at 1:32:16 AM, Jim Brain (brain at jbrain.com) wrote:
On 8/15/2014 9:19 AM, Sean Caron wrote:
I'm fortunate to still have a working GatorBox so
I just use MacIP with the
original, non-OT TCP/IP control panel and I'm off and running. I've got a 4
Meg Mac SE that will run Mosaic or NCSA Telnet, no problems :) My PB 180c
can even run SSH! NuBus machines and the Quadras connect directly in via
Ethernet, of course.
I know the Gatorboxes (or FastPaths) are very hard to find these days but a
friend of mine has had some success using one of the little cheapie Asante
Localtalk-to-Ethernet printer bridges just for the physical layer, then a
Cisco with an appropriate IOS image (supporting Appletalk) for everything
else. He's used this config to "successfully" run MacIP on (within the
bounds of available client software, LOL) and netboot a IIGS.
Best,
Sean
On Wed, Aug 13, 2014 at 6:55 PM, Joe Cassara <joecassara at mac.com> wrote:
> Hi Retro fans,
>
> I have a cache of retro computers I wanted to grant access to the
> internet. As we all know, utilities exist to open and send TCP sockets to a
> serial port (Jim Brain's TCPSer is awesome), but getting them to work right
> on a Mac can be challenging. So, I wrote my own:
>
> http://cassarasoftware.com/serialtcp-for-mac/
>
> It's rather bare bones at the moment, but gets the job done. I hope it
> helps everyone looking to get their old stuff online!
>
> ? Joe
>
Joe,
is there a way to plumb SerialTCP's front end to tcpser, or make a
library of the tcpser code?
I'm happy to take suggestions on making it work better on the Mac, but I
think you're front end is the best way to go.
I need to rewire the codebase, so I am open to suggestions.
Jim
--
Jim Brain
brain at jbrain.com
www.jbrain.com
Cheers,
m