All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Wildgoose <lists@wildgooses.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Using Token Bucket Filter to simulate a low bandwidth
Date: Thu, 01 Jul 2004 10:54:50 +0000	[thread overview]
Message-ID: <40E3ED7A.4080707@wildgooses.com> (raw)
In-Reply-To: <200407011054.15481.n.howden@eris.qinetiq.com>

Nick Howden wrote:

>Hello, 
>
>I am attempting to use the LARTC traffic control to simulate a radio link that 
>has variable bandwidth and availability. The basic bandwidth could be as low 
>as 500 bits/sec but will generally be about 4000 bits/sec. If the simulated 
>radio link is unavailable (zero bandwidth) then packets should be queued 
>until a link is re-established. 
>  
>

Yeah, I think you are going to find it hard to simulate equivalent 
latency as well?

I seem to remember a kernel module for slowing down a link for testing?  
Can't remember the details, but I saw it in my 2.6 kernel somewhere.  
Perhaps check the docs on that.

For my own custom apps I simulated a satellite link simply by writing a 
small proxy program for my particular protocol (in perl and again in 
VB).  It queued packets and released them after a set time period at a 
set rate.  If you are only testing a simple app then this is another way 
to go

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

  reply	other threads:[~2004-07-01 10:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-01  9:54 [LARTC] Using Token Bucket Filter to simulate a low bandwidth radio link Nick Howden
2004-07-01 10:54 ` Ed Wildgoose [this message]
2004-07-01 11:08 ` [LARTC] Using Token Bucket Filter to simulate a low bandwidth Catalin BOIE
2004-07-01 11:26 ` [LARTC] Using Token Bucket Filter to simulate a low bandwidth radio hclfm

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=40E3ED7A.4080707@wildgooses.com \
    --to=lists@wildgooses.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.