*** This bug is a duplicate of bug 50214 ***
https://bugs.launchpad.net/bugs/50214
Matthew,
I'm astounded by this whole experience. This doesn't seem to be an easy bug
to track down. I've spent a fair amount of time on this myself and don't
completely grok the problem, other than I suspect it is some sort of race
condition/timing error/insufficient necessary conditions checking between
iwconfig actually completing the AP association and ifup bringing up the
interface (told you I was confused). This would explain the differences in
the behavior of NetworkManager among the network cards - it's the drivers
for the cards themselves that differ in this situation. Therein lies the
big problem with wireless on Linux in general - too many cards with too many
different ways of bringing them to life. You've got everything from
completely open source drivers like the Ralink stuff to the Atheros closed
source HAL to the fwcutter requirement for the firmware for the Broadcom
cards to ndiswrapper for the mongrels. There are a lot of paths here that
may need to be explored and eventually need to be consolidated. Frankly,
I'm shocked that NetworkManager works as well as it does. That being said,
it's just not yet good enough - it doesn't "Just Work" (tm).
I'm probably going to uncloak my AP to get around this right now. With
tools like Kismet that's a pretty weak defense anyway. But I have clients
that still require cloaked APs as part of their approved security measures.
This issue really needs a lot more attention than it's been given over the
last year or so. I'm afraid that it's working well enough for most folks
that it's dropped off the priority list for the Powers That Be (tm). It
really needs to be pushed through to completion.
Tom
On 9/10/07, Matthew Carpenter <[EMAIL PROTECTED]> wrote:
>
> *** This bug is a duplicate of bug 50214 ***
> https://bugs.launchpad.net/bugs/50214
>
> On Monday 10 September 2007, Tom Wood wrote:
> > *** This bug is a duplicate of bug 50214 ***
> > https://bugs.launchpad.net/bugs/50214
> >
> > Color me confused. This has now been marked as a dupe of bug # 50214.
> > What I find most interesting is that with any other wireless NIC that I
> > have, this is *not* a problem, just with this Atheros PCI-based NIC that
> > has the same chipset in it as a PCMCIA-based NIC from the same
> > manufacturer (Netgear WG311T is PCI and the PCMCIA is a WG511T). One
> > Broadcom NIC that I have (Linksys WMP54GS) works without a hitch on this
> > network. So do my Orinoco Classic Gold 802.11b-only PCMCIA NICs. And
> > last, but not least, my Broadcom-based Compaq NX9010 (Broadcom BCM4306)
> > works like a charm against this cloaked network under Feisty. Only the
> > WG311T does not work without the ifup/ifdown.
> >
> > Under Feisty and Gutsy, the only two versions I've tried, the WG311T
> > requires the ifup/ifdown trick to work. Maybe that's a good clue to
> > start figuring out what's wrong with NetworkManager, if indeed that is
> > the culprit. To repeat, all my other wireless NICs work fine against my
> > cloaked network under either Edgy or Feisty.
> >
> > Thanks for looking into this, Alexander. It will be fantastic when we
> > finally get to put this one to rest.
>
> I'm having this issue with an IPW3945 using WPA on Feisty, so this is not
> an
> Atheros bug only.
> What's disturbing is that the bug has been around for a year and it is
> still
> undecided how important it is!
>
> --
> NetworkManager fails to finish association to AP
> https://bugs.launchpad.net/bugs/133966
> You received this bug notification because you are a direct subscriber
> of the bug.
>
--
NetworkManager fails to finish association to AP
https://bugs.launchpad.net/bugs/133966
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
