From: "Nathan" <firstname.lastname@example.org> To: "Marc-Christian Petersen" <email@example.com> Cc: "Linux Kernel List" <firstname.lastname@example.org> Subject: Re: Updated to kernel 2.4.19 and now ipchains and iptables are broke. Date: Thu, 26 Sep 2002 11:11:29 -0600 [thread overview] Message-ID: <004201c2657f$c1a1bed0$f101010a@nathan> (raw) In-Reply-To: <email@example.com> I saw the config option for netfilter that said if you use this it won't use ipchains, so I said no to that... The section of my .config file from make config (yeah I'm a glutton for punishment): # Networking options # CONFIG_PACKET=y # CONFIG_PACKET_MMAP is not set # CONFIG_NETLINK_DEV is not set # CONFIG_NETFILTER is not set # CONFIG_FILTER is not set CONFIG_UNIX=y CONFIG_INET=y CONFIG_IP_MULTICAST=y CONFIG_IP_ADVANCED_ROUTER=y # CONFIG_IP_MULTIPLE_TABLES is not set # CONFIG_IP_ROUTE_MULTIPATH is not set # CONFIG_IP_ROUTE_TOS is not set CONFIG_IP_ROUTE_VERBOSE=y # CONFIG_IP_ROUTE_LARGE_TABLES is not set # CONFIG_IP_PNP is not set # CONFIG_NET_IPIP is not set CONFIG_NET_IPGRE=y # CONFIG_NET_IPGRE_BROADCAST is not set # CONFIG_IP_MROUTE is not set # CONFIG_ARPD is not set # CONFIG_INET_ECN is not set CONFIG_SYN_COOKIES=y CONFIG_IPV6=y # CONFIG_KHTTPD is not set # CONFIG_ATM is not set # CONFIG_VLAN_8021Q is not set ----- Original Message ----- From: "Marc-Christian Petersen" <firstname.lastname@example.org> To: <email@example.com> Cc: "Nathan" <firstname.lastname@example.org> Sent: Thursday, September 26, 2002 11:02 AM Subject: Re: Updated to kernel 2.4.19 and now ipchains and iptables are broke. Hi Nathan, > This is surely the greenest of green questions (sorry), but I finally got my > kernel re-compiled the way I want it using the 2.4.19 sources from > kernel.org. It loads, seems to be working fine, except ipchains and > iptables... ipchains insists that it is incompatible with my kernel, and > iptables isn't sure what's going on but it thinks maybe something (. Well > fine. I downloaded the latest versions of ipchains/tables from rpmfind and > upgraded, same thing. "Incompatible with this kernel" for ipchains seems so that you have compiled Netfilter stuff into your kernel. "itself or the kernel needs upgrading" for iptables seems so that you either haven't compiled netfilter as module(s) or static into the kernel and forgot something in the kernel config. > I haven't been able to find any actual solutions off google for this... a > few people mention the same problem but no fixes. Can someone point this > rookie in the right direction to fix my packet filters? :-) Check your kernel config. "make menuconfig" or "xconfig" and goto: Networking options ---> IP: Netfilter Configuration ---> and look if you did it properly. -- Kind regards Marc-Christian Petersen http://sourceforge.net/projects/wolk PGP/GnuPG Key: 1024D/569DE2E3DB441A16 Fingerprint: 3469 0CF8 CA7E 0042 7824 080A 569D E2E3 DB44 1A16 Key available at www.keyserver.net. Encrypted e-mail preferred.
next prev parent reply other threads:[~2002-09-26 17:05 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-09-26 17:02 Marc-Christian Petersen 2002-09-26 17:11 ` Nathan [this message] 2002-09-26 17:19 ` Marc-Christian Petersen -- strict thread matches above, loose matches on Subject: below -- 2002-09-26 16:50 Nathan 2002-09-27 7:07 ` Harald Welte
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='004201c2657f$c1a1bed0$f101010a@nathan' \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Updated to kernel 2.4.19 and now ipchains and iptables are broke.' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).