Dennis Freise <[EMAIL PROTECTED]> wrote: > --Signature=_Sun__9_Nov_2003_19_20_11_+0100_KkMeCY42_=g+UfKT > Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline > Content-Transfer-Encoding: 7bit > > On Sun, 9 Nov 2003 17:36:21 +0000 (UTC) Eamon Caddigan > <[EMAIL PROTECTED]> wrote: > >> > root # iptables -t nat -I POSTROUTING -j MASQUERAQDE -s >> > 192.168.1.3/16 >> > /lib/modules/2.4.22-ck1/kernel/net/ipv4/netfilter/ip_tables.o: >> > unresolved symbol nf_unregister_sockopt >> > /lib/modules/2.4.22-ck1/kernel/net/ipv4/netfilter/ip_tables.o: >> > unresolved symbol nf_register_sockopt >> > /lib/modules/2.4.22-ck1/kernel/net/ipv4/netfilter/ip_tables.o: >> > insmod >> > /lib/modules/2.4.22-ck1/kernel/net/ipv4/netfilter/ip_tables.o >> > failed >> > /lib/modules/2.4.22-ck1/kernel/net/ipv4/netfilter/ip_tables.o: >> > insmod ip_tables failed iptables v1.2.8: can't initialize iptables >> > table `nat': iptables who? (do you need to insmod?) Perhaps >> > iptables or your kernel needs to be upgraded. >> >> Had the same problem when I first tried to get ip_tables up and >> running. Some Googling revealed that ip_tables only works if >> CONFIG_MODVERSIONS isn't set. Weird, huh? > > I do have CONFIG_MODVERSIONS=y set and I do have masquerading up and > running on ppp0. Therefor I do think it actually _is_ working > together :)
Wow, which kernel version are you running? CONFIG_MODVERSIONS was the only difference between unresolved symbol errors in ip_tables.o and a working setup for me, using gentoo-sources-2.4.20-r8. That kernel is a harsh mistress. -Eamon -- [EMAIL PROTECTED] mailing list
