All of lore.kernel.org
 help / color / mirror / Atom feed
From: bert hubert ahu@ds9a.nl
To: lartc@vger.kernel.org
Subject: [LARTC] How to mark and queue
Date: Thu, 19 Oct 2000 11:41:02 +0000	[thread overview]
Message-ID: <marc-lartc-98373938216815@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938216813@msgid-missing>

<PRE>On Thu, Oct 19, 2000 at 10:15:28AM +0200, Josip Gracin wrote:
&gt;<i> Hello!
</I>&gt;<i> 
</I>&gt;<i> I would like to set up a machine to introduce random (but controllable)
</I>&gt;<i> dropping of packets that are being forwarded.  I also need to classify the
</I>
Try to make a u32 match on a part of the header that changes a lot. I
suspect the IP packet id would be a good candidate, but you need to make
sure that resends of the same packet do get through. If you match, route to
loopback.

&gt;<i> traffic because I want some traffic shaping.  The obvious solution is to
</I>&gt;<i> QUEUE packets to user level and if they are ACCEPTed, put a MARK
</I>&gt;<i> (--set-mark) on them for classifying.  This would seem logical:
</I>&gt;<i> 
</I>&gt;<i> iptables -A FORWARD -j QUEUE -j MARK
</I>&gt;<i> 
</I>&gt;<i> Of course, it is not possible.  How do I do this than?  That is, how to do
</I>&gt;<i> it without using two identical rules, one with QUEUE action and another
</I>&gt;<i> with MARK action which does not seem to be a nice solution.
</I>
Try asking the netfilter mailinglist.

Regards,

bert hubert

-- 
PowerDNS                     Versatile DNS Services  
Trilab                       The Technology People   
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet


</PRE>

  reply	other threads:[~2000-10-19 11:41 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 [this message]
2000-10-19 11:42 ` Josip
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-98373938216815@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.