All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Clewett <B.Clewett@roadrunner.uk.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Problems at end of slow satelite link
Date: Thu, 06 Mar 2003 16:33:15 +0000	[thread overview]
Message-ID: <marc-lartc-104696880831202@msgid-missing> (raw)

Newbe hoping this is the correct area to post.

I've been reading the LARTC HOWTO, but at 110 pages, I am finding it 
difficult to know where to start.  I hope you may be able to surgest a 
starting place to a couple of problems I am having.

I am dealing with the slow end of a satelite ADSL.  This is 'lumpy', 
with huge latency (1 to 30 sec), 10% dropped packets, huge but 
intermittent bursts of packets, and generally a pile of poo.   The 
supplier (BT) is of course no help, so we have to live with what we have.

I have tried limiting the bandwidth with a Tocket Bucket Filter with 
almost no effect.

What I think I need is to agressivelly schedule SSH and Telnet before 
all other TCP connections.  Others I don't care about.  There are I see 
many scheduling options, can any member surgest how I might atchive this?

The second problem I have is that my connection keeps terminating 
(Telnet, SSH) with 'Connection closed by foreign host', with no message 
in logs.  Always during streaming of data.  Some part of the kernel is 
getting tired of waiting for the other end to respond, or possible a 
buffer overflow?  Again, if any member may surgest how this can be 
countered with extream predudice, I would be extreamly greatful.

Regards, Ben Clewett.


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2003-03-06 16:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-06 16:33 Ben Clewett [this message]
2003-03-08 19:42 ` [LARTC] Problems at end of slow satelite link Stef Coene
2003-03-10 11:00 ` Ben Clewett
2003-03-10 17:57 ` Stef Coene

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-104696880831202@msgid-missing \
    --to=b.clewett@roadrunner.uk.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.