Re: Problems with network-manager 0.6.6 in Ubuntu(8.04)

[Dan Williams <dcbw redhat com>]

On Tue, 2008-04-08 at 14:52 -0400, Ryan Novosielski wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Rev. Justin Brown wrote:
> > I am trying to connect to my school's wireless network (PEAP, MSCHAPv2,
> > Dynamic WEP). I use Ubuntu and am trying to switch to Hardy beta. It
> > comes with network-manager 0.6.6. <http://0.6.6.> However, I can no
> > longer connect. I have tried two different ways: "Connect to another
> > network" and "Connect to 802.1x network." They both seem to yield the
> > same result. Are there any known regressions or should I change to a
> > older/newer version? Whenever I edit the connections, the default always
> > stores my password as a Private key instead of a password, which seems
> > strange, but that also doesn't help.
> > Some more info:
> > Ubuntu Hardy beta fully updated
> > Kernel 2.6.24-15 #1 SMP
> > Intel ABG3945 running iwl3945 driver
> > The daemon logs repeat the same messages everytime I try to connect:
> > Apr  7 16:41:37 lemon NetworkManager: <debug> [1207604497.359889]
> > nm_device_802_11_wireless_update_bssid(): Roamed from BSSID
> > 00:15:C7:83:2F:01 to 00:15:C7:83:2F:00 on wireless network 'slunet'
> > Apr  7 16:41:37 lemon NetworkManager: <debug> [1207604497.365255]
> > nm_dbus_signal_filter(): NetworkManagerInfo triggered update of wireless
> > network 'slunet'
> > Apr  7 16:41:37 lemon NetworkManager: <debug> [1207604497.366136]
> > nm_dbus_signal_filter(): NetworkManagerInfo triggered update of wireless
> > network 'slunet'
> > Apr  7 16:41:37 lemon NetworkManager: <info>  Old device 'wlan0'
> > activating, won't change.
> > Apr  7 16:41:53 lemon last message repeated 3 times
> 
> Could this be related to the the SCAN_CAPA patch as well? Seems like
> lots of lost ability to connect to 802.1x AP's is due to this kind of stuff.

It's mostly driver related issues that the SCAN_CAP NM patch fix in
concert with the kernel patch.  Having only the NM side of that will
still make NM use AP_SCAN=2, leading to probably failures in many
mac80211 drivers.

Dan