|
|
 |  |
Re: Telnet to BSDI still not workingFrom: Shawn Hogan Date: Tuesday, July 21, 1998
Time: 11:32:11 amBill Warner wrote:
>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...
Well, I have the source code to a commercial-grade telnet client that
DOES work properly with BSDI... so I'll see what I can figure out with
that first.
>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.
Agreed... I'll be the first to admit that I have no clue what I'm doing
when it comes to low-level networking programming... And this is my first
attempt at writing any sort of TCP/IP application. So... I'll be the
first to say that the problem is probably not with BSDI. :-) I'm just
trying to figure out what parameter that BSDI doesn't like enough to make
it drop the session in mid-session. {shrug}
Well I'm going to play with it a little more today, and if I really can't
figure it out, I might put it on the shelf for awhile so I can get some
other stuff done, and just let people know about the tset workaround.
But I'll keep plugging away at it for now.
It's just very frustrating for me... Not that it doesn't work, but
because I don't know the telnet protocol inside-out and backwards like I
do databases and some other things. :-)
>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.
At least I know there is some sort of workaround until I get this
negotiation thing working right on BSDI machines. (There is actually one
company that is telnetting into a FreeBSD machine, and then opening a
telnet session from that shell to their BSDI box... ugly but it worked I
guess.) hehe
- Shawn
-------------------------------
Shawn D. Hogan
President, Data Point Solutions
http://www.data-point.com
(619) 452-3696
ICQ: 8319647
|

Return to Digital Point Solutions' Home Page |