All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Ebner <he@fli4l.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Can I Classify Non-IP Traffic?
Date: Fri, 03 Jan 2003 03:00:21 +0000	[thread overview]
Message-ID: <marc-lartc-104156288917857@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104152616513416@msgid-missing>

hi martin,

Martin A. Brown wrote:
> Seems like he needs a "protocol generic" (or better yet for him, "protocol
> ipx"), which would allow him to count byte offsets in the manner of u32.
> 
> I know of no such tool.

i just quote what julian wrote some time ago, seems as if it would 
possible what griff wants to do:

--snip--

> 	Hello,
> 
> On Sun, 22 Dec 2002, Nickola Kolev wrote:
> 
> 
>>>> > I need to classified the traffic by looking at the packet destination
>>>> > and source MAC address. Can anyone here suggest ways to do this.
>>>> >
>>>> > I have read through the HOWTO documentation, from there I know that
>>>> > U32 filter can only filter out IP or higher layer. May I know why U32
>>>> > filter did not support datalink layer (MAC address)? Is it that when
> 
> 
> 	This is a lie.
> 
> 
>>>> > packet entering TC, the datalink layer no longer there? Are there any
>>>> > filter which can filter the MAC address?
> 
> 
> 	You can filter with U32 by src/dst MAC on ingress and
> by dst MAC on egress. On egress the src MAC is replaced with
> new one and there is no good reason to apply U32 filters for sender's
> MAC.
> 
> 
>>>> > Before this, I have successfully implement QoS through source and
>>>> > destination IP address using CBQ. Here I would like to thanks LARTC
>>>> > for the help.
>>>> >
>>
>>>
>>> Yes, you can do this, but using fw marking, not u32 classifier. Just
> 
> 
> 	Why not, just use negative offsets with U32 to access
> the 14-byte eth frame header before the IP header:
> 
> Decimal Ofs	Description
> -----------------------------------
> -14:		DST MAC, 6 bytes
> -8:		SRC MAC, 6 bytes
> -2:		Eth PROTO, 2 bytes, eg. ETH_P_IP
> 0:		Protocol header (IP Header)
> 
> 
>>> search through the various
>>> netfilter extensions - you really can do miracles with them :))
>>>
>>> E-gards,
>>> Nickola
> 
> 
> Regards
> 
> --
> Julian Anastasov <ja@ssi.bg>

--snap--

regards,
   hannes

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

  parent reply	other threads:[~2003-01-03  3:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-02 16:40 [LARTC] Can I Classify Non-IP Traffic? Griff@BP3Web
2003-01-02 17:05 ` Ivo De Decker
2003-01-02 19:41 ` Jose Luis Domingo Lopez
2003-01-02 19:51 ` Martin A. Brown
2003-01-03  3:00 ` Hannes Ebner [this message]
2003-01-03  5:36 ` Martin A. Brown
2003-01-03 21:23 ` 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-104156288917857@msgid-missing \
    --to=he@fli4l.de \
    --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.