Quote:
The iptables package included with slackware 11 is simply outdated. There were no specific options for the package. Simply build the source from netfilter.org and load the rules via script instead of using the restore function. The link I posted above to the iptables 1.3.7 package works with 2.6.18+. Try it out and see for yourself. *NOTE* Unless the proper modules were built for or included with the kernel currently running then yes, iptables will return errors due to unsupported features. Manually load the modules or recompile a kernel with proper feature support for iptables. |
Quote:
Quote:
Is there some *legitimate* need to have the latest version of iptables on your system, or are you simply wanting some shiny new version number? Quote:
Quote:
|
Quote:
The package I built for 1.3.7 and posted in a previous link works fine with 2.6.18+. Try it yourself if you don't believe me. The issue here is that 1.3.5 DOES NOT WORK with 2.6.20. This is reported on the netfilter.org website in the iptables changelogs. Telling him to use the 'official' slackware 11 package is pointless because it DOES NOT WORK with 2.6.20. |
This is informative. It seemed as if iptables-1.3.7 compiled ok for kernel 2.6.20.1 and I just have a problem with the iptables-restore program which doesn't have to be used. I guess there's a difference between iptables-restore and iptables? My iptables rules are in /etc. I'm obviously an amateur at this-my degree is in civil engineering and not pcs!
|
Quote:
As you can see here: bash-3.1# iptables-save > /etc/iptables bash-3.1# iptables-restore < /etc/iptables bash-3.1# the iptables-save(8) and iptables-restore(8) functions work just fine. I normally load my rules from the /etc/rc.d/rc.firewall script (which, for the record, is called from /etc/rc.d/rc.inet2), but for your benefit, I just verified that the two save/restore functions work as advertised. Quote:
bash-3.1# uname -a Linux isotope 2.6.20 #1 SMP PREEMPT Tue Feb 6 18:49:52 CST 2007 i686 pentium4 i386 GNU/Linux bash-3.1# iptables --version iptables v1.3.5 bash-3.1# ls /var/log/packages/iptables-1.3.5-i486-2 /var/log/packages/iptables-1.3.5-i486-2 |
ok, I followed the advice of loading each rule individually and found (I think) the offending rule:
-A INPUT -m state --state ESTABLISHED -j ACCEPT This rule loaded up fine in the other kernels....what do I need to enable now in the .config for the kernel? |
Quote:
|
that was it....I have iptables-1.3.7 booting fine with kernel-2.6.20.1. After booting into the new kernel I built iptables with only make and make install and a sym link between /usr/src/linux and /usr/src/linux-2.6.20.1. The .config file for the kernel (using menuconfig) had all the options enabled in:
Networking>Networking Options>Network Packet Filtering Framework>Core Netfilter Configuration |
Quote:
Also, don't forget to remove the custom iptables binaries and libraries if you later want to install/upgrade it with an official Slackware package. Unless you changed it, you installed it to /usr/local. Official (and most unofficial) packages will install to /usr, so you'll wind up with two sets of iptables files, and the one in /usr/local will usually override the one in /usr unless the path is explicitly defined in scripts and such. Quote:
RW |
I get peace of mind from using the latest stable version of software so I keep my kernel and iptables current. I don't know enough about pc security to use the snapshots of iptables. Thanks for all the help here!
|
Quote:
If you're wanting the latest *stable* version of a 2.6 kernel for a production system, you should probably lean toward 2.6.16.x (which is currently at 2.6.16.42) - that kernel series is going to maintained long-term with security and reliability fixes. |
Quote:
I have iptable tgz packages installed for 1.3.5 and 1.3.6. I have been building 1.3.7 for each stable kernel update since December. How would I go back to iptables 1.3.5? |
Quote:
Quote:
With all that said, if you *really* want to run the latest version of iptables, then please, for your sake, consider using the SlackBuild script and associated files available at http://slackware.osuosl.org/slackwar...ptables-1.3.6/ See http://slackbuilds.org/howto/ for an idea of how to work with that. The benefit of using the SlackBuild script is that it will build a package that you can install/upgrade/remove with the standard pkgtool(8) suite. |
wow-SlackBuild looks good! I now have something new to mess with-thank you!
|
Success
Thanks to all who contributed to this thread. Very useful.
Had the same problem with my FC6 installation when I tried to update the kernel to a custom 2.6.20.2 just now. Got error during boot saying iptables-restore failed at line 27 (which is the commit statement in my case). I run 'make menuconfig' again and went into: Networking>Networking Options>Network Packet Filtering Framework>Core Netfilter Configuration Enabled everything as modules in there, then make, reinstall kernel and modules, reboot, problem solved :D Mons Edit: just for completeness, the iptables version I have is 1.3.5 and when loading the lines in /etc/sysconfig/iptables one by one, the failing line is a similar one to robw810 above (...state ESTABLISHED...). That's just if others get the same problem, all green 'OK's on my machine now :) |
All times are GMT -5. The time now is 09:21 AM. |