The following warnings occurred:
Warning [2] Undefined property: MyLanguage::$archive_pages - Line: 2 - File: printthread.php(287) : eval()'d code PHP 8.1.28 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/printthread.php(287) : eval()'d code 2 errorHandler->error_callback
/printthread.php 287 eval
/printthread.php 117 printthread_multipage



CBMSTUFF FORUM
Making an actual telnet connection=garbled text - Printable Version

+- CBMSTUFF FORUM (https://www.cbmstuff.com/forum)
+-- Forum: CBMSTUFF PRODUCTS (https://www.cbmstuff.com/forum/forumdisplay.php?fid=1)
+--- Forum: WiModem (https://www.cbmstuff.com/forum/forumdisplay.php?fid=75)
+---- Forum: Usage (https://www.cbmstuff.com/forum/forumdisplay.php?fid=77)
+---- Thread: Making an actual telnet connection=garbled text (/showthread.php?tid=365)

Pages: 1 2 3


RE: Making an actual telnet connection=garbled text - captain_zzap - 02-21-2017

Found something else:
http://mud-dev.wikidot.com/telnet:negotiation

Shouldn't it be enough to send IAC 255 and then WONT 252?


RE: Making an actual telnet connection=garbled text - captain_zzap - 02-22-2017

After some more research I found this thread on Lemon64:

http://www.lemon64.com/forum/viewtopic.php?t=40874&postdays=0&postorder=asc&start=0

It's really the negotiation. And it's probably no enough to just send "iac won't". You probably should negotiate in the right way. bummer.
It's probably also the same reason why people can't connect to sdf.org as in this thread:
https://www.cbmstuff.com/forum/showthread.php?tid=360


RE: Making an actual telnet connection=garbled text - captain_zzap - 02-22-2017

Ok, no telnet, but a working serial terminal through socat, a virtual tty, and getty. Yay!
[Image: img_5795.jpg]


RE: Making an actual telnet connection=garbled text - Zeropage - 02-22-2017

Does it work ok for you at 9600 baud?

I find that after a while the text starts getting garbled.

2400 is ok.


RE: Making an actual telnet connection=garbled text - captain_zzap - 02-22-2017

(02-22-2017, 02:17 PM)Zeropage Wrote: Does it work ok for you at 9600 baud?

I find that after a while the text starts getting garbled.

2400 is ok.

I've testet only for a few minutes, the encoding isn't right, and I've seen artifacts from tmux, but the text itself seemed fine at 9600 baud. I have not enabled flow control.


RE: Making an actual telnet connection=garbled text - jbni - 06-20-2017

(02-22-2017, 02:07 PM)captain_zzap Wrote: Ok, no telnet, but a working serial terminal through socat, a virtual tty, and getty. Yay!

Would you mine putting together a quick howto on this? What you did on the server, etc?

I can handle setting up telnetd, but I'm at an utter loss setting up a terminal like this.


RE: Making an actual telnet connection=garbled text - captain_zzap - 06-20-2017

Essentially it's just:
socat pty,link=/dev/ttyV0,raw tcp-l:11313
and then launching a getty on /dev/ttyV0
on Arch Linux with 
systemctl start getty@ttyV0.service

[Image: img_6349.jpg]
[Image: img_6348.jpg]


RE: Making an actual telnet connection=garbled text - admin - 06-20-2017

Yeah, don't forget to enable flow control for 9600 baud with AT&K1, otherwise you will likely have issues.

So, since I knew zero about internet connectivity before the WiModem project, I decided to look into telnet to see what it really is. Apparently, you should be filtering ESCape characters (0xFF) and that is something that I don't do. So, I am looking into that.


RE: Making an actual telnet connection=garbled text - captain_zzap - 06-21-2017

Support for Telnet would be awesome. And useful on the your generic rs232 Adapter too.
Flow control is now enabled. Back in February it wasn't working right. But it does now.


RE: Making an actual telnet connection=garbled text - admin - 10-12-2017

Telnet support has been added!