Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Nishit Shah <nsshah.82@gmail.com>,
	Richard Horton <arimus.uk@googlemail.com>,
	Netfilter Developer Mailing List
	<netfilter-devel@vger.kernel.org>,
	netfilter@vger.kernel.org, Bart De Schuymer <bdschuym@pandora.be>,
	Jay Fenlason <fenlason@redhat.com>,
	mt@suse.de, jskala@redhat.com
Subject: Re: arptables ruleset not working when compiling on  fedora6,7,8/centos 5/redhat 5
Date: Wed, 01 Jul 2009 13:18:53 +0200	[thread overview]
Message-ID: <4A4B461D.5050407@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.00.0907011302390.3504@fbirervta.pbzchgretzou.qr>

Jan Engelhardt wrote:
> On Wednesday 2009-07-01 11:56, Patrick McHardy wrote:
>> Nishit Shah wrote:
>>> On Mon, Jun 29, 2009 at 9:48 PM, Nishit Shah<nsshah.82@gmail.com> wrote:
>>>> -/usr/include/linux/netfilter.h:#define NF_MAX_VERDICT NF_REPEAT
>>>> +/usr/include/linux/netfilter.h:#define NF_MAX_VERDICT NF_STOP
>>>>
>>> I am adding the patch for the same.
>> Please send this to Bart (CCed), who is maintaining arptables.
> 
> There is also a rogue arptables_jf clone by some RedHat person —
> no homepage, no point of download except distro .src.rpms —
> and used by Fedora and openSUSE.
> 
> Ccing the relevant persons responsible for that clone, which I am also 
> hereby accusing of failing to submit their stuff upstream causing 
> unnecessary extra hurdles for users.

Thanks for pointing this out. Jay, please elaborate on why you've
chosen to fork this instead of working with upstream.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-07-01 11:18 UTC|newest]

Thread overview: 20+ 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:21 ` Richard Horton
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:44         ` Patrick McHardy
2009-06-29 16:18           ` Nishit Shah
2009-06-30  8:08             ` Nishit Shah
2009-07-01  9:56               ` Patrick McHardy
2009-07-01 11:09                 ` Jan Engelhardt
2009-07-01 11:18                   ` Patrick McHardy [this message]
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-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

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=4A4B461D.5050407@trash.net \
    --to=kaber@trash.net \
    --cc=arimus.uk@googlemail.com \
    --cc=bdschuym@pandora.be \
    --cc=fenlason@redhat.com \
    --cc=jengelh@medozas.de \
    --cc=jskala@redhat.com \
    --cc=mt@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox