'old' bssid's causing problems wireless?

Bug #270719 reported by ThudsFlauntedPhiltres
4
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

Ubuntu Hardy. on macbook

connecting to wireless network (802.1X ) using the following options

TTLS
Dynamic WEP
PAP
username
passwd

There are 5 bssids for the different accesss points. It seems that as I accumulate access points, I can't get back on the network.

In this particular instance
doing iwlist ath0 ap
shows that I see two acess points (00:12:...) in the screen shot and that I have four bssids stored in my profile.

It seems that I cannot reconnect until I remove the 'old' bssid's from the profile. It seems like the wireless software is not making it through the list of bssids or something.

I have done this a number of times but I don't really know enough about how this stuff works to rule out coincidence ... i.e. maybe I just fiddle with stuff until the wireless is back on and I think I fixed it by my fiddling.

Any advice on making this report more useful? I will only be on this wireless network for another week or so.

screenshots of the bssid editor and iwcofig ath0 ap output follow.

Revision history for this message
ThudsFlauntedPhiltres (mathtick) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Could you try to reproduce the same with Ubuntu 8.10 or 9.04? Thanks in advance.

Changed in network-manager:
status: New → Incomplete
Revision history for this message
ThudsFlauntedPhiltres (mathtick) wrote : Re: [Bug 270719] Re: 'old' bssid's causing problems wireless?

I'm not around the same wireless network so I haven't noticed the problem
occuring ... I am still having disconnects but I'll have to look into it to
see if the symptoms look to be similar.

On Thu, Jan 15, 2009 at 8:21 AM, Pedro Villavicencio <email address hidden>wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug a while ago and there hasn't been
> any activity in it recently. We were wondering is this still an issue
> for you? Could you try to reproduce the same with Ubuntu 8.10 or 9.04?
> Thanks in advance.
>
> ** Changed in: network-manager (Ubuntu)
> Status: New => Incomplete
>
> --
> 'old' bssid's causing problems wireless?
> https://bugs.launchpad.net/bugs/270719
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "network-manager" source package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: network-manager
>
> Ubuntu Hardy. on macbook
>
> connecting to wireless network (802.1X ) using the following options
>
> TTLS
> Dynamic WEP
> PAP
> username
> passwd
>
> There are 5 bssids for the different accesss points. It seems that as I
> accumulate access points, I can't get back on the network.
>
> In this particular instance
> doing iwlist ath0 ap
> shows that I see two acess points (00:12:...) in the screen shot and that I
> have four bssids stored in my profile.
>
> It seems that I cannot reconnect until I remove the 'old' bssid's from the
> profile. It seems like the wireless software is not making it through the
> list of bssids or something.
>
> I have done this a number of times but I don't really know enough about how
> this stuff works to rule out coincidence ... i.e. maybe I just fiddle with
> stuff until the wireless is back on and I think I fixed it by my fiddling.
>
> Any advice on making this report more useful? I will only be on this
> wireless network for another week or so.
>
> screenshots of the bssid editor and iwcofig ath0 ap output follow.
>

Revision history for this message
TehMwak (i-like-to-use) wrote :

I am running ubuntu 9.04 and upgrade it daily. I also have the same problem with my EEEpc 900ha. I'm going to see if I can also replicate it on my desktop pc running 8.10.

Revision history for this message
Victor Vargas (kamus) 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 (Ubuntu):
status: Incomplete → Invalid
tags: added: encryption-wep
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.