From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] xtables-addons : Invalid module format
Date: Fri, 5 Aug 2011 09:53:07 -0400 [thread overview]
Message-ID: <CA+czFiCbZ-7aEU95xXigFHNTkqN19gXnsohVwSMW2F_bDgOVxw@mail.gmail.com> (raw)
In-Reply-To: <CAA2qdGXG1cTXRvOxOG6oYTZeoa+c_XMObbO5BkME8nXEHJkdUg@mail.gmail.com>
On Fri, Aug 5, 2011 at 9:45 AM, Pandu Poluan <pandu@poluan.info> wrote:
> On Fri, Aug 5, 2011 at 20:32, Pandu Poluan <pandu@poluan.info> wrote:
>> On Fri, Aug 5, 2011 at 20:24, Michael Mol <mikemol@gmail.com> wrote:
>>> That sounds like a symbol conflict, such as if you were to try to
>>> insert a module into a kernel, where the kernel already had the code
>>> built-in.
>>>
>>> Check your kernel configuration and ensure that all of the iptables
>>> stuff is built as modules, rather than built-in. Then (I suspect) it
>>> should be a matter of figuring out which module conflicts.
>>>
>>
>> Hmmm... okay, I'll try to build another kernel.
>>
>> There's this whole page of "IPset" in `make menuconfig` that I had
>> naively set to built-in.
>>
>> I'll post updates.
>>
>
> Well, whaddaya know...
>
> I set `CONFIG_IP_SET=m`, rebuild the kernel, and re-emerged
> xtables-addons, and...
>
> It works ! ! !
>
> Thank you so much :-)
>
> (If we ever meet, remind me to treat you to a nice mug o'beer -- or
> your preferred cold drink)
Not necessary. :)
Well, I do hope to be at Dragon*Con this year, so if you're in the area. ;)
--
:wq
prev parent reply other threads:[~2011-08-05 13:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 13:11 [gentoo-user] xtables-addons : Invalid module format Pandu Poluan
2011-08-05 13:24 ` Michael Mol
2011-08-05 13:32 ` Pandu Poluan
2011-08-05 13:45 ` Pandu Poluan
2011-08-05 13:53 ` Michael Mol [this message]
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=CA+czFiCbZ-7aEU95xXigFHNTkqN19gXnsohVwSMW2F_bDgOVxw@mail.gmail.com \
--to=mikemol@gmail.com \
--cc=gentoo-user@lists.gentoo.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