Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 173785 - Need delay between ifup-wireless and checking link status
Need delay between ifup-wireless and checking link status
Product: Fedora
Classification: Fedora
Component: initscripts (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2005-11-21 00:27 EST by Anton Solovyev
Modified: 2014-03-16 22:56 EDT (History)
2 users (show)

See Also:
Fixed In Version: 8.38-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-08-07 14:29:57 EDT
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 Anton Solovyev 2005-11-21 00:27:24 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1

Description of problem:
I have ipw2200 wireless card in a laptop. It takes some (though fairly short) time for the card to connect to the network when WEP is enabled.

The ifup script is written in such a way that it checks link status right after ifup-wireless is executed. In my case there is not enough time for the card to connect and the link status check that immediately follows in the code fails (on boot).

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Well...

Actual Results:  Wireless interface is not brought up on boot.

Expected Results:  The opposite.

Additional info:

I suggest letting user to insert a delay in the very end of the ifup-wireless. A variable in ifcfg-ethX would be fine.
Comment 1 Bill Nottingham 2006-08-07 14:29:57 EDT
Current rawhide initscripts has a LINKDELAY parameter which may solve this for you.

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