Re: Problems with ipw3945
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexander Sack wrote: > On Wed, Nov 28, 2007 at 05:16:14PM -0500, Dan Williams wrote: >> On Wed, 2007-11-28 at 23:07 +0100, Martin Ginkel wrote: >>> Hi, >>> >>> on my notebook I'm trying to user NM to access wireless networks. >>> There is a larger problem with setting essids and >>> associating/disassociating >>> to APs. >> 0.6.5, right? >> >>> Apparently the card assumes to interpret the essid "" (empty) to be *any*. >> Yeah, that's the standard behavior. >> >>> Therefore it associates immediately to the next ap. >>> I watched this with iwevent. >>> Nm first sets the essid to "" to disassociate, later it sets the id, I >>> selected >>> in the menu. But the card is already associated by the "" setting and >>> NM waits forever for an association event after setting the id. >> Well, the driver needs to send the association event whenever it gets an >> association request, even if that association request is for the same AP >> that it's already associated with. This seems like a driver bug to me. >> Association requests must always be followed by either a failed >> association event, or a valid associated AP event. It sounds like the >> ipw3945 driver isn't doing that. >> > > This is a drivers bug. We have a fix for that in ubuntu. You can find > it in: > > https://code.launchpad.net/~asac/intellinuxwireless/ipw3945.asac > > the commit of revision 2 is what you want. In which releases of Ubuntu does that fix appear? - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II |$&| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHTtQHmb+gadEcsb4RAn9sAJ4pKkJD86VR2D9eQ364O5VNydAmQwCfaBsC niF+xVbNyIgWghqjuQtvSFA= =u0Ih -END PGP SIGNATURE- ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems with ipw3945
On Thu, Nov 29, 2007 at 10:00:23AM -0500, Ryan Novosielski wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Alexander Sack wrote: > > On Wed, Nov 28, 2007 at 05:16:14PM -0500, Dan Williams wrote: > >> On Wed, 2007-11-28 at 23:07 +0100, Martin Ginkel wrote: > >>> Hi, > >>> > >>> on my notebook I'm trying to user NM to access wireless networks. > >>> There is a larger problem with setting essids and > >>> associating/disassociating > >>> to APs. > >> 0.6.5, right? > >> > >>> Apparently the card assumes to interpret the essid "" (empty) to be *any*. > >> Yeah, that's the standard behavior. > >> > >>> Therefore it associates immediately to the next ap. > >>> I watched this with iwevent. > >>> Nm first sets the essid to "" to disassociate, later it sets the id, I > >>> selected > >>> in the menu. But the card is already associated by the "" setting and > >>> NM waits forever for an association event after setting the id. > >> Well, the driver needs to send the association event whenever it gets an > >> association request, even if that association request is for the same AP > >> that it's already associated with. This seems like a driver bug to me. > >> Association requests must always be followed by either a failed > >> association event, or a valid associated AP event. It sounds like the > >> ipw3945 driver isn't doing that. > >> > > > > This is a drivers bug. We have a fix for that in ubuntu. You can find > > it in: > > > > https://code.launchpad.net/~asac/intellinuxwireless/ipw3945.asac > > > > the commit of revision 2 is what you want. > > In which releases of Ubuntu does that fix appear? > gutsy and hardy iirc. - Alexander ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems with ipw3945
On Wed, Nov 28, 2007 at 05:16:14PM -0500, Dan Williams wrote: > On Wed, 2007-11-28 at 23:07 +0100, Martin Ginkel wrote: > > Hi, > > > > on my notebook I'm trying to user NM to access wireless networks. > > There is a larger problem with setting essids and > > associating/disassociating > > to APs. > > 0.6.5, right? > > > Apparently the card assumes to interpret the essid "" (empty) to be *any*. > > Yeah, that's the standard behavior. > > > Therefore it associates immediately to the next ap. > > I watched this with iwevent. > > Nm first sets the essid to "" to disassociate, later it sets the id, I > > selected > > in the menu. But the card is already associated by the "" setting and > > NM waits forever for an association event after setting the id. > > Well, the driver needs to send the association event whenever it gets an > association request, even if that association request is for the same AP > that it's already associated with. This seems like a driver bug to me. > Association requests must always be followed by either a failed > association event, or a valid associated AP event. It sounds like the > ipw3945 driver isn't doing that. > This is a drivers bug. We have a fix for that in ubuntu. You can find it in: https://code.launchpad.net/~asac/intellinuxwireless/ipw3945.asac the commit of revision 2 is what you want. - Alexander ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems with ipw3945
On Wed, 2007-11-28 at 23:07 +0100, Martin Ginkel wrote: > Hi, > > on my notebook I'm trying to user NM to access wireless networks. > There is a larger problem with setting essids and > associating/disassociating > to APs. 0.6.5, right? > Apparently the card assumes to interpret the essid "" (empty) to be *any*. Yeah, that's the standard behavior. > Therefore it associates immediately to the next ap. > I watched this with iwevent. > Nm first sets the essid to "" to disassociate, later it sets the id, I > selected > in the menu. But the card is already associated by the "" setting and > NM waits forever for an association event after setting the id. Well, the driver needs to send the association event whenever it gets an association request, even if that association request is for the same AP that it's already associated with. This seems like a driver bug to me. Association requests must always be followed by either a failed association event, or a valid associated AP event. It sounds like the ipw3945 driver isn't doing that. Dan > > The current lousy workaround is to set an ID "blurp" manually after NM > set "". > Then the card will generate the events correctly. > > Would it be difficult to poll the status of the card first, before > waiting for the events? > > > Best regards > Martin > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Problems with ipw3945
Hi, on my notebook I'm trying to user NM to access wireless networks. There is a larger problem with setting essids and associating/disassociating to APs. Apparently the card assumes to interpret the essid "" (empty) to be *any*. Therefore it associates immediately to the next ap. I watched this with iwevent. Nm first sets the essid to "" to disassociate, later it sets the id, I selected in the menu. But the card is already associated by the "" setting and NM waits forever for an association event after setting the id. The current lousy workaround is to set an ID "blurp" manually after NM set "". Then the card will generate the events correctly. Would it be difficult to poll the status of the card first, before waiting for the events? Best regards Martin ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
