From: Andrew Morton <akpm@linux-foundation.org>
To: Haavard Skinnemoen <hskinnemoen@atmel.com>
Cc: Ben Nizette <bn@niasdigital.com>,
netfilter-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, Andrew Morgan <morgan@kernel.org>
Subject: Re: BUG: 2.6.25-rc1: iptables postrouting setup causes oops
Date: Wed, 13 Feb 2008 01:22:31 -0800 [thread overview]
Message-ID: <20080213012231.46865608.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080213101024.39347322@dhcp-252-066.norway.atmel.com>
On Wed, 13 Feb 2008 10:10:24 +0100 Haavard Skinnemoen <hskinnemoen@atmel.com> wrote:
> On Wed, 13 Feb 2008 00:48:29 -0800
> Andrew Morton <akpm@linux-foundation.org> wrote:
>
> > On Tue, 12 Feb 2008 22:46:01 +1100 Ben Nizette <bn@niasdigital.com> wrote:
> >
> > >
> > > On an AVR32, root over NFS, config attached, running (from a startup
> > > script):
> > >
> > > iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
> > >
> > > Results in (dmesg extract including a bit of context for good measure):
> > > -------------8<----------------
> > > VFS: Mounted root (nfs filesystem).
> > > Freeing init memory: 72K (90000000 - 90012000)
> > > eth0: no IPv6 routers present
> > > warning: `dnsmasq' uses 32-bit capabilities (legacy support in use)
>
> Hmm. What does that mean? What size do capabilities normally have?
My near-namesake put than in, but I immediately forgot what it means?
next prev parent reply other threads:[~2008-02-13 9:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 11:46 BUG: 2.6.25-rc1: iptables postrouting setup causes oops Ben Nizette
2008-02-13 8:48 ` Andrew Morton
2008-02-13 9:10 ` Haavard Skinnemoen
2008-02-13 9:22 ` Andrew Morton [this message]
2008-02-13 16:42 ` Andrew G. Morgan
2008-02-13 18:19 ` Haavard Skinnemoen
2008-02-13 11:29 ` Haavard Skinnemoen
2008-02-13 22:41 ` Ben Nizette
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=20080213012231.46865608.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bn@niasdigital.com \
--cc=hskinnemoen@atmel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=morgan@kernel.org \
--cc=netdev@vger.kernel.org \
--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.