On 07/20/2010 10:54 AM, Frank Elsner wrote:
On Tue, 20 Jul 2010 09:55:02 -0700 JD wrote:
On 07/20/2010 08:28 AM, Frank Elsner wrote:
On Tue, 20 Jul 2010 10:12:29 -0500 (CDT) lxnf98mm@comcast.net wrote:
I added a wireless card to a machine that has no gui interface installed, so no NM I configured wpa_supplicant and wlan startup script What I do not get is when the machine boots wpa_supplicant starts after the network script
"after" is the problem. wpa_supplicant must start *before" network. Change the sequence.
--Frank Elsner
I have done this numerous times. Then an update will come and reset the sequence so that in run level 5, S10network will be executed before S23wpa-supplicant.
But this has NOT caused any problems for me since I changed my ifcfg-ra0 to use a static IP address instead of dynamic.
I had no problems with dynamic IPs for interface wlan0 :-)
All S10network is doing is simply ifconfig'ing the network interfaces. The problems will occur if you interface is configured to get it's IP address dynamically, per /etc/sysconfig/network-scripts/ifcfg-$INTERFACE
That said, I have found the DHCP over wireless does not work for for me at all - ifconfig is never able to obtain an address. So I used static IP. Now it does not matter which one starts first.
Ups, you should analyze your dhclient problems and fix it. Dynamic IPs are quite usual in WLANs.
--Frank Elsner
I think the problem is in the router. It is an at&t uverse router. Even the windows machines cannot get a dhcp brokered address over wireless. So I set all 3 windows machines to static ip's as well.