From mboxrd@z Thu Jan 1 00:00:00 1970 From: gypsy Date: Thu, 13 Dec 2007 02:42:35 +0000 Subject: Re: [LARTC] Re: LARTC Digest, Vol 34, Issue 12 Message-Id: <47609C1B.AEBF7EEA@iswest.com> List-Id: References: <823158cf0712120830i63861d5fyc7c4836bd6fe2bf0@mail.gmail.com> In-Reply-To: <823158cf0712120830i63861d5fyc7c4836bd6fe2bf0@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org "m.a.t.e.o" wrote: > ####### > for the MAC address: M0M1M2M3M4M5 > > tc filter add dev eth1 parent 1: protocol ip prio 5 u32 > match u16 0x0800 > 0xffff at -2 match u16 0x4455 0xffff at -4 match u32 > 0x00112233 0xffffffff > at -8 flowid 1:40 > > ####### Have you tried "protocol all" rather than "protocol ip"? I tested M0M1M2M3M4M5 (a long time ago) and it did work for eth1 and imq0. I guess that when the interface it was used on "saw" the MAC specified by it then I got a match. It did not work when the machine was too far away (in # hops), probably because then the MAC is no longer "visible". In short, M0M1M2M3M4M5 matched any computer on my internal LAN and the gateway of my ISP but nothing else. -- gypsy _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc