* [A] SLIP Question: UDP works but TCP doesn't (SLS 1.0.3)

* [A] SLIP Question: UDP works but TCP doesn't (SLS 1.0.3)

Post by Luc Cluitma » Sat, 14 Aug 1993 18:49:58



A week ago I posted a question on getting SLIP working. I got an answer. I
also got a lot of questions like 'Yeah, I've got the same problem. Can you
send me any answers you get...'. This and the fact that my rmailfile got
completely screwed up this morning (and I lost the adresses of the people
requesting an answer) is the reason I post here. (I hope c.o.l.admin is the
best group to post to. Where is c.o.l.networking? :-))

Original question (abreviated):

Quote:>I recently installed LINUX on my 486 machine. Last weekend I tried to get SLIP
>working. It works only half: I can get UDP connections but I cannot get TCP
>connections!

>So 'ping' and some tools using UDP that I wrote myself work great, but the
>more usefull tools like telnet, ftp, and remote X-connections block after
>connecting.  For example, FTP gets to the point where it tells me 'connected
>to bla.foo.bar.timbuktu' and then is as responsive as a dodo.

 <stuff deleted about kernel pl11 and SLS 1.0.3-out-of-the-box>


Quote:> I'll lay you any odds that it's SLIP header compression. 99pl11 added
> header compression (CSLIP). So yourassociates are not using CSLIP and
> you are. If you are talking to a SLIP server which doesn't do CSLIP,
> only UDP datagrams will get through (they never get their headers
> compressed). The fix is to go to linux/net/inet/slip.c

> In sl_encaps, there is a line beginning

>   len = slhc_compress(...
> Comment out this line and you will stop sending CSLIP packets. You don't
> need to alter the code for receiving CSLIP, though you can if you want.
> To do this, go to the routine sl_bump. There's an if(1) around a big
> block of code for receiving CSLIP. Change it to if(0).

It works for me!

Notice also that you should set your 'mtu' not too high. I use 256. Otherwise
you may get effects like: 'I can get the first few Kbytes and then the link
blocks'.


--

 - DARK IN HERE, ISN'T IT?
(Signature still under construction... -For over four years- Be very patient.)

 
 
 

* [A] SLIP Question: UDP works but TCP doesn't (SLS 1.0.3)

Post by Joe Batt » Sun, 15 Aug 1993 10:10:53



question:

Quote:>>I recently installed LINUX on my 486 machine. Last weekend I tried to get SLIP
>>working. It works only half: I can get UDP connections but I cannot get TCP
>>connections!
answer:
>> I'll lay you any odds that it's SLIP header compression. 99pl11 added
>> header compression (CSLIP). So yourassociates are not using CSLIP and
>> you are. If you are talking to a SLIP server which doesn't do CSLIP,
>> only UDP datagrams will get through (they never get their headers
>> compressed). The fix is to go to linux/net/inet/slip.c

Anyway,
        I have had 'similar' problems recently. Using pl11 with CSLIP configed,
I can use telnet, ftp, and other tcp functions. But, I could not use NFS. This
was a big problem for me. Experimentation and recompilation showed me that with
CSLIP off ( just using SLIP ) the amount of error in each packet decreased
significantly, yet, there was still some error. I believe this error is
associated with the calculation of packet lenghts.
        But, using pl10 kernels, or, using a pl10 client and pl11 server, I can
use NFS. But, without CSLIP on both ends, I can't use tcp, only udp.

Has anyone else noticed this problem? As soon as I find a fix, I'll post.

regards,

Joe Battle


 
 
 

1. * [Q] SLIP Question: UDP works but TCP doesn't (SLS 1.0.3)

Hi linux-world,

I recently installed LINUX on my 486 machine. Last weekend I tried to get SLIP
working. It works only half: I can get UDP connections but I cannot get TCP
connections!

So 'ping' and some tools using UDP that I wrote myself work great, but the
more usefull tools like telnet, ftp, and remote X-connections block after
connecting.  For example, FTP gets to the point where it tells me 'connected
to bla.foo.bar.timbuktu' and then is as responsive as a dodo.

Some other people in our group also have a LINUX box and can use SLIP without
problem. The main difference between their system and mine is that they are
using LINUX kernel pl10. One of them tried using pl11 and got the same
troubles as I have now. Some bug in pl11?

The software I use is out-of-the-box SLS 1.0.3. It struck me that in the
rc.net file that was installed calls to the ethernet device were made, though
I do not have an ethernet card. Does SLS simply assume that anybody who would
like to use IP must have an ethernetcard?

More system information:
486DX-33, 16M RAM, 150M SCSI partion for LINUX, boot via floppy (no LILO), no
parallel ports, no ethernetcard, 2 serial ports (COM2: with a 16550A connected
to modem), LINUX pl11 and other SLS 1.0.3 stuff.

Luc.
--

 - DARK IN HERE, ISN'T IT?
(Signature still under construction... -For over four years- Be very patient.)

2. Help! kernel(1.2.9) compiling errors

3. TCP works, UDP doesn't on a stand alone box

4. Random error with SunAda

5. TCP works but UDP, ICMP doesn't

6. Initio UltraWide SCSI adapters?

7. ipchains/TCP/UDP, Why should I open UDP ports so that my TCP ports can work?

8. HELP!!! The requested URL /cgi-bin/test-cgi was not found on this server.

9. Man doesn't work or need some work from SLS release !!!

10. PPP connection works well ,while SLIP connection doesn't work,why and how?

11. Re. bffcreate -X doesn't work Re: bffcreate -X Doesn't Work

12. LaTeX on SLS 1.03 doesn't work

13. xauth doesn't work properly (SLS .99/p12)