Messages in this thread | | | Date | Wed, 27 Mar 1996 12:54:38 +0100 (MET) | From | Jacek Zapala <> | Subject | Re: NCSA telnet doesn't work any more |
| |
On Wed, 27 Mar 1996, Alan Cox wrote:
> > I have already posted this in linux-net, but got no single response. Now > > I have some more data, so I'm posting this once more. > > Ok the reason I ignored it is I bin most reports based on certain stacks because > they are known problem stacks anyway. Notably trumpet v1 and NCSA > > > I have found that linux 1.3.74 and 1.3.77 does not work with NCSA telnet for > > DOS (or rather NCSA telnet doesn't with linux). From NCSA side it looks like > > the conection is open, but nothing (even login's output) arrives. From the > > linux side in.telnetd is launched, but nothing more. > > Someone said something about NCSA having been fixed. I don't know more about > it - maybe ask the NCSA people. Also send them this trace too. If they need > a contact to work out why the two dont talk point them at me. > > > 18:08:12.000000 kakofonix.posnet.com.telnet > 1.2.3.88.11134: . ack 16 win 13125 (ttl 64, id 1700) > > 18:08:12.000000 1.2.3.88.11134 > kakofonix.posnet.com.telnet: . ack 1 win 1024 (ttl 100, id 5) > > Up to here looks ok. Note now that we keep sending the remote machine data > and it is ignoring us after this. That is broken because unless its turned off > it should either be > > a) Sending us an ICMP protocol error if it thinks we are talking garbage > b) Sending a TCP reject if its lost the connection > c) Sending a TCP ack frame for at least every other tcp frame regardless of > whether sequence spaces are right or wrong > > > If you have any ideas or need additional information or testing, feel free > > to write me even at 8 in the morning :-) > > Can you try leaving pc/tcp compatibility off and disabling MTU discovery ? > > Alan
Ok, I will check it in the moment.....
Jacek
| |