Comment 106 for bug 121439

I'm not near an open network to try, but are open networks still an issue? They appeared to be a few days ago last time I tried to use one (2007-08-23).

Seems the network card associates before NW manager asks it to. Digging at the ipw3945 sourcecode, there is an option for that behaviour:

module_param(associate, int, 0444);
MODULE_PARM_DESC(associate, "auto associate when scanning (default 0 off)");

There is also an option to auto-create an ad-hoc network if needed, default as on.

If the card "appears" to be associating to some open networks without network manager asking it, is there:

 a) Some bug in the driver ignoring this option
 b) Some bug in NW manager actually asking for the assocation
 c) Some other script causing the association or setting this parameter when loading ipw3945

Could I request that when a fix is released, some technical details of what that was, or what the problem is believed to be is posted.
Perhaps a link to a commit in http://kernel.ubuntu.com/git or some other SCM where changes are made?

I realise that for Fiesty and other released versions this is less important, and many users won't care about these details, but for Gutsy (or any development branch) bug reports, I can imagine the people testing might be interested in the debugging process. Whilst I'm much more familiar developing / debugging GTK+ applications, I do try and read the sources / follow fixes for any bug I encounter as a way of learning from those who know enough solve the problem.

Kind regards,
Peter Clifton