From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Marking packets by mac addr using tc filter u32 match?
Date: Thu, 15 Dec 2005 14:45:42 +0000 [thread overview]
Message-ID: <43A18196.943DA921@iswest.com> (raw)
In-Reply-To: <BAY107-F3151E7335EBD3E34F2786BD5440@phx.gbl>
Kristiadi Himawan wrote:
>
> Hi, i cannot access that page. Could you send it for me :)
http://yesican.chsoft.biz/lartc/arp.html
http://yesican.chsoft.biz/lartc/mac.html
http://yesican.chsoft.biz/lartc/index.html
(duron is my local copy)
--
gypsy
> gypsy wrote:
>
> >Kristiadi Himawan wrote:
> >
> >
> >>So is there a technique to filter this kind of ARP traffic ?
> >>
> >>17:16:53.740978 arp who-has 192.43.165.29 tell 192.43.165.30
> >>17:16:53.752482 arp reply 192.43.165.29 is-at 00:04:c1:b5:bd:f1
> >>17:16:53.812889 arp who-has 192.43.162.194 tell 192.43.162.193
> >>17:16:53.812922 arp reply 192.43.162.194 is-at 00:08:c7:c9:a3:17
> >>
> >>Anyone can help?
> >>
> >>
> >
> >This works for me:
> >http://duron/lartc/arp.html
> >
> >
> >
> >># Example that matches ARP (a big "thank you" to Martin Brown for this!):
> >># the ARP protocol is 2 bytes at -2
> >># the "0806" comes from linux/include/linux/if_ether.h
> >>tc filter add dev $DEV parent 1: protocol ip prio 5 u32 \
> >> match u16 0x0806 0xffff at -2 flowid 1:50
> >>
> >>
> >
> >--
> >gypsy
> >
> >
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2005-12-15 14:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-10 1:07 [LARTC] Marking packets by mac addr using tc filter u32 match? Juan Pizarro
2005-12-10 17:12 ` gypsy
2005-12-11 7:46 ` brick
2005-12-11 8:28 ` Lee Sanders
2005-12-12 10:19 ` Kristiadi Himawan
2005-12-12 14:44 ` gypsy
2005-12-13 2:27 ` Kristiadi Himawan
2005-12-13 10:17 ` Michael Davidson
2005-12-13 10:50 ` Kristiadi Himawan
2005-12-13 15:04 ` gypsy
2005-12-15 14:45 ` gypsy [this message]
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=43A18196.943DA921@iswest.com \
--to=gypsy@iswest.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox