All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Nishit Shah <nsshah.82@gmail.com>
Cc: jengelh@medozas.de, Richard Horton <arimus.uk@googlemail.com>,
	netfilter-devel@vger.kernel.org, netfilter@vger.kernel.org,
	Bart De Schuymer <bdschuym@pandora.be>
Subject: Re: arptables ruleset not working when compiling on 	fedora6,7,8/centos 5/redhat 5
Date: Wed, 01 Jul 2009 11:56:20 +0200	[thread overview]
Message-ID: <4A4B32C4.8050800@trash.net> (raw)
In-Reply-To: <b2d58cb80906300108q2ee5a060gf8013a88560d8820@mail.gmail.com>

Nishit Shah wrote:
> On Mon, Jun 29, 2009 at 9:48 PM, Nishit Shah<nsshah.82@gmail.com> wrote:
>> On Mon, Jun 29, 2009 at 9:14 PM, Patrick McHardy<kaber@trash.net> wrote:
>>> Ah, I remember, we had some breakage with of the ARPT codes with the
>>> introduction of x_tables in 2.6.16. Please try to figure out the
>>> difference of those values between working and non-working state
>>> (ARPT_CONTINUE, ARPT_RETURN etc.)
>>>
>> Bingo !!!
>>
>> It is due to the value of ARPT_RETURN. ARPT_RETURN defined in
>> arptables-v0.0.3-3 is
>>
>> ./include/linux/netfilter_arp/arp_tables.h:#define ARPT_RETURN
>> (-NF_MAX_VERDICT - 1)
>>
>> and value of NF_MAX_VERDICT is different on machine running with gcc
>> 2.96/glibc 2.2.4 and above all machines.
>>
>> value of NF_MAX_VERDICT on machine running gcc 2.96 and glibc 2.2.4,
>>
>>        /usr/include/linux/netfilter.h:#define NF_MAX_VERDICT NF_REPEAT
>>
>> and same file on all above machines,
>>
>>        /usr/include/linux/netfilter.h:#define NF_MAX_VERDICT NF_STOP
>>
>> Thanks Patrick :)
>>
>> Rgds,
>> Nishit Shah.
>>
> 
> I am adding the patch for the same.

Please send this to Bart (CCed), who is maintaining arptables.


  reply	other threads:[~2009-07-01  9:56 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-29 14:12 arptables ruleset not working when compiling on fedora6,7,8/centos 5/redhat 5 Nishit Shah
2009-06-29 14:12 ` Nishit Shah
2009-06-29 14:21 ` Richard Horton
2009-06-29 14:21   ` Richard Horton
2009-06-29 14:51   ` Nishit Shah
2009-06-29 14:51     ` Nishit Shah
2009-06-29 14:58     ` Patrick McHardy
2009-06-29 15:18       ` Nishit Shah
2009-06-29 15:18         ` Nishit Shah
2009-06-29 15:44         ` Patrick McHardy
2009-06-29 16:18           ` Nishit Shah
2009-06-29 16:18             ` Nishit Shah
2009-06-30  8:08             ` Nishit Shah
2009-06-30  8:08               ` Nishit Shah
2009-07-01  9:56               ` Patrick McHardy [this message]
2009-07-01 11:09                 ` Jan Engelhardt
2009-07-01 11:18                   ` Patrick McHardy
2009-07-02 16:58                     ` Bart De Schuymer
2009-07-05 12:59                 ` Bart De Schuymer
2009-07-05 15:59                   ` Jan Engelhardt
2009-07-06 19:54                     ` Bart De Schuymer
2009-07-06 20:01                       ` Jan Engelhardt
2009-07-08  6:57                         ` Nishit Shah
2009-07-08  6:57                           ` Nishit Shah
2009-07-09 17:50                           ` Bart De Schuymer
2009-06-29 18:47       ` Jan Engelhardt
  -- strict thread matches above, loose matches on Subject: below --
2009-07-01 11:02 bdschuym@pandora.be
2009-07-01 11:02 ` bdschuym@pandora.be

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=4A4B32C4.8050800@trash.net \
    --to=kaber@trash.net \
    --cc=arimus.uk@googlemail.com \
    --cc=bdschuym@pandora.be \
    --cc=jengelh@medozas.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=netfilter@vger.kernel.org \
    --cc=nsshah.82@gmail.com \
    /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.