Re: When will 0.70 be released? / bug in 0.6.5

["Wander Winkelhorst" <w winkelhorst gmail com>]

On Jan 14, 2008 4:28 AM, Dan Williams <dcbw redhat com> wrote:

On Sun, 2008-01-13 at 11:07 +0100, Wander Winkelhorst wrote:
> Hi!
>
> I think I've found a bug in NM 0.6.5 where it marks AP's as invalid
> too agressivly. I've hacked around it and then I'd thought I'd check
> out SVN. The bug doesn't seem to be in the SVN version; the whole
> structure of the file is different.
>
> So when is version 0.7 going to be released? Or is there going to be a
> 0.6.6 ?

There will be a 0.6.6, and the stable branch will keep receiving fixes
for a while yet, probably until nobody is interested any more.

> What should I do with my patch? It seems like it's usefull (at least
> to me it is) but if 0.7 is going to be released very soon, I think I'd
> better spare myself and all of you the trouble of sending it in.

It wouldn't hurt to post the patch, or at least explain a little more
about the problem.

Hi,

I haven't actually solved the problems I'm experiencing, I think I've solved a few, but there seem to be even more problems that keep me from connecting.
Here's the things I've done allready to NM:

- I've increased a timeout value in nm-device-802-11-wireless.c (NM_SUPPLICANT_TIMEOUT from 20 to 40) which helps when activating
- in device-802-11-wireless.c I've uncommented the check for "invalid" AP's like this:
                if (nm_ap_list_get_ap_by_essid (app_data->invalid_ap_list, ap_essid)) {
                        nm_debug("ESSID %s is in the \"invalid\" list, not using it", ap_essid);
                        nm_debug("HACK!! STILL using it");
                        //continue;
                }

This seems to help keep a stable connection

This still isn't perfect or even good enough; I'm getting errors like:

NetworkManager: <debug> [1200644137.414459] nm_device_802_11_wireless_get_best_ap(): We have a link to this AP, keeping it
NetworkManager: <info>  AUTO: Best wired device = (null), best wireless device = eth1 (myap)
NetworkManager: <info>  eth1: link timed out.
NetworkManager: <debug> [1200644140.016129] nm_device_802_11_wireless_get_best_ap(): We have a link to this AP, keeping it
NetworkManager: <info>  AUTO: Best wired device = (null), best wireless device = eth1 (myap)
NetworkManager: <info>  SWITCH: found better connection 'eth1/myap' than current connection 'eth1/myap'.  same_ssid=1, have_link=0
NetworkManager: <info>  Will activate connection 'eth1/myap'.
NetworkManager: <info>  Device eth1 activation scheduled...
NetworkManager: <info>  Deactivating device eth1.
...
NetworkManager: <info>  Activation (eth1/wireless): access point 'myap' is encrypted, but NO valid key exists.  New key needed.
...
nm_dbus_get_user_key_for_network_cb(): nm_dbus_get_user_key_for_network_cb(): dbus returned an error.   (org.freedesktop.NetworkManagerInfo.GetKeyError) org.freedesktop.NetworkManagerInfo.GetKeyError
..
NetworkManager: <info>  Activation (eth1) failed.

I'm still chasing these bugs.

Hope this helps

Wander.