Making wpa_supplicant work with dhclient on Fedora

[Dan Williams]

On Mon, 2008-05-19 at 11:22 +0800, Reik Red wrote:
> Jar wrote:
> > Reik Red wrote:
> >   
> >> Pavel Roskin wrote:
> >>     
> >>> Hello!
> >>>
> >>> I have figured out a way to use wpa_supplicant and dhclient on the same
> >>> interface in Fedora (tested on Fedora 8 and Fedora 9).  I'm actually
> >>> surprised that I don't see loud screams that it's not working.  It's
> >>> quite possible that I'm missing something obvious that everybody else it
> >>> doing.  Then I apologize for the noise in advance.  Anyway, that's the
> >>> simplest solution I could find.
> >>>   
> >>>       
> >
> > I personally usually just edit the /etc/init.d/wpa_supplicant
> > so that it will start before network service
> > (chkconfig:   - 23 88 --> chkconfig:   - 9 90) and everything works. 
> > Also the section:
> >
> > ### 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
> >
> > has to be deleted because otherwise wpa_supplicant service try to start 
> > after messagebus (even if in /etc/sysconfig/wpa_supplicant the D-Bus 
> > interface is not enabled) and it is too late for dhcp. I think the 
> > wireless stuff should also work in text mode without the help of X & NM.
> >
> >   
> Jar, could not agree more that wireless should work in text mode, and 
> not depend on some add-on code or post-boot action by KDE or Gnome or 
> what-have-you.

You shouldn't need to depend on add-on code, and it does work in text
mode.  But if you do want it to work in text mode (until the startup
sequence bugs are fixed), then you are assumed to be comfortable enough
with a terminal to be able to set the startup priorities earlier, and to
possibly remove the -u flag that enables D-Bus support, because dbus
starts after network.

Basically, the whole startup framework needs to be more granular.  ie,
rsyslog has to start after network because some people use networked
syslog, but the startup script isn't smart enough to _know_ when it
needs network and when it doesn't, and to start itself either before or
after the network service accordingly.  Same for the supplicant.

Dan