Re: Re: LARTC Digest, Vol 34, Issue 12

Linux Advanced Routing and Traffic Control

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"m.a.t.e.o" wrote:
>      #######
>      for the MAC address: M0M1M2M3M4M5
> 
>      tc filter add dev eth1 parent 1: protocol ip prio 5 u32
>      match u16 0x0800
>      0xffff at -2 match u16 0x4455 0xffff at -4 match u32
>      0x00112233 0xffffffff
>      at -8 flowid 1:40
> 
>      #######

Have you tried "protocol all" rather than "protocol ip"?  I tested
M0M1M2M3M4M5 (a long time ago) and it did work for eth1 and imq0.

I guess that when the interface it was used on "saw" the MAC specified
by it then I got a match.  It did not work when the machine was too far
away (in # hops), probably because then the MAC is no longer "visible".

In short, M0M1M2M3M4M5 matched any computer on my internal LAN and the
gateway of my ISP but nothing else.
--
gypsy
_______________________________________________
LARTC mailing list
LARTC@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

[Index of Archives]     [LARTC Home Page]     [Netfilter]     [Netfilter Development]     [Network Development]     [Bugtraq]     [GCC Help]     [Yosemite News]     [Linux Kernel]     [Fedora Users]
  Powered by Linux