* modprobe: cannot parse modules.dep error
@ 2007-12-18 9:32 Saravanan Chanemouganandam
2007-12-18 11:08 ` Denys Vlasenko
0 siblings, 1 reply; 2+ messages in thread
From: Saravanan Chanemouganandam @ 2007-12-18 9:32 UTC (permalink / raw)
To: netfilter; +Cc: busybox
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: modprobe: cannot parse modules.dep error
2007-12-18 9:32 modprobe: cannot parse modules.dep error Saravanan Chanemouganandam
@ 2007-12-18 11:08 ` Denys Vlasenko
0 siblings, 0 replies; 2+ messages in thread
From: Denys Vlasenko @ 2007-12-18 11:08 UTC (permalink / raw)
To: busybox; +Cc: Saravanan Chanemouganandam, netfilter
On Tuesday 18 December 2007 09:32, Saravanan Chanemouganandam wrote:
> 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
Can you try the following in modprobe.c?
static struct dep_t *build_dep(void)
{
...
filename = xasprintf("/lib/modules/%s/modules.dep", un.release);
fd = open(filename, O_RDONLY);
if (ENABLE_FEATURE_CLEAN_UP)
free(filename);
if (fd < 0) {
/* Ok, that didn't work. Fall back to looking in /lib/modules */
fd = open("/lib/modules/modules.dep", O_RDONLY);
if (fd < 0) {
- bb_error_msg_and_die("cannot parse modules.dep");
+ bb_error_msg("cannot parse modules.dep");
+ return NULL;
}
}
...
--
vda
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-12-18 11:08 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-12-18 9:32 modprobe: cannot parse modules.dep error Saravanan Chanemouganandam
2007-12-18 11:08 ` Denys Vlasenko
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox