Linux NFS development
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Wojciech Kromer
	<wojciech.kromer-m/c5HOfTwvjVItvQsEIGlw@public.gmane.org>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	linux-nfs@vger.kernel.org
Subject: Re: NFS root + iptables in 2.6.25
Date: Fri, 19 Sep 2008 02:00:57 -0700	[thread overview]
Message-ID: <20080919020057.f2f256fe.akpm@linux-foundation.org> (raw)
In-Reply-To: <48D3451D.1080807-m/c5HOfTwvjVItvQsEIGlw@public.gmane.org>

On Fri, 19 Sep 2008 08:22:21 +0200 Wojciech Kromer <wojciech.kromer-m/c5HOfTwvjVItvQsEIGlw@public.gmane.org> wrote:

> Hi.
> 
> I'm using nfs root filesystem for developing.
> On 2.6.23 everything works fine, but on 2.6.25 loading any iptables
> module causes problems:
> 
> 
> # modprobe iptable_nat
> nf_conntrack version 0.5.0 (1024 buckets, 4096 max)
> nfs: RPC call returned error 1
> nfs: RPC call returned error 1
> nfs: RPC call returned error 1
> nfs: RPC call returned error 1
> nfs: RPC call returned error 1
> nfs: RPC call returned error 1
> 
> 
> Probably iptables changed it's default behavior from "allow all" to
> "deny all" at startup.
> Is there any way to change it back?
> I can't change anything after loading any iptable module, because all
> programs on filesystem are not accessible after loading...
> 
> 

(cc's added)

(googles "nfs: RPC call returned error 1")

hm, there has been a dribble of reports going back several years, but
nothing conclusive afaict.


           reply	other threads:[~2008-09-19  9:01 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <48D3451D.1080807-m/c5HOfTwvjVItvQsEIGlw@public.gmane.org>]

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=20080919020057.f2f256fe.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=wojciech.kromer-m/c5HOfTwvjVItvQsEIGlw@public.gmane.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