Bug 147046 - NetworkManager and iptables prevent system from shutdown
Summary: NetworkManager and iptables prevent system from shutdown
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager   
(Show other bugs)
Version: 3
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Dan Williams
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2005-02-03 22:51 UTC by Quereller
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-03-20 17:53:51 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
chkconfig --list (3.45 KB, text/plain)
2005-02-03 22:54 UTC, Quereller
no flags Details

Description Quereller 2005-02-03 22:51:29 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041111 Firefox/1.0

Description of problem:
When running services iptables and NetworkManger together, system
hangs on shutdown when stopping iptables. It even hangs when I remove
K92iptables so it could also be related to stoping loopback.

Version-Release number of selected component (if applicable):
NetworkManager-0.3.3-1.cvs20050119.2.fc3 iptables-1.2.11-3.1.FC3

How reproducible:

Steps to Reproduce:
1. Start NetworkManger
2. Start iptables
3. shutdown

Actual Results:  system hangs

Expected Results:  clean shutdown

Additional info:

Hardware: 1 NIC e1000

The problem is not related to the iptables rules itself, you can
accept all packets and it happens anyway

Comment 1 Quereller 2005-02-03 22:54:50 UTC
Created attachment 110630 [details]
chkconfig --list

Comment 2 Mark Stier 2005-03-19 23:12:33 UTC
This bug occurs on my notebook, too. I have done some investigation and can
provide a quick work-around:

disable the iptables modules unloading by setting the corresponding option in
/etc/sysconfig/iptables-config to "no".

Shutting down the iptables service lets me reproduce the problem: I had a
"modprobe -r ipt_state" process consuming all CPU and which could not be killed
by a KILL signal.

The bug only occurs if the NetworkManager actually has been active (i.e. after
the NetworkManagerInfo applet told it where to connect).

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