Bug 16070

Summary:	firewalld doesn't respond to transient interfaces
Product:	[Retired] Red Hat Linux	Reporter:	John William <jw2357>
Component:	linuxconf	Assignee:	Nalin Dahyabhai <nalin>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2	CC:	tao
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-02-21 18:47:44 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description John William 2000-08-12 16:29:30 UTC

I am running RH6.2, with linuxconf 1.19r2. The machine has two ethernet 
interfaces, eth0 on the local network and eth1 connected to the Internet. 
I am using the "firewalld" firewall daemon to manage the connection 
through eth1. The machine also has a modem and can use ppp0 to connect to 
the Internet.

When the firewall daemon was started, eth1 was up and ppp0 was down. 
firewalld created a reasonable set of rules (verified with /sbin/ipchains -
L -v). After some time, eth1 went down. I shut down eth1 (/sbin/ifconfig 
eth1 down) and started ppp0 (/sbin/ifconfig ppp0 up). The linuxconf 
firewall daemon was still running, but never changed the rules. When I 
went into linuxconf, to the properties page for the firewall daemon, 
everything looked ok, and when linuxconf restarted the daemon, it created 
a good set of rules for that configuration. However, after switching 
interfaces back, firewalld again didn't recognize the change.

Comment 1 Brent Fox 2002-06-05 16:11:12 UTC

Closing because we don't ship linuxconf anymore

Comment 2 Red Hat Bugzilla 2006-02-21 18:47:44 UTC

Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.