Re: [LARTC] Problems matching by mac address
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 0x 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 0x at -14 \ match u32 0x260f04ad 0x at -12 \ flowid 12:10 Andy. ___ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
Re: [LARTC] Problems matching by mac address
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
RE: [LARTC] Problems matching by mac address
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. If anyone has any ideas on how I can accomplish destination mac address filtering through multiple hops, I'd love to hear them. Otherwise, I think I'm going back to the drawing board on this one. Adam Interesting Outlook doesn't recognize Googled as a verb... -Original Message- From: Andy Furniss [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 12, 2006 2:11 PM To: Adam M. Towarnyckyj Cc: lartc@mailman.ds9a.nl Subject: Re: [LARTC] Problems matching by mac address 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
RE: [LARTC] Problems matching by mac address
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. Adam -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adam M. Towarnyckyj Sent: Friday, April 07, 2006 2:06 PM To: lartc@mailman.ds9a.nl Subject: RE: [LARTC] Problems matching by mac address 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:[EMAIL PROTECTED] Sent: Tuesday, April 04, 2006 3:15 PM To: Adam M. Towarnyckyj Cc: lartc@mailman.ds9a.nl Subject: Re: [LARTC] 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 0x at -2 match u32 0x3f05437f 0xFF at -12 match u16 0x0012 0x at -14 flowid 12:10 Shouldn't that be match u32 0x3f05437f 0x 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@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc ___ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
Re: [LARTC] 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 0x at -2 match u32 0x3f05437f 0xFF at -12 match u16 0x0012 0x at -14 flowid 12:10 Shouldn't that be match u32 0x3f05437f 0x 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@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
