Sunny wrote:
On Fri, 28 Jan 2005 13:57:08 -0600, Darryl Gregorash <raven@accesscomm.ca> wrote:
Mea culpa; the ip6tables modules are named just that, ip6tables_*. You could try an extended regexp search (-E option in grep), or just run lsmod and sort through the list. Module dependencies are listed in the fourth column.
linux:/ # lsmod | grep -i ip ipv6 236800 134 linux:/ #
This is the only one I can suspect. God, I hate to reboot.
Sunny
No firewall on that system? There should be about 9 modules named ip* just from iptables alone, nevermind NAT and connection tracking, and nevermind ip6tables. If ipv6 is enabled, then the system should automatically configure a default ipv6 address for your network devices, and I think that should result in a few more modules being loaded. In any event, "lsmod | grep ip" should yield far more than just ipv6. BTW, I discovered just today that, at least in 9.0, SuSEfirewall2 will load a couple of ip6tables modules even if ipv6 is not loaded. It used modprobe to do so, and there is no complaint from the system. If I try to load the same module using insmod, I get "unresolved symbol" errors. Very strange. I'm a bit curious about the output you're posting here; when I run lsmod, I get things like iptable_nat 15374 1 [ip_nat_ftp] This shows that this module depends on ip_nat_ftp, so the latter cannot be removed until iptable_nat (and any other modules depending on it) is removed.