All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Bart De Schuymer <bdschuym@pandora.be>
Cc: Ben Gamsa <ben@somanetworks.com>, netfilter-devel@vger.kernel.org
Subject: Re: arptables issue with user-defined chains and -j RETURN
Date: Mon, 16 Jun 2008 09:28:49 +0200	[thread overview]
Message-ID: <48561631.4040807@trash.net> (raw)
In-Reply-To: <1213466540.2945.13.camel@localhost.localdomain>

Bart De Schuymer wrote:
> Op wo, 11-06-2008 te 08:14 +0200, schreef Patrick McHardy:
>> I think the error is in userspace, it shouldn't define the value
>> dependant on a non-fixed value. If the kernel did this as well
>> before the intoduction of x_tables (which defined ARPT_RETURN
>> to XT_RETURN), compatibility was already broken by the introduction
>> of NF_STOP a long time ago. So I think the correct fix is to
>> resync the arp_tables userspace header files with the kernel.
> 
> Things compile fine from CVS using the KERNEL_DIR directive with your
> favorite kernel source.
> I'm having more trouble than I like getting things to compile by just
> also including x_tables.h in the local arptables directory (__be16 isn't
> defined). I guess my /usr/include/linux directory isn't up-to-date. Is
> there any directive about this? How does iptables cope with this?


For iptables we ended up adding the types.h file to the
iptables source. I think arptables should do the same
to support compilation on old systems.

      reply	other threads:[~2008-06-16  7:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 16:40 arptables issue with user-defined chains and -j RETURN Ben Gamsa
2008-06-11  6:14 ` Patrick McHardy
2008-06-14 18:02   ` Bart De Schuymer
2008-06-16  7:28     ` Patrick McHardy [this message]

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=48561631.4040807@trash.net \
    --to=kaber@trash.net \
    --cc=bdschuym@pandora.be \
    --cc=ben@somanetworks.com \
    --cc=netfilter-devel@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.