Re: WPA Supplicant *CAN* connect, but NetworkManager can't.

["Darren Albers" <dalbers gmail com>]

On 8/17/07, Michael Wilber <hotdog003 gmail com> wrote:
> Darren Albers wrote:
> > On 8/16/07, Michael Wilber <hotdog003 gmail com> wrote:
> >
> >> Hello! I'm using a Zonet ZEW1602 wireless card using ndiswrapper in
> >> Ubuntu Feisty.
> >>
> >> If I do 'wpa_supplicant -Dndiswrapper -iwlan0 ' [...], then I can't
> >> connect, as usual.
> >> If I do 'wpa_supplicant -Dwext -iwlan0' [...], then I can.
> >>
> >> NetworkManager still can't. I talked with some of the devs on
> >> #ndiswrapper, and they say that -Dndiswrapper has been depreciated for
> >> quite some time. Is this a bug, and if so, how do I report it?
> >>
> >
> > This might be a Feisty specific bug, NetworkManager will always use
> > WEXT and not the device specific driver however a number of
> > distributions patched NetworkManager to use the device specific driver
> > for some cards.   Two drivers that many Distro's patched for were
> > NDISwrapper and Madwifi.
> >
> > I know that Ubuntu used to ship these patches but I don't know if they
> > still do, can you grab the Ubuntu source (apt-get source
> > network-manager) and look in the debian/patches directory and see if
> > one of the patches sends -Dndiswrapper instead of -Dwext?
> >
> I can't find anything, I'm afraid.
>
> Here's the list of patches that ubuntu applies:
> 01-supplicant_timeout.patch
> 02-dbus_access_network_manager.patch
> 04-if_fix.patch
> 05-debian_backend.patch
> 06-dispatch_more_events.patch
> 09_fix_bigendian_words.patch
> 10-po_fr.patch
> 11-man_page_sh_name.patch
> 12_dbus1.0.patch
> 13-rml-wpa-workarounds.patch
> 14-j-hostap-supplicant-driver.patch
> 16_undefined_macros.patch
> 17_avahi_autoipd.patch
> 18_static_network-admin.patch
> 19_interfaces_can_have_more_than_one_instance.patch
> 20_do_not_take_over_dhcpv4iface_when_v6_is_configured.patch
> 21_manual_means_always_online.diff
> 22_manual_config_available_when_connected.patch
>
> None of them mention ndiswrapper. The 13-rml-wpa-workarounds.patch,
> however, does change wext to madwifi, although I don't think it's related.
>
> If you'd like, I can do an strace on network manager.
>
>

I think the next step would be to post the output of NM, try the following:

Stop NM with:
    sudo /etc/dbus-1/event.d/25NetworkManager stop

Once NetworkManager is stopped start it again from a terminal with:
sudo NetworkManager --no-daemon

Copy the output of NetworkManager and post it here (remember to remove
any wireless encryption keys that might be in the output!).