Hey Alexey, Thanks for the input. I think that lack of two F's was a typo on my part but I tried it anyways and it still does not work. I also added the ceil to it with no luck. I'm a bit confused on what you meant by not having any rules to classify from root down to 12:. Can you elaborate or show me an example? As I stated before, this is pretty much the exact setup I used when I filtered by destination IP. The only thing I'm changing now is the actual filter command. Everything else has been in place for a while. Thanks. Adam -----Original Message----- From: Alexey Toptygin [mailto:alexeyt@xxxxxxxxxxxxx] Sent: Tuesday, April 04, 2006 3:15 PM To: Adam M. Towarnyckyj Cc: lartc@xxxxxxxxxxxxxxx Subject: Re: Problems matching by mac address On Tue, 4 Apr 2006, Adam M. Towarnyckyj wrote: > I recently read on a prior post as well as the FAQ that > packets can be limited by mac address using the u32 filter. I attempted > this and, while all the commands went through with no errors, it is not > limiting at all. I'm attempting to limit all IP traffic to a specific > destination mac address (00:12:3f:05:43:7f). Here is a quick rundown of > the commands I've used: Not sure that this will help, but > tc qdisc add dev eth1 parent 1:2 handle 12: htb > tc class add dev eth1 parent 12: classid 12:10 htb rate 128kbit no ceil? > tc filter add dev eth1 protocol ip parent 12: prio 5 u32 match u16 > 0x0800 0xFFFF at -2 match u32 0x3f05437f 0xFFFFFF at -12 match u16 > 0x0012 0xFFFF at -14 flowid 12:10 Shouldn't that be "match u32 0x3f05437f 0xFFFFFFFF at -12" (2 more Fs) Also, what you sent didn't have any rules to classify from root down to 12: so the above filter won't be consulted... Alexey _______________________________________________ LARTC mailing list LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
