All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Dirk Morris <dmorris@metavize.com>
Cc: Patrick McHardy <kaber@trash.net>, netfilter-devel@lists.netfilter.org
Subject: Re: -m physdev iptables: Invalid Argument
Date: Sat, 25 Oct 2003 11:21:17 +0200	[thread overview]
Message-ID: <20031025092117.GA17255@alpha.home.local> (raw)
In-Reply-To: <3F99CB83.1020405@metavize.com>

On Fri, Oct 24, 2003 at 06:01:55PM -0700, Dirk Morris wrote:
> ~/iptables-1.2.9rc1 # ./iptables 
> --version                                                         
> iptables v1.2.9rc1
> ~/iptables-1.2.9rc1 # uname 
> -a                                                                     
> Linux timmy 2.6.0-test8 #2 Wed Oct 22 15:14:09 PDT 2003 i686 GNU/Linux
> 
> I don't know what else to try at this point.
> 
> ~/iptables-1.2.9rc1 # sudo ./iptables -t nat -A PREROUTING -m physdev 
> --physdev-in eth0 -j REJECT
> iptables: Invalid argument
> ~/iptables-1.2.9rc1 # sudo ./iptables -t nat -A PREROUTING -j REJECT -m 
> physdev --physdev-in eth0
> iptables: Invalid argument

Just out of curiosity, are you sure it's not the REJECT which causes the
invalid argument ?

could you try :
 - iptables -t nat -A PREROUTING -m physdev --physdev-in eth0 -j DROP
 - iptables -t nat -A PREROUTING -j REJECT

and check which one returns an error ?

Was your iptables-1.2.9rc1 compiled with 2.6.0test8 headers or with 2.4
headers ? it might make a difference.

Regards,
Willy

  reply	other threads:[~2003-10-25  9:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-24 18:13 -m physdev iptables: Invalid Argument Dirk Morris
2003-10-24 23:41 ` Patrick McHardy
2003-10-25  0:02   ` Dirk Morris
2003-10-25  0:12     ` Patrick McHardy
2003-10-25  0:26       ` Dirk Morris
2003-10-25  0:40         ` Patrick McHardy
2003-10-25  1:01           ` Dirk Morris
2003-10-25  9:21             ` Willy Tarreau [this message]
2003-10-25  9:38               ` Bart De Schuymer
2003-10-25 18:12                 ` dmorris

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=20031025092117.GA17255@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=dmorris@metavize.com \
    --cc=kaber@trash.net \
    --cc=netfilter-devel@lists.netfilter.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.