Cannot associate to Linksys WRE54G range expander

Bug #61505 reported by cleentrax
6
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: network-manager-gnome

I have an unsecured wifi network with a Linksys WRT54G router, and a Linksys WRE54G range expander.

Edgy will not connect to the network through the expander -- it will only connect through the router. I have tried this with three wifi adapters in Windows, and two wifi devices in Edgy. Windows can connect through the expander, which shows up with an SSID identical to the router's, but with a unique BSSID.

This appears to be a software issue, as the problem does not exist with the same hardware in Windows.

More info here:
http://ubuntuforums.org/showthread.php?t=260989

Revision history for this message
Scott Robinson (scott-ubuntu) wrote :

Can you give the results of an "iwlist scanning"?

Revision history for this message
Henrik Nilsen Omma (henrik) wrote : Re: [edgy] Cannot associate to Linksys WRE54G range expander

Closing this bug as it does not have information for us to start working on it. It would help if you could test this in Gutsy. We'll only be able to address most network-manager bugs in the latest release. Please re-open if you can confirm this in Gutsy and can supply more information. Thanks.

Changed in network-manager:
status: New → Invalid
Revision history for this message
Ursus (barrett-smithweb) wrote :

I can confirm this in Gutsy using network-manager version 0.6.5-0ubuntu16.7.10.0

The network in question is mixed b/g using a linksys wrt54g v8 router and wre54g ver 3 expander.

Output of `iwlist scanning` is attached, edited to remove other networks detected. Judging by location and signal quality, cell 06 in the listing is the expander and cell 01 is the router, though connection strength indicates that I was only able to connect to the router.

Ursus (barrett-smithweb)
Changed in network-manager:
status: Invalid → Confirmed
Revision history for this message
Alexander Sack (asac) wrote :

what we need here is a complete syslog taken _after_ reproducing the bug. can you still reproduce and attach that info? Thanks!

Changed in network-manager:
status: Confirmed → Incomplete
Revision history for this message
Daniel T Chen (crimsun) wrote :

I cannot reproduce the symptom on 8.10 and my hardware.

Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in network-manager:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.