netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Meelis Roos <mroos@linux.ee>
Cc: netdev@vger.kernel.org
Subject: Re: iptables broken on ppc (ptrace too?) (2.6.17-rc3)
Date: Mon, 15 May 2006 20:41:21 +0200	[thread overview]
Message-ID: <4468CB51.4060707@trash.net> (raw)
In-Reply-To: <Pine.SOC.4.61.0605152028420.9077@math.ut.ee>

Meelis Roos wrote:
>>> Iptables seems to be broken on ppc for me. Kernel 2.6.17-rc3 (currently
>>> compiling rc4+git). 32-bit ppc, ARCH=ppc with PReP target. Iptables
>>> userland binary is from the latest Debian unstable (1.3.3-2).
>>>
>>> The symptoms: iptables usually just tells Invalid Argument on any
>>> modification attempt. I'm trying to set up a simple one-rule NAT for
>>> test:
>>> iptables -t nat -A POSTROUTING -s 172.30.0.0/24 -j SNAT --to 10.0.0.1
>>> and it usually fails but has succeeded 2 times (I now have 2 rules of
>>> this kind and they seem to just wotk once set up). Trying to delete the
>>> second rule (either by replacing -A with -D or using just -D 2) gives
>>> the same error.
>>
>>
>>
>> This should already be fixed in -rc4.
> 
> 
> Unfortunately it was still there with yesterdays rc4+git.


I may have misinterpreted your report - are you running a 32bit or 64bit
kernel?

  reply	other threads:[~2006-05-15 18:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-14 15:31 iptables broken on ppc (ptrace too?) (2.6.17-rc3) Meelis Roos
2006-05-14 17:15 ` Patrick McHardy
2006-05-15 17:29   ` Meelis Roos
2006-05-15 18:41     ` Patrick McHardy [this message]
2006-05-15 19:28       ` Meelis Roos
2006-05-15 19:36         ` Patrick McHardy
2006-05-15 20:07           ` Meelis Roos
2006-05-24  9:20           ` Meelis Roos

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=4468CB51.4060707@trash.net \
    --to=kaber@trash.net \
    --cc=mroos@linux.ee \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).