All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] [PATCH] mark in u32
Date: Thu, 06 Jan 2005 08:53:41 +0000	[thread overview]
Message-ID: <41DCFC95.20207@dsl.pipex.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0501051151270.8614@webhosting.rdsbv.ro>

Stephen Hemminger wrote:
> On Wed, 05 Jan 2005 14:59:44 +0000
> Andy Furniss <andy.furniss@dsl.pipex.com> wrote:
> 
> 
>>Catalin(ux aka Dino) BOIE wrote:
>>
>>>Hello, Stephen, List!
>>>
>>>Attached is the patch for iproute2 to add the possibility to use fwmark 
>>>in u32 filters.
>>>The kernel part was included in 2.6.10.
>>>
>>>Please apply!
>>>Thank you!
>>>
>>>For more info:
>>>- Kernel patch (not needed for 2.6.10): 
>>>http://kernel.umbrella.ro/net/mark_in_u32/net-match-nfmark-in-u32.patch
>>>
>>>- Examples:
>>>http://kernel.umbrella.ro/net/mark_in_u32/examples.txt
>>>
>>>---
>>>Catalin(ux aka Dino) BOIE
>>>catab at deuroconsult.ro
>>>http://kernel.umbrella.ro/
>>
>>That looks handy :-) Do you know why fw mark doesn't work with policers 
>>in 2.6 (assuming it's not just me)
>>
>>To stephen - I may be wrong here but in the readme it says that default 
>>kernel include is /usr/src/linux/include but if I grep for 
>>KERNEL_INCLUDE I see :-
>>
>>./Makefile:KERNEL_INCLUDE:=/usr/include
>>./Makefile:CFLAGS = $(CCOPTS) -I$(KERNEL_INCLUDE) -I../include $(DEFINES)
>>./Makefile:     ./configure $(KERNEL_INCLUDE)
>>./README:KERNEL_INCLUDE should point to correct linux kernel include 
>>directory.
> 
> 
> I changed away from Alexey's old KERNEL_INCLUDE, because it was necessary
> for the package to be able to be compiled without depending on the kernel
> header files. There were cases where new features needed to be compiled on
> old systems where the definition was missing.  Think about building current
> iproute2 util's with 2.4.20 includes.
> 
> The current solution (though less than ideal) was to put stripped down
> version of the routing specific includes into the iproute2 package.
> 

Ahh I see, thanks for the explanation.

Andy.


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

  parent reply	other threads:[~2005-01-06  8:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-05 10:05 [LARTC] [PATCH] mark in u32 Catalin(ux aka Dino) BOIE
2005-01-05 14:59 ` Andy Furniss
2005-01-05 15:10 ` Thomas Graf
2005-01-05 15:25 ` Andy Furniss
2005-01-05 15:52 ` Thomas Graf
2005-01-05 16:40 ` Andy Furniss
2005-01-05 23:44 ` Stephen Hemminger
2005-01-06  8:53 ` Andy Furniss [this message]
2005-01-06  9:00 ` Andy Furniss
2005-01-06  9:50 ` Thomas Graf
2005-01-06 13:27 ` Andy Furniss
2005-01-06 16:45 ` Thomas Graf
2005-01-06 23:23 ` Andy Furniss
2005-01-06 23:25 ` Thomas Graf
2005-01-06 23:35 ` Andy Furniss
2005-01-07  2:45 ` Andy Furniss
2005-01-07 10:29 ` Andy Furniss
2005-01-08  2:34 ` Andy Furniss
2005-01-08  4:14 ` gypsy
2005-01-08  4:58 ` gypsy

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=41DCFC95.20207@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.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.