All of lore.kernel.org
 help / color / mirror / Atom feed
From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB: Filtering flat out not working :(g
Date: Fri, 01 Mar 2002 10:06:31 +0000	[thread overview]
Message-ID: <marc-lartc-101497726602549@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101488556702466@msgid-missing>

On Thu, Feb 28, 2002 at 03:31:02PM +0000, Tim Carr wrote:
> >From: bert hubert <ahu@ds9a.nl>
> >To: EGAL Vincent <egal@ipanematech.com>
> >CC: Tim Carr <cygnusx__1@hotmail.com>, lartc@mailman.ds9a.nl
> >Subject: Re: [LARTC] HTB: Filtering flat out not working :(g
> >
> >Exactly - queueing disciplines and their attached filters come *way* after
> >iptables or ipchains have doen their work.
> >
> >If you need information from before mangling, you should use fwmark to tag
> >packets, and then filter based on that fwmark. How to do this is in the
> >HOWTO.
> 
> As i mentioned in the email, i've already tried this. No, the HOWTO does not 
> tell you how to do QoS with MARKing. It tells you how to MARK the packets, 
> and it tells you how to route the packets, but that's not what I want: I 
> want QoS, not policy-based routing etc. (I'm talking about this specific 
> part of the FAQ: 
> http://www.lartc.org/HOWTO//cvs/2.4routing/output/2.4routing-11.html )

Down below on:
http://www.lartc.org/HOWTO//cvs/2.4routing/output/2.4routing-9.html#ss9.2

On fwmark

    You can mark packets with either ipchains and have that mark survive
routing across interfaces. This is really useful to for example only shape
traffic on eth1 that came in on eth0. Syntax: # tc filter add dev eth1
protocol ip parent 1:0 prio 1 handle 6 fw flowid 1:1 Note that this is not a
u32 match!

    You can place a mark like this:

# iptables -A PREROUTING -t mangle -i eth0 -j MARK --set-mark 6

    The number 6 is arbitrary.

    If you don't want to understand the full tc filter syntax, just use
iptables, and only learn to select on fwmark.


-- 
http://www.PowerDNS.com          Versatile DNS Software & Services
http://www.tk                              the dot in .tk
http://lartc.org           Linux Advanced Routing & Traffic Control HOWTO
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2002-03-01 10:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-28  8:35 [LARTC] HTB: Filtering flat out not working :(g bert hubert
2002-02-28 15:31 ` Tim Carr
2002-03-01  7:50 ` Stef Coene
2002-03-01 10:06 ` bert hubert [this message]

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-101497726602549@msgid-missing \
    --to=ahu@ds9a.nl \
    --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.