| 2014-03-08 11:00:19 |
LennartP |
bug |
|
|
added bug |
| 2014-05-08 20:06:00 |
Launchpad Janitor |
broadcom-sta (Ubuntu): status |
New |
Confirmed |
|
| 2014-10-29 19:06:50 |
penalvch |
broadcom-sta (Ubuntu): status |
Confirmed |
Incomplete |
|
| 2014-11-06 07:23:14 |
auriza |
bug |
|
|
added subscriber auriza |
| 2014-11-06 22:05:43 |
penalvch |
tags |
|
amd64 latest-bios-209 saucy trusty |
|
| 2014-11-06 22:12:12 |
penalvch |
description |
1) lsb_release -rd
Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04
N.B: The same problem existed in 13.10 with this computer about a month ago.
2) From software center: broadcom-sta-source 6.30.223.141-1.
3) What i expected to happen: Once the driver connects to my AP at home, i expect it to forward IP-packets between the AP and my computer.
4) What happened instead: Almost nothing. There is a valid ARP entry for the AP in the ARP cache, but there are no replies from ping.
The AP is a DLINK DIR-645. I've got two Android devices of different versions using the AP w/o problems, so the AP is not broken. The driver works with an AP from Huawei. This computer has been able to use the AP w/o problems running 12.04 until abount six months ago, when no longer connect to it. |
1) lsb_release -rd
Description: Ubuntu 14.04.1 LTS
Release: 14.04
2) apt-cache policy broadcom-sta-source
broadcom-sta-source:
Installed: 6.30.223.141-1
Candidate: 6.30.223.141-1
Version table:
*** 6.30.223.141-1 0
500 http://se.archive.ubuntu.com/ubuntu/ trusty/multiverse amd64 Packages
100 /var/lib/dpkg/status
3) What is expected to happen with my Asus 1225B-SIV047M laptop and DLINK DIR-645 AP is the WiFi works via the broadcom-sta-source driver.
4) What happened instead: Almost nothing. There is a valid ARP entry for the AP in the ARP cache, but there are no replies from ping. The same problem existed in 13.10 with this computer about a month ago. However, this computer has been able to use the AP w/o problems running 12.04 until about six months ago, when no longer connect to it.
I have two Android devices of different versions using the AP w/o problems.
However, the driver works with an AP from Huawei.
uname -a
Linux slim2a 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
lspci -vvnn | grep -A 9 Network
04:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter [14e4:4727] (rev 01)
Subsystem: AzureWave Device [1a3b:2047]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at fea00000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: wl
sudo dmidecode -s bios-version
209
sudo dmidecode -s bios-release-date
06/05/2012 |
|
| 2014-11-06 22:22:50 |
penalvch |
summary |
BCM4313 not working with some wireless AP |
14e4:4727 [Asus 1225B] BCM4313 not working with D-Link DIR-645 AP |
|
| 2014-11-06 22:23:16 |
penalvch |
broadcom-sta (Ubuntu): importance |
Undecided |
Medium |
|
| 2014-11-09 18:17:02 |
penalvch |
description |
1) lsb_release -rd
Description: Ubuntu 14.04.1 LTS
Release: 14.04
2) apt-cache policy broadcom-sta-source
broadcom-sta-source:
Installed: 6.30.223.141-1
Candidate: 6.30.223.141-1
Version table:
*** 6.30.223.141-1 0
500 http://se.archive.ubuntu.com/ubuntu/ trusty/multiverse amd64 Packages
100 /var/lib/dpkg/status
3) What is expected to happen with my Asus 1225B-SIV047M laptop and DLINK DIR-645 AP is the WiFi works via the broadcom-sta-source driver.
4) What happened instead: Almost nothing. There is a valid ARP entry for the AP in the ARP cache, but there are no replies from ping. The same problem existed in 13.10 with this computer about a month ago. However, this computer has been able to use the AP w/o problems running 12.04 until about six months ago, when no longer connect to it.
I have two Android devices of different versions using the AP w/o problems.
However, the driver works with an AP from Huawei.
uname -a
Linux slim2a 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
lspci -vvnn | grep -A 9 Network
04:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter [14e4:4727] (rev 01)
Subsystem: AzureWave Device [1a3b:2047]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at fea00000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: wl
sudo dmidecode -s bios-version
209
sudo dmidecode -s bios-release-date
06/05/2012 |
1) lsb_release -rd
Description: Ubuntu 14.04.1 LTS
Release: 14.04
2) apt-cache policy broadcom-sta-source
broadcom-sta-source:
Installed: 6.30.223.141-1
Candidate: 6.30.223.141-1
Version table:
*** 6.30.223.141-1 0
500 http://se.archive.ubuntu.com/ubuntu/ trusty/multiverse amd64 Packages
100 /var/lib/dpkg/status
3) What is expected to happen with my Asus 1225B-SIV047M laptop and DLINK DIR-645 AP is the WiFi works via the broadcom-sta-source driver.
4) What happened instead: Almost nothing. There is a valid ARP entry for the AP in the ARP cache, but there are no replies from ping. The same problem existed in 13.10 with this computer about a month ago. However, this computer has been able to use the AP w/o problems running 12.04 until about six months ago, when no longer connect to it. I tried upgrading the AP firmware to 1.04 B12 but this didn't change anything.
I have two Android devices of different versions using the AP without problems.
However, the wifi works with an AP from Huawei.
uname -a
Linux slim2a 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
lspci -vvnn | grep -A 9 Network
04:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter [14e4:4727] (rev 01)
Subsystem: AzureWave Device [1a3b:2047]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at fea00000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: wl
sudo dmidecode -s bios-version
209
sudo dmidecode -s bios-release-date
06/05/2012 |
|
| 2015-01-07 00:01:43 |
penalvch |
affects |
broadcom-sta (Ubuntu) |
bcmwl (Ubuntu) |
|
| 2015-01-07 00:01:43 |
penalvch |
bcmwl (Ubuntu): status |
Incomplete |
Fix Released |
|
| 2015-01-11 14:56:21 |
LennartP |
description |
1) lsb_release -rd
Description: Ubuntu 14.04.1 LTS
Release: 14.04
2) apt-cache policy broadcom-sta-source
broadcom-sta-source:
Installed: 6.30.223.141-1
Candidate: 6.30.223.141-1
Version table:
*** 6.30.223.141-1 0
500 http://se.archive.ubuntu.com/ubuntu/ trusty/multiverse amd64 Packages
100 /var/lib/dpkg/status
3) What is expected to happen with my Asus 1225B-SIV047M laptop and DLINK DIR-645 AP is the WiFi works via the broadcom-sta-source driver.
4) What happened instead: Almost nothing. There is a valid ARP entry for the AP in the ARP cache, but there are no replies from ping. The same problem existed in 13.10 with this computer about a month ago. However, this computer has been able to use the AP w/o problems running 12.04 until about six months ago, when no longer connect to it. I tried upgrading the AP firmware to 1.04 B12 but this didn't change anything.
I have two Android devices of different versions using the AP without problems.
However, the wifi works with an AP from Huawei.
uname -a
Linux slim2a 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
lspci -vvnn | grep -A 9 Network
04:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter [14e4:4727] (rev 01)
Subsystem: AzureWave Device [1a3b:2047]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at fea00000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: wl
sudo dmidecode -s bios-version
209
sudo dmidecode -s bios-release-date
06/05/2012 |
[Impact]
Users of Ubuntu 14.04 with bcmwl are unable to utilize WiFi with the D-Link DIR-645 AP (AccessPoint). |
|
| 2015-01-11 14:58:59 |
LennartP |
description |
[Impact]
Users of Ubuntu 14.04 with bcmwl are unable to utilize WiFi with the D-Link DIR-645 AP (AccessPoint). |
[Impact]
Users of Ubuntu 14.04 with bcmwl are unable to utilize WiFi with the D-Link DIR-645 AP (AccessPoint). They are able to connect to the AP using WPA2-PSK and obtain an IP address from the AP, but no IP unicast packets are evere received. Thus, WiFi is for all practical purposes not working for this combination of Ubuntu software and AP. |
|
| 2015-01-11 15:02:13 |
LennartP |
description |
[Impact]
Users of Ubuntu 14.04 with bcmwl are unable to utilize WiFi with the D-Link DIR-645 AP (AccessPoint). They are able to connect to the AP using WPA2-PSK and obtain an IP address from the AP, but no IP unicast packets are evere received. Thus, WiFi is for all practical purposes not working for this combination of Ubuntu software and AP. |
[Impact]
Users of Ubuntu 14.04 with bcmwl are unable to utilize WiFi with the D-Link DIR-645 AP (AccessPoint). They are able to connect to the AP using WPA2-PSK and obtain an IP address from the AP, but no IP unicast packets are evere received. Thus, WiFi is for all practical purposes not working for this combination of Ubuntu software and AP.
While this is happening, devices using other software (e.g. Android) are able to utilize WiFi with the same AP without problems.
The bug can also be reproduced using the ASUS WL-330N AP. There may be other APs with which the bug can also be reproduced. |
|
| 2015-01-11 15:03:49 |
LennartP |
description |
[Impact]
Users of Ubuntu 14.04 with bcmwl are unable to utilize WiFi with the D-Link DIR-645 AP (AccessPoint). They are able to connect to the AP using WPA2-PSK and obtain an IP address from the AP, but no IP unicast packets are evere received. Thus, WiFi is for all practical purposes not working for this combination of Ubuntu software and AP.
While this is happening, devices using other software (e.g. Android) are able to utilize WiFi with the same AP without problems.
The bug can also be reproduced using the ASUS WL-330N AP. There may be other APs with which the bug can also be reproduced. |
[Impact]
Users of Ubuntu 14.04 with bcmwl are unable to utilize WiFi with the D-Link DIR-645 AP (AccessPoint). They are able to connect to the AP using WPA2-PSK and obtain an IP address from the AP, but no IP unicast packets are evere received. Thus, WiFi is for all practical purposes not working for this combination of Ubuntu software and AP.
While this is happening, devices using other software (e.g. Android) are able to utilize WiFi with the same AP without problems.
The bug can also be reproduced using the ASUS WL-330N AP. There may be other APs with which the bug can also be reproduced.
The bug was not present in Ubuntu 12.04. It is fixed in Ubuntu Vivid Vervet. |
|
| 2015-01-11 15:06:14 |
LennartP |
description |
[Impact]
Users of Ubuntu 14.04 with bcmwl are unable to utilize WiFi with the D-Link DIR-645 AP (AccessPoint). They are able to connect to the AP using WPA2-PSK and obtain an IP address from the AP, but no IP unicast packets are evere received. Thus, WiFi is for all practical purposes not working for this combination of Ubuntu software and AP.
While this is happening, devices using other software (e.g. Android) are able to utilize WiFi with the same AP without problems.
The bug can also be reproduced using the ASUS WL-330N AP. There may be other APs with which the bug can also be reproduced.
The bug was not present in Ubuntu 12.04. It is fixed in Ubuntu Vivid Vervet. |
[Impact]
Users of Ubuntu 14.04 with bcmwl are unable to utilize WiFi with the D-Link DIR-645 AP (AccessPoint). They are able to connect to the AP using WPA2-PSK and obtain an IP address from the AP, but no IP unicast packets are evere received. Thus, WiFi is for all practical purposes not working for this combination of Ubuntu software and AP.
While this is happening, devices using other software (e.g. Android) are able to utilize WiFi with the same AP without problems.
The bug can also be reproduced using the ASUS WL-330N AP. There may be other APs with which the bug can also be reproduced.
The bug was not present in Ubuntu 12.04. It is fixed in Ubuntu Vivid Vervet.
The bug should be back-ported to Ubuntu 14.04 because WiFi is a fundamental function for laptops which has worked in Ubuntu LTS before. Speaking for myself, I am reluctant to move to a development release of Ubuntu such as Vivid because problems are to be expected with applications running on top of Ubuntu, e.g. Virtualbox, in such a release. |
|
| 2015-01-11 15:13:13 |
LennartP |
description |
[Impact]
Users of Ubuntu 14.04 with bcmwl are unable to utilize WiFi with the D-Link DIR-645 AP (AccessPoint). They are able to connect to the AP using WPA2-PSK and obtain an IP address from the AP, but no IP unicast packets are evere received. Thus, WiFi is for all practical purposes not working for this combination of Ubuntu software and AP.
While this is happening, devices using other software (e.g. Android) are able to utilize WiFi with the same AP without problems.
The bug can also be reproduced using the ASUS WL-330N AP. There may be other APs with which the bug can also be reproduced.
The bug was not present in Ubuntu 12.04. It is fixed in Ubuntu Vivid Vervet.
The bug should be back-ported to Ubuntu 14.04 because WiFi is a fundamental function for laptops which has worked in Ubuntu LTS before. Speaking for myself, I am reluctant to move to a development release of Ubuntu such as Vivid because problems are to be expected with applications running on top of Ubuntu, e.g. Virtualbox, in such a release. |
[Impact]
Users of Ubuntu 14.04 with bcmwl are unable to utilize WiFi with the D-Link DIR-645 AP (AccessPoint). They are able to connect to the AP using WPA2-PSK and obtain an IP address from the AP, but no IP unicast packets are ever received. Thus, WiFi is for all practical purposes not working for this combination of Ubuntu software and AP.
While this is happening, devices using other software (e.g. Android) are able to utilize WiFi with the same AP without problems.
The bug can also be reproduced using the ASUS WL-330N AP. There may be other APs with which the bug can also be reproduced.
The bug was not present in Ubuntu 12.04. It is fixed in Ubuntu Vivid Vervet.
The bug should be back-ported to Ubuntu 14.04 because WiFi is a fundamental function for laptops which has worked in Ubuntu LTS before. Speaking for myself, I am reluctant to move to a development release of Ubuntu such as Vivid because problems are to be expected with applications running on top of Ubuntu, e.g. Virtualbox, in such a release.
[Test Case]
DUT :== Device Under Test, a laptop with Ubuntu 14.04 and bcmwl installed.
1. Ascertain no other network connection (e.g. wired Ethernet) are connected to DUT.
2. Connect DUT to av D-Link DIR-645 or ASUS WL-330N AP using WPA2-PSK.
3. Open a Terminal and do at least one of the following:
3a. Determine the IP address of the default gateway ("destination 0.0.0.0") using netstat -rn and ping the IP-address. |
|
| 2015-01-11 15:17:45 |
LennartP |
description |
[Impact]
Users of Ubuntu 14.04 with bcmwl are unable to utilize WiFi with the D-Link DIR-645 AP (AccessPoint). They are able to connect to the AP using WPA2-PSK and obtain an IP address from the AP, but no IP unicast packets are ever received. Thus, WiFi is for all practical purposes not working for this combination of Ubuntu software and AP.
While this is happening, devices using other software (e.g. Android) are able to utilize WiFi with the same AP without problems.
The bug can also be reproduced using the ASUS WL-330N AP. There may be other APs with which the bug can also be reproduced.
The bug was not present in Ubuntu 12.04. It is fixed in Ubuntu Vivid Vervet.
The bug should be back-ported to Ubuntu 14.04 because WiFi is a fundamental function for laptops which has worked in Ubuntu LTS before. Speaking for myself, I am reluctant to move to a development release of Ubuntu such as Vivid because problems are to be expected with applications running on top of Ubuntu, e.g. Virtualbox, in such a release.
[Test Case]
DUT :== Device Under Test, a laptop with Ubuntu 14.04 and bcmwl installed.
1. Ascertain no other network connection (e.g. wired Ethernet) are connected to DUT.
2. Connect DUT to av D-Link DIR-645 or ASUS WL-330N AP using WPA2-PSK.
3. Open a Terminal and do at least one of the following:
3a. Determine the IP address of the default gateway ("destination 0.0.0.0") using netstat -rn and ping the IP-address. |
[Impact]
Users of Ubuntu 14.04 with bcmwl are unable to utilize WiFi with the D-Link DIR-645 AP (AccessPoint). They are able to connect to the AP using WPA2-PSK and obtain an IP address from the AP, but no IP unicast packets are ever received. Thus, WiFi is for all practical purposes not working for this combination of Ubuntu software and AP.
While this is happening, devices using other software (e.g. Android) are able to utilize WiFi with the same AP without problems.
The bug can also be reproduced using the ASUS WL-330N AP. There may be other APs with which the bug can also be reproduced.
The bug was not present in Ubuntu 12.04. It is fixed in Ubuntu Vivid Vervet.
The bug should be back-ported to Ubuntu 14.04 because WiFi is a fundamental function for laptops which has worked in Ubuntu LTS before. Speaking for myself, I am reluctant to move to a development release of Ubuntu such as Vivid because problems are to be expected with applications running on top of Ubuntu, e.g. Virtualbox, in such a release.
[Test Case]
DUT :== Device Under Test, a laptop with Ubuntu 14.04 and bcmwl installed.
1. Ascertain no other network connection (e.g. wired Ethernet) are connected to DUT.
2. Connect DUT to av D-Link DIR-645 or ASUS WL-330N AP using WPA2-PSK.
3. Open a Terminal and do at least one of the following:
3a. Determine the IP address of the default gateway ("destination 0.0.0.0") using netstat -rn and ping the IP-address.
3b. Ping the IP address of some other device connected to the same AP. Optionally, use a protocol analyzer (e.g. WireShark) to observe ping packets being received by the other device from DUT and responses being sent back.
4a. If the buig is fixed, you should see lines like "64 bytes received from <IP |
|
| 2015-01-11 15:20:17 |
LennartP |
description |
[Impact]
Users of Ubuntu 14.04 with bcmwl are unable to utilize WiFi with the D-Link DIR-645 AP (AccessPoint). They are able to connect to the AP using WPA2-PSK and obtain an IP address from the AP, but no IP unicast packets are ever received. Thus, WiFi is for all practical purposes not working for this combination of Ubuntu software and AP.
While this is happening, devices using other software (e.g. Android) are able to utilize WiFi with the same AP without problems.
The bug can also be reproduced using the ASUS WL-330N AP. There may be other APs with which the bug can also be reproduced.
The bug was not present in Ubuntu 12.04. It is fixed in Ubuntu Vivid Vervet.
The bug should be back-ported to Ubuntu 14.04 because WiFi is a fundamental function for laptops which has worked in Ubuntu LTS before. Speaking for myself, I am reluctant to move to a development release of Ubuntu such as Vivid because problems are to be expected with applications running on top of Ubuntu, e.g. Virtualbox, in such a release.
[Test Case]
DUT :== Device Under Test, a laptop with Ubuntu 14.04 and bcmwl installed.
1. Ascertain no other network connection (e.g. wired Ethernet) are connected to DUT.
2. Connect DUT to av D-Link DIR-645 or ASUS WL-330N AP using WPA2-PSK.
3. Open a Terminal and do at least one of the following:
3a. Determine the IP address of the default gateway ("destination 0.0.0.0") using netstat -rn and ping the IP-address.
3b. Ping the IP address of some other device connected to the same AP. Optionally, use a protocol analyzer (e.g. WireShark) to observe ping packets being received by the other device from DUT and responses being sent back.
4a. If the buig is fixed, you should see lines like "64 bytes received from <IP |
[Impact]
Users of Ubuntu 14.04 with bcmwl are unable to utilize WiFi with the D-Link DIR-645 AP (AccessPoint). They are able to connect to the AP using WPA2-PSK and obtain an IP address from the AP, but no IP unicast packets are ever received. Thus, WiFi is for all practical purposes not working for this combination of Ubuntu software and AP.
While this is happening, devices using other software (e.g. Android) are able to utilize WiFi with the same AP without problems.
The bug can also be reproduced using the ASUS WL-330N AP. There may be other APs with which the bug can also be reproduced.
The bug was not present in Ubuntu 12.04. It is fixed in Ubuntu Vivid Vervet.
The bug should be back-ported to Ubuntu 14.04 because WiFi is a fundamental function for laptops which has worked in Ubuntu LTS before. Speaking for myself, I am reluctant to move to a development release of Ubuntu such as Vivid because problems are to be expected with applications running on top of Ubuntu, e.g. Virtualbox, in such a release.
[Test Case]
DUT :== Device Under Test, a laptop with Ubuntu 14.04 and bcmwl installed.
1. Ascertain no other network connection (e.g. wired Ethernet) are connected to DUT.
2. Connect DUT to av D-Link DIR-645 or ASUS WL-330N AP using WPA2-PSK.
3. Open a Terminal and do at least one of the following:
3a. Determine the IP address of the default gateway ("destination 0.0.0.0") using netstat -rn and ping the IP-address.
3b. Ping the IP address of some other device connected to the same AP. Optionally, use a protocol analyzer (e.g. WireShark) to observe ping packets being received by the other device from DUT and responses being sent back.
4a. If the buig is fixed, you should see lines like "64 bytes received from <IP-address>" in your terminal. After pressing CTRL+C, ping should report "0% packet loss".
4b. If the bug is not fixed, ping just writes "PING <IP-address> ..." and nothing else happens. After pressing CTRL+C, ping reports "100% packet loss". |
|
| 2015-01-11 15:25:05 |
LennartP |
description |
[Impact]
Users of Ubuntu 14.04 with bcmwl are unable to utilize WiFi with the D-Link DIR-645 AP (AccessPoint). They are able to connect to the AP using WPA2-PSK and obtain an IP address from the AP, but no IP unicast packets are ever received. Thus, WiFi is for all practical purposes not working for this combination of Ubuntu software and AP.
While this is happening, devices using other software (e.g. Android) are able to utilize WiFi with the same AP without problems.
The bug can also be reproduced using the ASUS WL-330N AP. There may be other APs with which the bug can also be reproduced.
The bug was not present in Ubuntu 12.04. It is fixed in Ubuntu Vivid Vervet.
The bug should be back-ported to Ubuntu 14.04 because WiFi is a fundamental function for laptops which has worked in Ubuntu LTS before. Speaking for myself, I am reluctant to move to a development release of Ubuntu such as Vivid because problems are to be expected with applications running on top of Ubuntu, e.g. Virtualbox, in such a release.
[Test Case]
DUT :== Device Under Test, a laptop with Ubuntu 14.04 and bcmwl installed.
1. Ascertain no other network connection (e.g. wired Ethernet) are connected to DUT.
2. Connect DUT to av D-Link DIR-645 or ASUS WL-330N AP using WPA2-PSK.
3. Open a Terminal and do at least one of the following:
3a. Determine the IP address of the default gateway ("destination 0.0.0.0") using netstat -rn and ping the IP-address.
3b. Ping the IP address of some other device connected to the same AP. Optionally, use a protocol analyzer (e.g. WireShark) to observe ping packets being received by the other device from DUT and responses being sent back.
4a. If the buig is fixed, you should see lines like "64 bytes received from <IP-address>" in your terminal. After pressing CTRL+C, ping should report "0% packet loss".
4b. If the bug is not fixed, ping just writes "PING <IP-address> ..." and nothing else happens. After pressing CTRL+C, ping reports "100% packet loss". |
[Impact]
Users of Ubuntu 14.04 with bcmwl are unable to utilize WiFi with the D-Link DIR-645 AP (AccessPoint). They are able to connect to the AP using WPA2-PSK and obtain an IP address from the AP, but no IP unicast packets are ever received. Thus, WiFi is for all practical purposes not working for this combination of Ubuntu software and AP.
While this is happening, devices using other software (e.g. Android) are able to utilize WiFi with the same AP without problems.
The bug can also be reproduced using the ASUS WL-330N AP. There may be other APs with which the bug can also be reproduced.
The bug was not present in Ubuntu 12.04. It is fixed in Ubuntu Vivid Vervet.
The bug should be back-ported to Ubuntu 14.04 because WiFi is a fundamental function for laptops which has worked in Ubuntu LTS before. Speaking for myself, I am reluctant to move to a development release of Ubuntu such as Vivid because problems are to be expected with applications running on top of Ubuntu, e.g. Virtualbox, in such a release.
[Test Case]
DUT :== Device Under Test, a laptop with Ubuntu 14.04 and bcmwl installed.
1. Ascertain no other network connection (e.g. wired Ethernet) are connected to DUT.
2. Connect DUT to av D-Link DIR-645 or ASUS WL-330N AP using WPA2-PSK.
3. Open a Terminal and do at least one of the following:
3a. Determine the IP address of the default gateway ("destination 0.0.0.0") using netstat -rn and ping the IP-address.
3b. Ping the IP address of some other device connected to the same AP. Optionally, use a protocol analyzer (e.g. WireShark) to observe ping packets being received by the other device from DUT and responses being sent back.
4a. If the buig is fixed, you should see lines like "64 bytes received from <IP-address>" in your terminal. After pressing CTRL+C, ping should report "0% packet loss".
4b. If the bug is not fixed, ping just writes "PING <IP-address> ..." and nothing else happens. After pressing CTRL+C, ping reports "100% packet loss".
[Regression Potential]
Software Regression is unlikely to occur. If it does will most likely manifest itself as Ubuntu 14.04 with bcmwl being unable to utilize WiFi with any AP (of any make and model). |
|
| 2015-01-11 16:41:03 |
Thomas Ward |
nominated for series |
|
Ubuntu Trusty |
|
| 2015-01-12 15:43:38 |
Brian Murray |
bug task added |
|
bcmwl (Ubuntu Trusty) |
|
| 2015-03-11 02:00:07 |
penalvch |
bcmwl (Ubuntu Trusty): importance |
Undecided |
Medium |
|
| 2015-03-11 02:00:07 |
penalvch |
bcmwl (Ubuntu Trusty): status |
New |
Triaged |
|
| 2015-03-11 02:00:55 |
penalvch |
bcmwl (Ubuntu Trusty): importance |
Medium |
High |
|
