From: Damion de Soto <damion@snapgear.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] how do you rate limit routable traffic without rate limiting
Date: Tue, 02 Mar 2004 02:59:32 +0000 [thread overview]
Message-ID: <4043F894.6010602@snapgear.com> (raw)
In-Reply-To: <B6356CFC1E307B4285591A5C9883C1520FF9C0@xch-nw-12.nw.nos.boeing.com>
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?
> 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
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Damion de Soto - Software Engineer email: damion@snapgear.com
SnapGear - A CyberGuard Company --- ph: +61 7 3435 2809
| Custom Embedded Solutions fax: +61 7 3891 3630
| and Security Appliances web: http://www.snapgear.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--- Free Embedded Linux Distro at http://www.snapgear.org ---
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-03-02 2:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 2:29 [LARTC] how do you rate limit routable traffic without rate limiting LAN protocols like arps and igm D'Annunzio, Michael A
2004-03-02 2:59 ` Damion de Soto [this message]
2004-03-02 5:48 ` [LARTC] how do you rate limit routable traffic without rate limiting LAN protocols like arps and D'Annunzio, Michael A
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=4043F894.6010602@snapgear.com \
--to=damion@snapgear.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.