On Sun, 2008-04-20 at 10:16 -0300, George N. White III wrote: > For debugging you > want to "open up" your AP temporarily and use a manual wpa_supplicant > configuration (disable NetworkManager, enable wpa_supplicant or just > start it from a command line). Ok, it seems that wpa_supplicant was the key. As soon as I started it up I got a "Link Quality = 93/100" I could then run "dhclient wlan0" on the comamnd line and the interface came up fine. At start-up I seem to have a bit of a "chicken and egg" dependency problem though. During startup the S10network script gets run first, which tries to do the dhclient command for wlan0, but the wpa_supplicant daemon doesn't get started until S28wpa_supplicant. Apparently, wpa_supplicant startup depends on S27messagebus, ### BEGIN INIT INFO # Provides: wpa_supplicant # Required-Start: $local_fs messagebus # Required-Stop: $local_fs messagebus # Default-Start: # Default-Stop: 0 1 6 # Short-Description: start and stop wpa_supplicant # Description: wpa_supplicant is a tool for connecting to wireless networks ### END INIT INFO which in turn depends on S26rsyslog: ### BEGIN INIT INFO # Provides: messagebus # Required-Start: $syslog $local_fs # Required-Stop: $syslog $local_fs # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: The D-Bus systemwide message bus # Description: This is a daemon which broadcasts notifications of system # events and other messages. See http://www.freedesktop.org/software/dbus ### END INIT INFO which depends on S10 network. ### BEGIN INIT INFO # Provides: $syslog # Required-Start: $local_fs $network $remote_fs # Required-Stop: $local_fs $network $remote_fs # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Enhanced system logging and kernel message trapping daemons # Description: Rsyslog is an enhanced multi-threaded syslogd supporting, # among others, MySQL, syslog/tcp, RFC 3195, permitted # sender lists, filtering on any message part, and fine # grain output format control. ### END INIT INFO So, due to dependency issues it seems I can't actually get wpa_supplicant started before the S10network script which gets the IP address assigned. All of this means that at bootup time I end up with everything up, but no IP address assigned to my wlan0 card. I run "dhclient wlan0" manually and it comes up just fine. While I can add a "dhclient wlan0" command to /etc/rc.local to get things up at boot time I assume there is some standard way to do this. I am a bit worried that some network related daemons are getting fired off before an IP address actually gets assigned to an interface. Don't a lot of daemons do an inventory of the different IP's available when they startup and then start listening on them for incoming requests ? If I don't bring the interface up until rc.local, which is the last thing run, any daemon that may be listening on IP addresses would miss listening on the wlan0 interface. What is the standard way to get wpa_supplicant fired off so I can get an IP address assigned before any of the network daemons get started ? Thanks Chris Kottaridis (chriskot@xxxxxxxxxxxxx) -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
