I connect through metrocast.net and have no such delays. I use speakup and ssh. The command I normally use is ssh-agent ssh -l jdashiel shellworld.net. I don't experience latency/delay over here. For that reason I figure speakup is cleared and two places to look at are the local computer and AT&T's u-verse network. What were the results of the last clamav scan and was that up-to-date and when was that done? When was the system with speakup last updated? If you're clear on those counts, then and only then would I approach u-verse and complain about latency/delay. On Mon, 24 Jun 2013, Karen Lewellen wrote: > Hi Jason, > As I understand it, Larry's question has nothing to do with TELNET so to > speak. > He is only using it, instead of sh TELNET, because of a speakup issue that > no one has addressed. > This equally has nothing to do with shellworld. I use ssh TELNET many times > a day to come here, am doing so right now to write this email. However I am > doing this in pure dos, have no delays, and am not, like Larry using speakup. > > In an effort to try and get him a more direct answer, is his lag issue due to > speakup or something else? > Karen > > On Mon, 24 Jun 2013, Jason White wrote: > > > Hart Larry <blinux-list@xxxxxxxxxx> wrote: > > > Ok, I login to Shellworld from a Debian system with a 12MB AT&T Uverse > > > connection. Over the last couple of years I had to switch from ssh to > > > telnet, > > > as for some reason, with Speakup, there is some sluggishness while > > > cursoring. > > > But now even telnet has this behavior, while logging in another Linux > > > machine > > > which has much better network conductivity, I have an easier time. > > > editing > > > without any lag. On Shellworld I can hit backspace a number of times and > > > the > > > beeping is spiraticly sluggish. > > > So, first I wonder if there are either other telnet options I can try, or > > > would > > > their be another protocol which may react faster? > > > > Almost everybody has moved away from telnet for security reasons. Basically, > > if you're using telnet, everything you type, including passwords, is sent > > over > > the network as plain text that crackers can intercept. So my advice is that > > you shouldn't use it. > > > > Regarding your network problem, try pinging the remote hosts that you're > > connecting to. The network latency could be your problem, in which case > > there's very little you can do about it unless it's an issue with your > > internet service provider's network. Some providers are better than others > > in > > this area. Mine, for example, maintains a very reliable network with good > > latency because their customers use a lot of VoIP, which is highly sensitive > > to timing issues. > > > > > > _______________________________________________ > > Blinux-list mailing list > > Blinux-list@xxxxxxxxxx > > https://www.redhat.com/mailman/listinfo/blinux-list > > > > > > _______________________________________________ > Blinux-list mailing list > Blinux-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/blinux-list > > --------------------------------------------------------------------------- jude <jdashiel@xxxxxxxxxxxxxx> About to block another web browser version? Ask yourself what Tim Berners-lee would do. _______________________________________________ Blinux-list mailing list Blinux-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/blinux-list