From: Saravanan Chanemouganandam <schane@osmozis.com>
To: netfilter@vger.kernel.org
Cc: busybox@busybox.net
Subject: modprobe: cannot parse modules.dep error
Date: Tue, 18 Dec 2007 10:32:16 +0100 [thread overview]
Message-ID: <200712181032.17947.schane@osmozis.com> (raw)
Hi all,
I am running into the following problem when invoking a netfilter iptables
( v1.3.8) and xtables support in the buildroot's busybox (v1.7.2) system. The
netfilter packet configuration and support modules are compiled and built
into the linux-2.6.16 kernel image.
When a 'C++' application code calls the iptables through
sprintf(buff, "%s -t mangle -A PREROUTING %s -j MARK --set-mark 512",
Config.iptables, Config.link[i]);
it throws the modprobe error.
iptables -t mangle -A PREROUTING -d 88.160.215.156 -p icmp -j MARK --set-mark
512
modprobe: cannot parse modules.dep
modprobe: cannot parse modules.dep
iptables -t mangle -A PREROUTING -s 88.160.215.156 -p icmp -j MARK --set-mark
512
modprobe: cannot parse modules.dep
modprobe: cannot parse modules.dep
iptables -t mangle -A PREROUTING -d 88.160.215.156 -p tcp --dport http -j MARK
--set-mark 512
modprobe: cannot parse modules.dep
modprobe: cannot parse modules.dep
Normally it shouldn't do module probing as all the netfilter support symbols
are included in the kernel image. Can anybody tell me why the system throws
the modprobe error though the netfilters supports are built into the kernel
image.?
Thanks
Sara
Osmozis
next reply other threads:[~2007-12-18 9:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 9:32 Saravanan Chanemouganandam [this message]
2007-12-18 11:08 ` modprobe: cannot parse modules.dep error Denys Vlasenko
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=200712181032.17947.schane@osmozis.com \
--to=schane@osmozis.com \
--cc=busybox@busybox.net \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox