Search Again: Re: Telnet to BSDI still not working From: Bill Warner Date: Tuesday, July 21, 1998 Time: 11:00:00 am At 11:00 PM 7/20/98 -0700, Shawn Hogan wrote: >Does anyone know if there is anything that can capture any data that my >computer SENDS? (I want to try to capture what a commercial telnet >program is sending during the negotiation.) I already have the means to >capture the incoming (obvisouly). Shawn, Don't know about on your side, but you can use tcpdump on the BSDI side to see everything. >Actually... I know quite a few UNIX based systems offer the source code >to most of the components. Anyone know if BSDI offers the source to it's >telnet daemon? Yes, as a BSDI source licensee I have source to the entire system, with a few small exceptions. Please e-mail me privately if you would still like to see the telnetd source for debugging purposes. Also, the BSDI telnetd has only minor changes from the distribution available from <ftp://ftp.cray.com:src/telnet>. You may also want to contact BSDI directly, <support@bsdi.com>. They may be willing to assist you, and since their engineers know the system better than anyone that may speed things up. But, before wasting time on any of that, please see below... >All I know is that BSDI is really starting to irritate me if nothing >else. :-) IME, BSDI's networking code is quite good, and about as standard compliant as you will find. In fact, the base telnet system that BSDI uses is maintained by Dave Borman who wrote many of those telnet RFCs on your desk. In short, unless you can show a real bug in BSDI's code, I think the burden is on the client to interoperate properly. In fact, it now seems likely that problem people had connecting to BSDI systems had nothing to do with telnet in the first place. My testing confirms that, as reported by someone else, your *OLD* telnet program works just fine against my BSDI system (3.1) as long as the user handles "tset" properly. A new telnet client is not needed. By default, BSDI shell accounts invoke tset out of .login to set the terminal type. This may result in the user being prompted to enter the correct terminal type. This has *nothing* to do with telnet. The telnet session is fully established by the time this prompt comes up. The solution is fairly simple: a) remove the "tset" statements from .login entirely; or b) change the "tset" statements in .login so that they don't prompt; or c) anticipate the prompt and set the response in the Optigold telnet preferences. --Bill

Messages In This Thread: Telnet to BSDI still not working by Serge Pluess on Jul 20, 1998 at 3:13:26 pm Re: Telnet to BSDI still not working by Shawn Hogan on Jul 20, 1998 at 4:12:32 pm Re: Telnet to BSDI still not working by Graeme Easton on Jul 20, 1998 at 6:04:46 pm Re: Telnet to BSDI still not working by Graeme Easton on Jul 20, 1998 at 6:45:11 pm Re: Telnet to BSDI still not working by Shawn Hogan on Jul 20, 1998 at 7:15:29 pm Re: Telnet to BSDI still not working by Graeme Easton on Jul 20, 1998 at 8:15:25 pm Re: Telnet to BSDI still not working by Graeme Easton on Jul 20, 1998 at 8:31:12 pm Re: Telnet to BSDI still not working by Shawn Hogan on Jul 20, 1998 at 8:39:32 pm Re: Telnet to BSDI still not working by Serge Pluess on Jul 20, 1998 at 10:27:22 pm Re: Telnet to BSDI still not working by Shawn Hogan on Jul 20, 1998 at 11:07:39 pm Re: Telnet to BSDI still not working by Graeme Easton on Jul 21, 1998 at 4:52:00 am Re: Telnet to BSDI still not working by Bill Warner on Jul 21, 1998 at 11:00:00 am Re: Telnet to BSDI still not working by Shawn Hogan on Jul 21, 1998 at 11:32:11 am Re: Telnet to BSDI still not working by Bill Warner on Jul 21, 1998 at 12:55:47 pm Re: Telnet to BSDI still not working by Shawn Hogan on Jul 21, 1998 at 1:12:14 pm Re: Telnet to BSDI still not working by Serge Pluess on Jul 21, 1998 at 1:49:10 pm Re: Telnet to BSDI still not working by Shawn Hogan on Jul 21, 1998 at 2:09:51 pm Re: Telnet to BSDI still not working by Jesse Trucks on Jul 21, 1998 at 2:30:23 pm Re: Telnet to BSDI still not working by Jesse Trucks on Jul 21, 1998 at 2:40:36 pm