There is now a iptables-1.4.11.1-1.mga1 in bs heading for updates_testing The reason for doing the version upgrade from 1.4.10 -> 1.4.11.1 is that it's needed to fully support our 2.6.38 series kernels. (1.4.10 only fully supports up to 2.6.36 series) (and 1.4.11* series got released 2011-May-26, so it missed final freeze) it also fixes mga# 1404 full changelog: - update to 1.4.11.1 (full kernel 2.6.37-39 support) - Move the runtime libip{4,6}tc.so.* libraries to /%{_lib}, so that iptables in /sbin can use them when /usr isn't mounted yet (mga#1404) - libmajor is now 6 - add compat symlinks for ip(6)tbles-multi - update filelists
CC: (none) => sander.lepikAssignee: bugsquad => qa-bugs
I've been running iptables 1.4.11.1 since June 23rd, on my i586 system without any problems. Is there a quick way to get a full list of what packages were provided by the source rpm? From /var/lib/urpmi/names.Core Updates Testing it appears to be ... libip6tc-devel libiptc-devel libip6tc0 libip4tc0 libip4tc-devel iptables libiptables6 libiptables-devel with the -devel packages manually instlaled. The following two were pulled in when I manually installed libip4tc-devel libiptc0 libipq-devel The package libipq0 did not get installed. Should it be?
CC: (none) => davidwhodgins
Tested on x86_64, it works for me (I don't know of a test case).
CC: (none) => lists.jjorge
Can someone from the sysadmin team push the packages libip6tc-devel libiptc-devel libip6tc0 libip4tc0 libip4tc-devel iptables libiptables6 libiptables-devel libiptc0 libipq-devel libipq0 from Core Updates Testing to Core Updates please. The srpm is iptables-1.4.11.1-1.mga1.src.rpm
(In reply to comment #2) > Tested on x86_64, it works for me (I don't know of a test case). I think a test case could be installing the packages, and testing a few iptables commands.
CC: (none) => boklm
(In reply to comment #4) > (In reply to comment #2) > > Tested on x86_64, it works for me (I don't know of a test case). > > I think a test case could be installing the packages, and testing a few > iptables commands. Also test that shorewall / drakfirewall is not broken.
As per comment 1, I've been running with the updated iptables since June 23rd. Shorewall is working, grc.com shows expected ports open, with rest stealthed. Incoming connections from autossh (from systems I support) are working, as are all expected outgoing connections. [dave@hodgins ~]$ locate libiptc.so /lib/libiptc.so.0 /lib/libiptc.so.0.0.0 /usr/lib/libiptc.so [dave@hodgins ~]$ ll /usr/lib/libiptc.so lrwxrwxrwx 1 root root 22 Jun 29 20:49 /usr/lib/libiptc.so -> ../../lib/libiptc.so.0* The module has been moved to /lib, with a symlink for compatibility. As per comment 3, the packages are ready to move to core updates, with an advisory ... Updating iptables to fully support 2.6.38 series kernels.
pushed to updates.
Status: NEW => RESOLVEDResolution: (none) => FIXED
CC: boklm => (none)