All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB and ARP
Date: Fri, 10 Jan 2003 14:58:36 +0000	[thread overview]
Message-ID: <marc-lartc-104221095516897@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104221019215811@msgid-missing>

Eric,

We recently had a discussion here about filtering non-IP traffic.  See my
attempt here:

  http://mailman.ds9a.nl/pipermail/lartc/2003q1/006656.html

And Julian's follow-up post which closed the thread:

  http://mailman.ds9a.nl/pipermail/lartc/2003q1/006663.html

You should be able to select with something like this:

  U32="tc filter add dev $DEV parent 1:0 protocol ip u32"
  $U32 match u16 0x0806 0xFFFF at -2

where 0x0806 identifies the ethernet frame as an ARP packet, per
$LINUX_SOURCE/include/linux/if_ether.h:

#define ETH_P_ARP       0x0806          /* Address Resolution packet    */

Good luck,

-Martin

On Fri, 10 Jan 2003, Eric Leblond wrote:

 : Hi,
 :
 : I discover recently that the arp traffic is managed like any other flow.
 : So you get hang after a moment if you don't use a default class.
 :
 : Is the any means to avoid this ? Not to have a default class is a way to
 : filter traffic ...
 :
 : One would be to managed to class ARP request with tc but I don't know if
 : it is possible.
 :
 : Thanks in advance,
 :

-- 
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2003-01-10 14:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-10 14:48 [LARTC] HTB and ARP Eric Leblond
2003-01-10 14:58 ` Martin A. Brown [this message]
2003-01-14 10:45 ` Eric Leblond
2003-01-14 23:51 ` Julian Anastasov

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=marc-lartc-104221095516897@msgid-missing \
    --to=mabrown-lartc@securepipe.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.