Making wpa_supplicant work with dhclient on Fedora
dcbw at redhat.com
Mon May 19 11:19:53 EDT 2008
On Mon, 2008-05-19 at 07:19 -0400, Pavel Roskin wrote:
> On Mon, 2008-05-19 at 11:22 +0800, Reik Red wrote:
> > 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.
> Yes, I tried NetworkManager in Fedora 9, and it's working fine as long
> as I log in into GNOME. The fundamental problem is, it's absolutely
Logging in is unnecessary to have NM connect you. If you have setup
your machine with static IP either from the installer, or from
system-config-network (make sure the "Controlled by NetworkManager" box
is checked) then NM will respect the static IP configuration you have
provided. If that's not the case, check
your /etc/sysconfig/network-scripts/ifcfg-eth0 config file to ensure
that it's using the settings you want, if not edit it with
system-config-network or directly with a text editor. If that file
looks correct, then we can debug further.
Note that system settings support for WPA does not currently exist, not
because NM can't handle WPA (which it certainly can) but because the
old-school config files (ifcfg-XXXX) can't handle WPA settings yet.
> unacceptable for anything I would ever want to access remotely. One
> reboot, and the communication is lost. I know, dynamic IP is not ideal
> for that, but there are ways work it around.
> I agree that distros should try to keep the stuff integrated, but this
> is too fundamental to leave it solely to the distros. It seems to me
> that several fixes are needed to make it all work reliably. But the
> first step is acknowledging the problem.
> Next step it to formulate what a good DHCP client should (and should
> not) do to play well with wpa_supplicant.
More information about the HostAP