* NFS root + iptables in 2.6.25
@ 2008-09-19 6:22 Wojciech Kromer
2008-09-19 8:00 ` Richard A Nelson
[not found] ` <48D3451D.1080807-m/c5HOfTwvjVItvQsEIGlw@public.gmane.org>
0 siblings, 2 replies; 7+ messages in thread
From: Wojciech Kromer @ 2008-09-19 6:22 UTC (permalink / raw)
To: linux-kernel
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...
Regards.
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: NFS root + iptables in 2.6.25
2008-09-19 6:22 NFS root + iptables in 2.6.25 Wojciech Kromer
@ 2008-09-19 8:00 ` Richard A Nelson
2008-09-19 9:50 ` Wojciech Kromer
[not found] ` <48D3451D.1080807-m/c5HOfTwvjVItvQsEIGlw@public.gmane.org>
1 sibling, 1 reply; 7+ messages in thread
From: Richard A Nelson @ 2008-09-19 8:00 UTC (permalink / raw)
To: Wojciech Kromer; +Cc: linux-kernel
On Fri, 19 Sep 2008, Wojciech Kromer wrote:
> # modprobe iptable_nat
> nf_conntrack version 0.5.0 (1024 buckets, 4096 max)
> 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...
NFS and iptables definitely takes some care - and there are still holes
- no way to specify ports for all requests...
but this seems odd... you must've had some extant rules that suddenly
seemingly changed behaviour before the modprobe was done
--
Rick Nelson
[In 'Doctor' mode], I spent a good ten minutes telling Emacs what I
thought of it. (The response was, 'Perhaps you could try to be less
abusive.')
-- Matt Welsh
^ permalink raw reply [flat|nested] 7+ messages in thread[parent not found: <48D3451D.1080807-m/c5HOfTwvjVItvQsEIGlw@public.gmane.org>]
* Re: NFS root + iptables in 2.6.25
2008-09-19 6:22 NFS root + iptables in 2.6.25 Wojciech Kromer
2008-09-19 8:00 ` Richard A Nelson
@ 2008-09-19 9:00 ` Andrew Morton
1 sibling, 0 replies; 7+ messages in thread
From: Andrew Morton @ 2008-09-19 9:00 UTC (permalink / raw)
To: Wojciech Kromer; +Cc: linux-kernel, netdev, linux-nfs
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.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: NFS root + iptables in 2.6.25
@ 2008-09-19 9:00 ` Andrew Morton
0 siblings, 0 replies; 7+ messages in thread
From: Andrew Morton @ 2008-09-19 9:00 UTC (permalink / raw)
To: Wojciech Kromer
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA,
netdev-u79uwXL29TY76Z2rM5mHXA, linux-nfs-u79uwXL29TY76Z2rM5mHXA
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: NFS root + iptables in 2.6.25
@ 2008-09-19 9:00 ` Andrew Morton
0 siblings, 0 replies; 7+ messages in thread
From: Andrew Morton @ 2008-09-19 9:00 UTC (permalink / raw)
To: Wojciech Kromer; +Cc: linux-kernel, netdev, linux-nfs
On Fri, 19 Sep 2008 08:22:21 +0200 Wojciech Kromer <wojciech.kromer@dgt.com.pl> 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.
^ permalink raw reply [flat|nested] 7+ messages in thread
* NFS root + iptables in 2.6.25
@ 2008-09-17 8:49 Wojciech Kromer
0 siblings, 0 replies; 7+ messages in thread
From: Wojciech Kromer @ 2008-09-17 8:49 UTC (permalink / raw)
To: netfilter
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...
Regards.
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2008-09-19 9:50 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-09-19 6:22 NFS root + iptables in 2.6.25 Wojciech Kromer
2008-09-19 8:00 ` Richard A Nelson
2008-09-19 9:50 ` Wojciech Kromer
[not found] ` <48D3451D.1080807-m/c5HOfTwvjVItvQsEIGlw@public.gmane.org>
2008-09-19 9:00 ` Andrew Morton
2008-09-19 9:00 ` Andrew Morton
2008-09-19 9:00 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2008-09-17 8:49 Wojciech Kromer
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.