Bug 106589 - Unloading iptables modules fails at "service iptables restart"
Summary: Unloading iptables modules fails at "service iptables restart"
Keywords:
Status: CLOSED DUPLICATE of bug 103177
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: iptables
Version: 7.3
Hardware: athlon
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Thomas Woerner
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-10-08 18:48 UTC by Samuli Kärkkäinen
Modified: 2007-04-18 16:58 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:59:02 UTC
Embargoed:


Attachments (Terms of Use)

Description Samuli Kärkkäinen 2003-10-08 18:48:37 UTC
When I do "service iptables restart" (or "service iptables start") I get
following output

Flushing firewall rules:                                   [  OK  ]
Setting chains to policy ACCEPT: filter                    [  OK  ]
Unloading iptables modules:

After which it sits there forever. "ps" shows that it's doing "modprobe -r
ip_conntrack_ftp". "lsmod" shows that it succeeds in unloading the module, or at
least in removing it from lsmod's listing. No error messages appear in the
syslog. Control-C doesn't kill the modprobe process, nor does even sending it
SIGKILL.

This didn't happen before I had updated to iptables-1.2.8-8.72.3. Kernel is
kernel-2.4.20-20.7. If I run the command immediately after booting the box, it
works alright, but fails repeatably when the box has been running for a while.

If, while the modprobe -r is still running, I do "insmod ip_conntrack_ftp", I
get the following errors:

/lib/modules/2.4.20-20.7/kernel/net/ipv4/netfilter/ip_conntrack_ftp.o:
unresolved symbol ip_conntrack_helper_unregister_Reea5a3fd
/lib/modules/2.4.20-20.7/kernel/net/ipv4/netfilter/ip_conntrack_ftp.o:
unresolved symbol ip_conntrack_helper_register_Ra22d6eb5
/lib/modules/2.4.20-20.7/kernel/net/ipv4/netfilter/ip_conntrack_ftp.o:
unresolved symbol ip_conntrack_expect_related_Rfc718b15

Comment 1 Thomas Woerner 2003-10-09 09:33:21 UTC

*** This bug has been marked as a duplicate of 103177 ***

Comment 2 Red Hat Bugzilla 2006-02-21 18:59:02 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


Note You need to log in before you can comment on or make changes to this bug.