From: Josip Gracin gracin@tel.fer.hr
To: lartc@vger.kernel.org
Subject: [LARTC] How to mark and queue
Date: Thu, 19 Oct 2000 11:42:29 +0000 [thread overview]
Message-ID: <marc-lartc-98373938216816@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938216813@msgid-missing>
<PRE>Thanks for the reply!
bert hubert (<A HREF="mailto:ahu@ds9a.nl">ahu@ds9a.nl</A>) wrote:
><i> On Thu, Oct 19, 2000 at 10:15:28AM +0200, Josip Gracin wrote:
</I>><i> > I would like to set up a machine to introduce random (but controllable)
</I>><i> > dropping of packets that are being forwarded. I also need to classify the
</I>><i>
</I>><i> Try to make a u32 match on a part of the header that changes a lot. I
</I>
But than I would not be able to control the randomness of drops. I need a
drop policy based on various stochastic functions.
><i> Try asking the netfilter mailinglist.
</I>
Oops, I thought this was a perfect list to ask the question. Sorry, I'll
ask there.
Best regards,
Josip
</PRE>
next prev parent reply other threads:[~2000-10-19 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-19 8:15 [LARTC] How to mark and queue Josip
2000-10-19 11:41 ` bert
2000-10-19 11:42 ` Josip [this message]
2000-10-19 12:06 ` Josip
2000-10-19 12:46 ` bert
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-98373938216816@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.