Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Problems matching by mac address
Date: Wed, 12 Apr 2006 21:10:32 +0000	[thread overview]
Message-ID: <443D6CC8.3090301@dsl.pipex.com> (raw)
In-Reply-To: <48DC429CB053B64EAD91BDD1DE106A1152C021@es1.corp.commspeed.net>

Adam M. Towarnyckyj wrote:
> Sorry for bumping this one, but I wanted to know if anyone else had any
> ideas as well. I'm a bit baffled as to why this isn't working. Thanks.

Hmm this is a strange one - I tried both ip and mac version of your 
script (on non-bridged eth) and both "work" ie the traffic ends up in 
htb 12:10 and gets shaped. I tested with proftpd as sender - it's going 
to be important to test both with the same app that sets tos bits for 
prio - probably also worth putting a bfifo on 1:3 just for stats as 
default prio is three band.

Now what I don't get is in both cases if I do tc -s filter ls parent 
12:0 I don't get any matches, so would have expected them to have gone 
through htb as default - unshaped not 12:10 - strange.

Will have to think/try different kernel and tc versions.

Did you do both tests with the same tos bit setting sender app?

Alexey's point about filtering to 12:0 is because normally if you set up 
a tree structure for filters you need a filter rule on root to pass 
traffic down to child(ren) - prios automatic filtering seems to do it - 
but not as I expected.

Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2006-04-12 21:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-04 17:54 [LARTC] Problems matching by mac address Adam M. Towarnyckyj
2006-04-04 22:15 ` Alexey Toptygin
2006-04-07 21:06 ` Adam M. Towarnyckyj
2006-04-11 17:39 ` Adam M. Towarnyckyj
2006-04-12 21:10 ` Andy Furniss [this message]
2006-04-12 23:08 ` Adam M. Towarnyckyj
2006-04-15 16:14 ` Andy Furniss

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=443D6CC8.3090301@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox