All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Clewett <B.Clewett@roadrunner.uk.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Problems at end of slow satelite link
Date: Mon, 10 Mar 2003 11:00:18 +0000	[thread overview]
Message-ID: <marc-lartc-104729406117157@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104696880831202@msgid-missing>

Stef Coene wrote:
> I think it's best you create a htb setup with different classes.  One of the 
> classes needs a higher priority so the packets in that classes are send 
> first.  Next you need to put the ssh/telnet/syn/ack packets in that classes.  
> All needed information can be found in the LARTC howto.  And you can also 
> find more info on www.docum.org.

This is Hierarchical Token Bucket, explained in section 9.4.5 of the 
HOWTO document?

I was rather hoping you were going to surgest something else, as this is 
not in my kernel... :)

I will however check out the documentation in some more detail.  There 
are a few unresolved questions I have on this pleasent protocol.

Like I notice it claims to scale up to the available bandwidth in 
proporsion to the allocated bandwidth.  I need to know how it calculates 
this bandwidth, as our link shows all the properties of the available 
bandwidth being proporsional to 1/S noise.  Ie, unpredictable and 
un-averagable.

I would like to know also whether HTB scales down, if bandwidth becomes 
throtted by our unpredictable pipe.  And in either case, whether it's 
possible to have a protected channel, like an admin channel, which 
doen't scale up or down with the rest, staying at, say, 16kbit...

All of which I will now try and find out.  And then attempt to get it 
into my kernels at either end. :)

Ben

The biggest mistory of my link-from-hell is the ping.  This shows either 
a latency of 800ms, or 1.5 seconds, or up to 30 seconds when the line 
goes on-hold for a while.  About once every two minutes.  Yet Telnet/SSH 
consistently give latency far far more than this, of about 10 to 60 
seconds consistetly.

If anybody can surgest a reason for this, I think this is likelly to be 
at the heart of any fix I can find...

Regards again...


> 
> Stef
> 


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

  parent reply	other threads:[~2003-03-10 11:00 UTC|newest]

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