(if someone can reply to this so g00r00 will see it, I'd appreciate it)

g00r00 --

I'm trying to figure out a couple things RE: NetRunner:

1 - Any time my server sends a NAWS (IAC DO NAWS), NR responds with WONT.
2 - Since #1 fails, ENiG falls back to a 'bansi.txt' style "report screen size"
(ESC[255n). NR responds to this query with 1,1 which I'd expect from a ESC[6n (as the cursor is indeed at 1,1 at the time). bansi.txt: shorturl.at/qxFNQ

Any ideas? I've played around with various ordering/etc., and have not gotten a
NAWS to anything but a WONT in response.

RE: NetRunner SSH: Overall this seems to work very well SSH-wise, but a couple oddities:
1 - TERM (via PTY info) is reported as "xterm" vs "ansi" which Telnet mode sends.
2 - Term size is reported as 80x48

Thanks!









--- ENiGMA 1/2 v0.0.9-alpha (linux; x64; 10.13.0)
* Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)

On 30 Dec 2018, NuSkooler pondered and said...

(if someone can reply to this so g00r00 will see it, I'd appreciate it)

g00r00 --

I'm trying to figure out a couple things RE: NetRunner:

1 - Any time my server sends a NAWS (IAC DO NAWS), NR responds with WONT. 2 - Since #1 fails, ENiG falls back to a 'bansi.txt' style "report
screen size" (ESC[255n). NR responds to this query with 1,1 which I'd expect from a ESC[6n (as the cursor is indeed at 1,1 at the time). bansi.txt: shorturl.at/qxFNQ

Any ideas? I've played around with various ordering/etc., and have not gotten a NAWS to anything but a WONT in response.

RE: NetRunner SSH: Overall this seems to work very well SSH-wise, but a couple oddities:
1 - TERM (via PTY info) is reported as "xterm" vs "ansi" which Telnet
mode sends.
2 - Term size is reported as 80x48

Thanks!

Reply :)


ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ ÄÄÄÄ Eùavon@bbs.nz ÄÄÄÄÄÄ Wùbbs.nz ÄÄÄ ÄÄÄÄ Kùkeybase.io/avon ÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

--- Mystic BBS v1.12 A42 2018/12/28 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)