Bug 16070 - firewalld doesn't respond to transient interfaces
firewalld doesn't respond to transient interfaces
Product: Red Hat Linux
Classification: Retired
Component: linuxconf (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Depends On:
  Show dependency treegraph
Reported: 2000-08-12 12:29 EDT by John William
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:47:44 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description John William 2000-08-12 12:29:30 EDT
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 12:11:12 EDT
Closing because we don't ship linuxconf anymore
Comment 2 Red Hat Bugzilla 2006-02-21 13:47:44 EST
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.