Date: Fri, 23 Feb 1996 09:47:12 -0600 (CST) From: "Matthew N. Dodd" <winter@jurai.net> To: Stephen Hovey <shovey@buffnet.net> Cc: freebsd-questions@freebsd.org Subject: Re: Telnet Slowdown (fwd) Message-ID: <Pine.BSF.3.91.960223091336.17857A-100000@sasami> In-Reply-To: <Pine.BSD.3.91.960223091206.6141G-100000@buffnet7.buffnet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 23 Feb 1996, Stephen Hovey wrote: > No - how snotty of you. I didnt say trumpet was a standards measure. > Im an ISP, I have to deal with users wanting to connect, so they gotta > be able to, and most of them use trumpet. Yes indeed, but thats what I get for not sleeping. Since you seem to be of the mind that "if it doesn't work, go with something else", I suggest that you tell your customers to get a commercial TCP/IP stack. After all, its only shareware, and can't possiably be as good as "real" software. :) Now, since we seem to place some importance this free software thing, lets look at what we have so far. You. Your FreeBSD machines are causing/the cause of some problems on your network. - You said you use: SCO, Linux, and FreeBSD. - You use Annex terminal servers. - A significant number of your users are using Trumpet Winsock. Me. My FreeBSD machines are a source of great delight and niftiness on my network. - I have all FreeBSD machines (Ok, a bastard child Linux box too) - I'm using Livingston PM2e terminal servers. - Far too many of my users are using Trumpet Winsock. You observed a connectivity problem on dialup and network hosts alike. The dialup host problem may have been the same as the network host problem. You observed that smaller machines were aflicted the least, and speculated that the problem might be resource related. Now then... I'm not able to match your SCO boxes, but other than terminal servers we're doing the same thing. It might be the terminal server or it might be the (l)users (sneaky little buggers) or a combination of both. Someone suggested turning off the TCP extensions, which would be my first guess as well. Next, you should check for serial problems on the Trumpet side, and make sure your using the newest version of Trumpet. If you're using 2.0 (that may be the newest) then there is a problem with using an MTU of 1500 (check the Livingston-Portmaster mailing lists for more info on this on. Archives are on Livingstons www page). If that doesn't give you anything, try tcpdumping the dialup and see whats going on. If you can't see anything obvious, email me a disk log of a session. This leads you to the network host problem. Tcpdump would be a good starting point. Find out if the problems are reproducable, and if so under what conditions. > No - Its not in a ring - i just call it 'the ring' out of habit. Im not > that stupid. :) You chopped my smiley. I know, it was in jest, I don't think your stupid (forgive my knee jerk wit in responce to SCO advocacy). The people I was talking about (the ones what wired a 10Base2 as a ring) were from an IBM shop. I heard the network admin spent all day trying to figure out that one. :) Have a good one. | Matthew N. Dodd | winter@jurai.net | http://www.jurai.net/~winter | | Technical Manager | mdodd@intersurf.net | http://www.intersurf.net | | InterSurf Online | "Welcome to the net Sir, would you like a handbasket?"|
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.960223091336.17857A-100000>