Opened 8 months ago

Closed 8 months ago

#18887 closed bug (not reproducible)

Connections to ANSI BBS systems are unreliable even in Terminal

Reported by: WildKeccak Owned by: axeld
Priority: normal Milestone: R1/beta5
Component: Network & Internet/TCP Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

Other systems, like QPuTTY and PuTTY are not workarounds, and are at least as bad.

hrev57704

HP Stream 11 2023 edition

Attachments (1)

syslog (444.3 KB ) - added by WildKeccak 8 months ago.
A system log

Download all attachments as: .zip

Change History (17)

by WildKeccak, 8 months ago

Attachment: syslog added

A system log

comment:1 by waddlesplash, 8 months ago

If PuTTY is also affected then clearly this is not a problem with Terminal. But you will have to be specific about what the problem exactly is.

comment:2 by WildKeccak, 8 months ago

It stops responding to keystrokes on ANSI BBS systems. I wish I could be more specific. Konsole is maybe better, but you then need to make sure it's 80 characters wide and 24 or 25 characters high. I was able to have a bit more success with Konsole.

comment:3 by WildKeccak, 8 months ago

There is never a disconnection message, just suddenly it stops.

comment:4 by waddlesplash, 8 months ago

What does "a bit more success" in Konsole mean?

How are you connected to these servers (i.e. what protocol)? Does beta4 behave any differently? Are any of them public?

comment:5 by WildKeccak, 8 months ago

I connect using Telnet and SSH. I don't notice any reliability differences between the two.

A workaround is to connect to my OpenBSD mosh server, and then have the OpenBSD box connect to the telnet or SSH server. Sometimes you have to relax the algorithms and ciphers.

I should check beta4!

Konsole may or may not perform better than terminal. It's more beautiful -- it might be the halo effect talking.

These are all registration required sites.

comment:6 by waddlesplash, 8 months ago

I guess the most likely possibility is that the TCP connection just stalled.

comment:7 by waddlesplash, 8 months ago

Component: - GeneralNetwork & Internet/TCP
Owner: changed from nobody to axeld

comment:8 by WildKeccak, 8 months ago

I've been checking beta4, no sign of this problem anywhere.

comment:9 by WildKeccak, 8 months ago

After about 20 minutes of trying, I don't see the problem with ssh on beta4

comment:10 by waddlesplash, 8 months ago

Milestone: UnscheduledR1/beta5
Platform: x86-64All

comment:11 by pulkomandy, 8 months ago

a tcpdump capture of a stalled session might be useful?

comment:12 by WildKeccak, 8 months ago

Knowing that I get my connection through a TP-Link UE300 adapter connected to a MicroTik RouterBoard that I configured according to

https://www.reddit.com/r/mikrotik/comments/b8wloq/how_do_i_connect_my_map_2nd_to_the_hotel_wifi_and/?rdt=46513

might be helpful too . . .

comment:13 by WildKeccak, 8 months ago

I'll probably try tcpdump tomorrow.

comment:14 by WildKeccak, 8 months ago

Works on a fresh install of hrev704 or hrev57707 as far as I can tell.

comment:15 by WildKeccak, 8 months ago

Can't reproduce

comment:16 by pulkomandy, 8 months ago

Resolution: not reproducible
Status: newclosed

Closing as not reproducible for now then. Let us know if you find a way to reproduce the problem reliably.

Note: See TracTickets for help on using tickets.