From: Maurice Volaski <mvolaski@aecom.yu.edu>
To: Harald Welte <laforge@netfilter.org>
Cc: netfilter@lists.netfilter.org, linux-kernel@vger.kernel.org
Subject: Re: iptables is complaining with bogus unknown error 18446744073709551615
Date: Thu, 27 Apr 2006 11:41:40 -0400 [thread overview]
Message-ID: <a06230904c07687df0a33@[129.98.90.227]> (raw)
In-Reply-To: <20060427135119.GB5177@rama>
>On Wed, Apr 26, 2006 at 09:12:38PM -0400, Maurice Volaski wrote:
>> Automatic kernel module loading! That is an option and it's off by
>> default. When it's off, attempts to load kernel modules are ignored
>> internally, and that's why iptables was failing. It tried to load
>> xt_tcpudp, but was ignored by the kernel.
>
>What do you mean by "it's an option" and "is off by default". I would
>claim that any major linux distribution that I've seen in the last ten
>years has support for module auto loading (enabled by default).
>
Distribution vendors are free to change it to whatever they want, I
guess, but it's OFF by default in the official kernel (.config).
--
Maurice Volaski, mvolaski@aecom.yu.edu
Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University
next prev parent reply other threads:[~2006-04-27 15:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200604210738.k3L7cBGO010103@mailgw.aecom.yu.edu>
2006-04-27 1:12 ` Maurice Volaski
2006-04-27 13:51 ` Harald Welte
2006-04-27 15:41 ` Maurice Volaski [this message]
2006-04-27 19:24 ` CONFIG_KMOD in x86_64/defconfig (was Re: iptables is complaining with bogus unknown error 18446744073709551615) Harald Welte
2006-04-27 20:00 ` Maurice Volaski
2006-04-27 20:01 ` Arjan van de Ven
2006-04-21 6:21 iptables is complaining with bogus unknown error 18446744073709551615 Maurice Volaski
2006-04-21 11:15 ` Harald Welte
2006-04-21 14:22 ` Maurice Volaski
[not found] ` <a06230913c06e96f75f32@129.98.90.227>
2006-04-21 18:26 ` Nick Warne
2006-04-22 0:05 ` Alessandro Suardi
2006-04-22 11:59 ` Nick Warne
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='a06230904c07687df0a33@[129.98.90.227]' \
--to=mvolaski@aecom.yu.edu \
--cc=laforge@netfilter.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter@lists.netfilter.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
all inboxes | Powered by JetHome®