From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Problems matching by mac address
Date: Sat, 15 Apr 2006 16:14:50 +0000 [thread overview]
Message-ID: <44411BFA.20503@dsl.pipex.com> (raw)
In-Reply-To: <48DC429CB053B64EAD91BDD1DE106A1152C021@es1.corp.commspeed.net>
Adam M. Towarnyckyj wrote:
> Andy,
>
> Thanks for investigating so extensively. However, I'm an idiot and made
> a fundamental mistake in networking that I should have realized in the
> first place. I completely didn't think about the fact that the filter is
> looking at the data link layer of the packet and that this gets changed
> through each device. The test machine is set up behind a router. Also,
> to answer your question, I'm using a download test app on a web server I
> set up, so I'm basically using the same program for testing the
> throughput each time.
>
> Sorry if I wasted anyone's time on this. With me, it's always something
> obvious I missed and usually I don't realize until after I have
> investigated every FAQ, Googled the hell out of the question, and posted
> to a list.
No problem - I don't know how to solve your new problem.
I retried the test on a 2.6.15 with tc 051107 and the counters are OK
now when I tc -s filter ls dev eth0 parent 12:0.
One thing - I always considered the match 0x0800 0xFFFF at -2 to be
redundant if you say protocol ip in the filter - so I ended up using the
following, which I think is a bit easier to read with mac of target
machine 00:C1:26:0F:04:AD.
tc filter add dev eth0 protocol ip parent 12: prio 1 u32 \
match u16 0x00c1 0xffff at -14 \
match u32 0x260f04ad 0xffffffff at -12 \
flowid 12:10
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-04-15 16:14 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
2006-04-12 23:08 ` Adam M. Towarnyckyj
2006-04-15 16:14 ` Andy Furniss [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=44411BFA.20503@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 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.