[LARTC] how do you rate limit routable traffic without rate limiting LAN protocols like arps and igmp?
I'm rate limiting and prioritizing traffic upstream of a slow wan link using htb, classic wonder shaper type stuff. I'm using the following command for traffic that does not match any of my defined filters: tc qdisc add dev eth0 root handle 1: htb default 50 It appears that local, non-routable traffic like arps and igmp are being snared by this and end-up queued in the lowest priorty queue. I was surprised that non-IP traffic would be effected by IP traffic control. How do I prevent this local, non-routable traffic from being queued? Since it's local, I just want it to go at line rate. I know if I remove the default parameter, traffic not matching any filter is sent over the root queue, but I need to have a defined default. All the literature I've seen only covers tc filters dealing with the protocol IP. I've tried to filter on the arp protocol (I read this works, but not for me), got error messages: I've tried to using u32 matches with negative offsets, but no luck. Sorta relieved that it didn't work, cause it seemed liked a hack. Mike ___ LARTC mailing list / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
RE: [LARTC] how do you rate limit routable traffic without rate limiting LAN protocols like arps and igmp?
Hi Damion, Hi Michael, It appears that local, non-routable traffic like arps and igmp are being snared by this and end-up queued in the lowest priorty queue. I was surprised that non-IP traffic would be effected by IP traffic control. How are you determining this? I restarted the queues to clear the counts and then ping'ed an unused IP address on the local subnet and counted the unanswered arp requests using tcpdump. I then used tc to show the queue counts and saw the respective counts in the default queue. I changed the default queue and perform the test again and saw the count appear in the new default queue. I'm pretty sure the counts in the default queue were arp requests. All the literature I've seen only covers tc filters dealing with the protocol IP. I've tried to filter on the arp protocol (I read this works, but not for me), got error messages: Yes, linux QoS can't shape sub-IP ARP packets. See the thread [LARTC] tc filter protocol arp question from January this year: http://mailman.ds9a.nl/pipermail/lartc/2004q1/thread.html I saw this thread and had the same problem, but I also came across this link: http://www.docum.org/stef.coene/qos/faq/cache/63.html from [EMAIL PROTECTED] It says: Simple, just use protocol arp in your filters. But it wasn't so simple. I'm really having the opposite problem. I'm trying not to shape arps. -- ~~~ Damion de Soto - Software Engineer email: [EMAIL PROTECTED] SnapGear - A CyberGuard Company ---ph: +61 7 3435 2809 | Custom Embedded Solutions fax: +61 7 3891 3630 | and Security Appliancesweb: http://www.snapgear.com ~~~ --- Free Embedded Linux Distro at http://www.snapgear.org --- ___ LARTC mailing list / [EMAIL PROTECTED] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
