[Buildroot] modprobe: cannot parse modules.dep error

[Buildroot] modprobe: cannot parse modules.dep error

[saravanan chanemouganandam]

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]);
system(buff);
it throws the following modprobe error. iptables -t mangle -A PREROUTING -d 88.160.215.156 -p icmp -j MARK --set-mark 512modprobe: cannot parse modules.depmodprobe: cannot parse modules.depiptables -t mangle -A PREROUTING -s 88.160.215.156 -p icmp -j MARK --set-mark 512modprobe: cannot parse modules.depmodprobe: cannot parse modules.depiptables -t mangle -A PREROUTING -d 88.160.215.156 -p tcp --dport http -j MARK --set-mark 512modprobe: cannot parse modules.depmodprobe: 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.? ThanksSaraOsmozis
_________________________________________________________________
Post free property ads on Yello Classifieds now! www.yello.in
http://ss1.richmedia.in/recurl.asp?pid=221
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20071218/b47b365b/attachment.htm 

[Buildroot] modprobe: cannot parse modules.dep error

[Ivan Kuten]

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]);
> system(buff);
> it throws the following modprobe error. iptables -t mangle -A PREROUTING -d 88.160.215.156 -p icmp -j MARK --set-mark 512modprobe: cannot parse modules.depmodprobe: cannot parse modules.depiptables -t mangle -A PREROUTING -s 88.160.215.156 -p icmp -j MARK --set-mark 512modprobe: cannot parse modules.depmodprobe: cannot parse modules.depiptables -t mangle -A PREROUTING -d 88.160.215.156 -p tcp --dport http -j MARK --set-mark 512modprobe: cannot parse modules.depmodprobe: 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.? ThanksSaraOsmozis

Try to do strace on iptables, may be calling modprobe is defined in iptables source.

Regards,
Ivan
--------------------------------
Embedded Linux engineer,
Promwad Company: http://www.promwad.com/
Homepage : http://www.ivankuten.com/
--------------------------------

[Buildroot] modprobe: cannot parse modules.dep error

[Ivan Kuten]

saravanan chanemouganandam wrote:
> Hi Ivan,
>  
>  
> Here is the starce on iptables showing call to "/sbin/modprobe" . I don't understand why it tries to load the modules thru modprobe when all netfilter ipables and xtables supports are built into the kernel.
>  
> Execuse me for the mail received in a junk format.
>  

Think iptables do not have a way to know if you compiled iptables as modules or in kernel.
I'd suggest to try ask on iptables mailing list why it has such behaviour.


Regards,
Ivan
--------------------------------
Embedded Linux engineer,
Promwad Company: http://www.promwad.com/
Homepage : http://www.ivankuten.com/
--------------------------------