TCPSER Raspberry Pi Amiga 500

[desiv]

Haven't used tcpser yet (or a Pi), so this won't be very helpful I'm afraid, but..

sudo tcpser -d /dev/ttyUSB0 -p23 -s 19200 -l5

Let's check the options:
sudo tcpser - running it as root.
-d /dev/ttyUSB0 - So, running it on the USB port ( Is the Pi's serial port USB0?)
-p23 - listening on port 23 (this is only for devices wanting to talk TO your Amiga "modem" I think).  I wouldn't think this would conflict with your Pi listening on 23 for it's telnet (assuming it is running telnetd and listening on 23).  Maybe, for testing, comment that out and leave it at the default 6400?
-l5 - logging level 5.   Maybe pop it up to max (l7 I think?) to see what happens?

If I try to telnet to the Pi itself or another Linux machine it seems to get stuck at:
2014-03-28 05:49:16:-1243241360:INFO:Parsing nvt command

I think that's just an informational message, so TCPSER doesn't seem to be complaining..

Since it works on Windows I am guessing my Amiga Term settings are OK.  I think the issue is on the Raspberry Pi itself, maybe the telnet settings.  But I am not a Linux expert and I can't figure it out.

One thing I'd do is test telnet on the Pi first.
SSH into the Pi from your windows machine (putty).  Then from your session, type "telnet 127.0.0.1" which should try to connect form the Pi to the Pi on port 23 using telnet.
If that works, your Pi is at least listening on 23.

If not, you're telnet daemon isn't happy.

desiv

[desiv]

Can you install telnet on Windows (I know, it's a bad thing security wise, but just for a test) and try telnetting to a Windows box.
(Depending on your OS, there are different ways to enable telnet on Windows - http://technet.microsoft.com/en-us/library/cc770501(v=ws.10).aspx )

Wonder if we might be having a terminal type issue.
Can you set NComm of JRComm for VT100 or something else, just to see?

Also, for more involved testing, on the Ubuntu or Pi machine, while it's happening, can you run a tcpdump?

Something quick, like "sudo tcpdump port 23" should show your connection attempts from your tcpser session to your machine ..  We'd be looking for, are packets going out?  And, are packets being acknowledged and going back...

desiv
p.s.  Try setting your Amiga terminal program to a 2 color screen, just to make sure it's not a display/font/color issue..

[desiv]

Hmmm..
They are talking to each other.
Now its just, what are they saying.. ;-)

Can you set you flow control to XON/XOFF and see what happens?

Also, in tcpser, there was an option for carrier detect (-I???), maybe try that.
(Doesn't look like it's thinking the carrier isn't there, just figure it's worth a shot..  ;-)

If the telnet BBS stuff works, but the telnet to Linux doesn't, it feels like it doesn't like the terminal type / negotiation..
(Actually, I still wonder if the linux host has a security setting stopping it?)
It's weird because, from a network perspective, there's really no difference between a telnet BBS and telnet to a linux box.  So it feels app..  Something on the Linux telnet daemon..

Can you telnet from your Windows box to the Ubuntu or Pi?
(If you have Windows 7 (and maybe 8?  not sure), i think telnet needs to be added:
http://social.technet.microsoft.com/wiki/contents/articles/910.windows-7-enabling-telnet-client.aspx )

I wonder if it's a security setting on Linux for telnetd..
(i haven't used telnetd in ages..  Only sshd)

desiv

[desiv]

Has no one actually done this for their Amiga, as far as I can tell this is the only realistic method for getting your 1.3 Amiga on the net? I thought more people would have tried this.

I use an external Lantronix box for that, although I didn't try connecting from my Amiga to a Linux box.  Only Telnet BBSes...

If you can transfer some programs to your Amiga, I'd try a better VT100 emulator next..
Maybe something like this:
http://aminet.net/package/comm/term/Vt100
(Note: I'm not sure that app is 1.3 happy.  It supports ARexx, so maybe not.  That was just a quick google search.)

I'll to set mine up if I get a chance this weekend.  I kind of have my A1000 totally open for a floppy emulator project I'm working on.. ;-)

desiv

[desiv]

Modem interface?

I wonder if the Windows tcpser is doing something different then..

For a telnet BBS, you use the  modem interface, or you type something like:
ATDT w.x.y.z
(where w.x.y.z is the IP or DNS name of the remote BBS)
TCPSER should send a RING to the telnet BBS program.  The telnet BBS, when it sees that, should send a CONNECT (and possibly a BAUD RATE) back to your program.
Your program sees the CONNECT and knows it's ONLINE.

TELNETd on a Linux box isn't going to know anything about RING or CONNECT..

Yep, been googling (as I was typing) and it looks like it might be related to IAC negotiation in telnet:
http://www.lemon64.com/forum/viewtopic.php?t=39987&sid=2011a548ba2b0338f3710203f90f7acd

Not sure why it works thru Windows tcpser tho...  It must be doing something different..

If the VT100 program you have lets you connect to a serial port, try that, and then use the ATDT w.x.y.x method to connect..
Not sure if it will recognize it at that stage tho, but maybe..

desiv