All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Habets thomas@habets.pp.se
To: lartc@vger.kernel.org
Subject: SV: [LARTC] Bandwidth limiting
Date: Fri, 24 Nov 2000 14:53:16 +0000	[thread overview]
Message-ID: <marc-lartc-98373938216972@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938216960@msgid-missing>

<PRE>On Thu, 23 Nov 2000, you wrote:
&gt;<i> I don't see the problem. You can specify the limit on the outgoing
</I>&gt;<i> interfaces, depending on the incoming interface. Using firewall marks is
</I>&gt;<i> quite easy.
</I>
I bet it is, since iptables is easy. Haven't learned to use fwmarks yet 
though.

&gt;<i>Have you tried the example setup from the HOWTO?
</I>
Yes, and after *another* long starring and testing pass I'm pretty sure I got 
it to work with the sfq or u32 or something, not really sure what did what 
though, but it'll come to me.

Why can't it just be like:
iptables -t shaper -A OUTPUT -s 1.2.3.0/24 --maxspeed\x128Kbit -j SHAPE

---------
typedef struct me_s {
  char name[]      = { &quot;Thomas Habets&quot; };
  char email[]     = { &quot;<A HREF="mailto:thomas@habets.pp.se">thomas@habets.pp.se</A>&quot; };
  char kernel[]    = { &quot;Linux 2.2&quot; };
  char *pgpKey[]   = { &quot;finger -m <A HREF="mailto:thompa@darkface.pp.se">thompa@darkface.pp.se</A>&quot; };
  char pgpfinger[] = { &quot;6517 2898 6AED EA2C 1015  DCF0 8E53 B69F 524B B541&quot; };
  char coolcmd[]   = { &quot;echo '. ./_&amp;. ./_'&gt;_;. ./_&quot; };
} me_t;


</PRE>

  parent reply	other threads:[~2000-11-24 14:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-22 14:25 SV: [LARTC] Bandwidth limiting Daniel
2000-11-22 16:58 ` Daniel
2000-11-23  9:12 ` Daniel
2000-11-23 16:05 ` Thomas
2000-11-23 16:10 ` Thomas
2000-11-23 16:21 ` Wingtung.Leung
2000-11-24 14:53 ` Thomas [this message]
2000-11-24 21:37 ` Wingtung.Leung

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-98373938216972@msgid-missing \
    --to=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.