On Wed, Aug 08, 2007 at 11:02:35PM -0000, Peter Clifton wrote:
> NAK - Still broken here.
>
> ii network-manager 0.6.5-0ubuntu9 network management framework daemon
> ii network-manager-gnome 0.6.5-0ubuntu8 network management framework (GNOME frontend)
>
> (Is there an update pending for network-manager-gnome which is needed,
> and I've not got yet?)
>
> Symptom here is a failure to associate to the wep network, with repeated
> prompting for the password.
0.6.5-0ubuntu9 only approaches wpa-psk for ipw3945 in not-hidden networks ...
>
> Workaround is:
>
> sudo /etc/dbus-1/event.d/25NetworkManager stop
> gconftool-2 --recursive-unset /system/networking/wireless/networks/<NAME_OF_NETWORK>
> sudo /etc/dbus-1/event.d/25NetworkManager start
>
> It will then connect properly.
>
> I also noted that when on an unsecure network recently, I still had to
> do the RF-Kill Off / On whilst assocating trick. This "feels" like its
> becase the ipw3945 driver manages to associate to any unsecure network
> it finds (might / might not be correct) _without_ network manager, and
> network-manager causes it to un-associate. It then fails to associate
> correctly with the desired network, and the RF-Off /On cycle perhaps
> kicks the driver into finding something (Does it always find the one you
> asked for?).
>
On Wed, Aug 08, 2007 at 11:02:35PM -0000, Peter Clifton wrote: manager- gnome 0.6.5-0ubuntu8 network management framework (GNOME frontend) manager- gnome which is needed,
> NAK - Still broken here.
>
> ii network-manager 0.6.5-0ubuntu9 network management framework daemon
> ii network-
>
> (Is there an update pending for network-
> and I've not got yet?)
>
> Symptom here is a failure to associate to the wep network, with repeated
> prompting for the password.
0.6.5-0ubuntu9 only approaches wpa-psk for ipw3945 in not-hidden networks ...
> 1/event. d/25NetworkMana ger stop networking/ wireless/ networks/ <NAME_OF_ NETWORK> 1/event. d/25NetworkMana ger start
> Workaround is:
>
> sudo /etc/dbus-
> gconftool-2 --recursive-unset /system/
> sudo /etc/dbus-
>
> It will then connect properly.
>
> I also noted that when on an unsecure network recently, I still had to
> do the RF-Kill Off / On whilst assocating trick. This "feels" like its
> becase the ipw3945 driver manages to associate to any unsecure network
> it finds (might / might not be correct) _without_ network manager, and
> network-manager causes it to un-associate. It then fails to associate
> correctly with the desired network, and the RF-Off /On cycle perhaps
> kicks the driver into finding something (Does it always find the one you
> asked for?).
>
this is all for wep?
- Alexander