Ticket #5401 (closed defect: duplicate)

Opened 7 years ago

Last modified 7 years ago

My XO does not associate with my access point

Reported by: paulproteus Owned by: mbletsas
Priority: high Milestone: Update.1
Component: wireless Version:
Keywords: Cc: jcardona, chockshi, tomeu
Action Needed: Verified: no
Deployments affected: Blocked By:
Blocking:

Description

At Creative Commons, we are using a Linksys WRT54GL. The XO I am using is a BTest4 and I am running stable build 650. The Linksys box serving as the access point is running OpenWRT Kamikaze, some stock stable release (I can get details if necessary).

I go to the broadest zoom level and click on the circle labeled Creative Commons. I am told that a wireless encryption key is required, which is true. I select "Hex" and enter the hex representation of our key, but the XO never connections; the circle remains blinking. So I try entering the ascii version, and get the same problem.

tomeu on #sugar suggested I file a bug. (-:

Change History

Changed 7 years ago by jg

  • owner changed from jg to mbletsas
  • cc jcardona, chockshi added
  • priority changed from normal to high
  • component changed from distro to wireless
  • milestone changed from Never Assigned to Update.1

Changed 7 years ago by mbletsas

  • status changed from new to closed
  • resolution set to duplicate

Jim,

We are already tracking that as a Sugar issue, please let's not open more bugs for existing well understood issues.

M.

Changed 7 years ago by paulproteus

For what it's worth, I did try setting the parameters in iwconfig in a Terminal to no effect.

If this is a duplicate, what is the ticket # for the dup?

Changed 7 years ago by mbletsas

#5044 and #5351 come immediately to mind

M.

Changed 7 years ago by paulproteus

#5044 is not the same - the UI handles the clicks fine, it's just that the icon blinks forever and the XO doesn't seem to associate. In #5044, the dialog never accepts the "OK" click, as I read it.

I can wait for #5351 to land if you insist, but I believe my problem is unrelated to these UI issues.

Changed 7 years ago by tomeu

  • cc tomeu added

I don't really see this as being a Sugar problem.

I'm afraid this ticket has been closed too swiftly, I don't think we should be wasting opportunities of knowing more how our system behaves in different environments.

Note: See TracTickets for help on using tickets.