Red Hat Bugzilla – Bug 122801
ifup exits before setting wireless options when bridging
Last modified: 2014-03-16 22:45:00 EDT
Description of problem:
When setting up bridged interfaces, any wireless options are ignored
because of an apparently bogus "exit 0" in /sbin/ifup that causes it
to exit before wireless options are processed. The following seems to
--- /sbin/ifup 2003-11-07 08:59:26.000000000 -0600
+++ /sbin/ifup 2004-05-08 02:54:51.405951000 -0500
@@ -180,7 +180,6 @@
# Upon adding a device to a bridge,
# it's necessary to make radvd reload its config
[ -r /var/run/radvd/radvd.pid ] && kill -HUP `cat
- exit 0
# now check the real state
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a bridge interface (TYPE=Bridge).
2. Add a wireless interface (BRIDGE=<bridge interface>, TYPE=Wireless)
and set some wireless options (ESSID, KEY, etc.).
3. Watch those options be silently ignored when bringing up the interface.
iwconfig on the wireless interface shows whatever the default (driver)
settings for the card are, such as ESSID "test".
iwconfig should report the options in ifcfg-<interface>. Removing
that one line from /sbin/ifup makes this work.
I haven't had a chance to see if this is still broken in FC2/rawhide yet.
Does just moving the 'is_wireless...' check & code above the bridge
code work for you?
is_wireless_... check moved in initscripts-8.17-1. Please try this and see if it
works for you.
*** Bug 164509 has been marked as a duplicate of this bug. ***
*** Bug 183335 has been marked as a duplicate of this bug. ***