packet errors in PPP cause TCP blocking

packet errors in PPP cause TCP blocking

Post by Penio Pene » Tue, 20 Jan 1998 04:00:00



I'm using a PPP connection to the external world and I'm having problems
with TPC throughput, for example an ftp download.

The symptoms are the following.  I monitor both the modem lights and the
hash mark progress.

Initially everything goes fine -- the receive light is on constantly and
the hash advances about 4K/sec, which is what the 56K modem gives.

At some point the hash marks stop advancing, and shortly after the receive
light stops.  At this point I can check with ifconfig that there has been
one packet error on the interface.  

After a while there is some sporadic activity on the lights, a whole slew
of hash marks appears at once, and the transmission resumes normally.

This process is repeated at regular intervals, so the effective throughput
is much less than the peak -- about 2.6 K/s.

What I believe is happening is that the dropped packet is not ACK-ed at
the TCP level, and the remote host stop sending further packets until this
one is retransmitted.

What is the relevant parameter to tweak, so that the error is encountered
and the packet -- retransmitted _before_ the other packets stop flowing?

Also, what could cause the fairly regular dropping of the packets?

--

 
 
 

packet errors in PPP cause TCP blocking

Post by Martin Kiehn » Fri, 23 Jan 1998 04:00:00


I have exactly the same problem. If you start ppp with kernel debugging
messages turned on, you will probably see a frame checksum error each time
the connection pauses. The only thing I was able to find about it was the
guess that a modem doesn't work properly. But the same connection works fine
with W95!

No one in comp.protocols.ppp or comp.dcom.modems had an answer to my question
so far. So if you finally can come up with something to prevent these *
stalls, I would REALLY appreciate it if you could let me know.

Regards,

Martin

--


 
 
 

packet errors in PPP cause TCP blocking

Post by Penio Pene » Fri, 23 Jan 1998 04:00:00



> I have exactly the same problem. If you start ppp with kernel debugging
> messages turned on, you will probably see a frame checksum error each time
> the connection pauses. The only thing I was able to find about it was the
> guess that a modem doesn't work properly. But the same connection works fine
> with W95!

I haven't tried it with Win95, so I don't know whether my problem is the
same, but it seems like it.

Quote:> No one in comp.protocols.ppp or comp.dcom.modems had an answer to my question
> so far.

Well, I guess that the blame is not with PPP, but in the TCP code.

OK, we dropped the packet and we have to retransmit it.  But this should
only add an extra packet, not stop the flow for two seconds.

My guess is that the timeout for retransmit is set too high, and the number
of un-ACK-ed packets to low.  I have a suspicion that there is a parameter
for this to be tweaked, but which?

Quote:> So if you finally can come up with something to prevent these *
> stalls, I would REALLY appreciate it if you could let me know.

Definitely,

--

 
 
 

1. sendmail+TLS causing unwarranted TCP RST packets

[crossposted to comp.mail.sendmail and comp.os.linux.networking since
the bug might be in sendmail, the linux tcp stack, ssl, iptables, or
somewhere else ....]

I've managed to discover something fairly disturbing when sending mail
from a linux machine running sendmail: if the connection is encrypted
via TLS, the connection won't close cleanly (with an exchange of FIN
packets) but will terminate abruptly with a RST packet (from the
machine that originated the email).  I have not observed a RST packet
from the originating machine when TLS is _not_ used.

I just tested this with someone to try to figure out what's wrong.
Here was the setup:
  My end is a RHEL 3 box:
     kernel-smp-2.4.21-27.0.2.EL
     sendmail-8.12.11-4.RHEL3.1
  Remote end is a Debian box:
     kernel: 2.6.12-rc2-mm1
     sendmail: 8.13.4
We confirmed that if the RedHat box initiated the message transfer, it
would be the one to issue a RST after the transaction was complete.
Similarly, if the Debian box initiated the transfer, it would issue a
RST.

Mail *is* flowing, but I find it somewhat disturbing that there are RST
packets being thrown about.  My theory of what might be happening is
that the sending sendmail process terminates after sending its final
data (QUIT) to the SSL layer, rather than waiting for any final
response (221 Goodbye).  Since the process is no longer there, the TCP
connection is broken, and a RST gets generated.  That means the bug is
in sendmail, right?  I'd like to get some confirmation about this
reasoning from others before filing a bug report, though, since my
hypothesis is little more than an educated guess.

Cheers,

Damian Menscher
--

-=#| 488 LLP, 1110 W. Green St, Urbana, IL 61801 Ofc:(217)333-0038 |#=-
-=#| 4602 Beckman, VMIL/MS, Imaging Technology Group:(217)244-3074 |#=-

-=#| The above opinions are not necessarily those of my employers. |#=-

2. Quick Proftpd Question

3. 103640-02 fixes jerky mouse cursor caused by blocked TCP connections

4. Booting 1.1.42 kernel..

5. brcfg to block TCP/IP packets over Linux bridge?

6. $ Take 5 minutes to read this and it WILL change your life $

7. LINUX PPP : RX packet errors on direct ppp link

8. IMP on horde: does anyone have "howto" for setting up this webmail?

9. PPP blocking after first out packet

10. blocking sync packets to 205.188.0.0/20 , will block all the icq servers:)

11. ipfw counting blocked packets but not blocking them?

12. TCP/PPP loosing packets

13. How to convert TCP/IP packet to IPX packet and visa-versa ?