kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

** Changed in: bcmwl (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: bcmwl (Ubuntu Trusty)
       Status: New => Triaged

** Changed in: bcmwl (Ubuntu Trusty)
   Importance: Medium => High

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1289746

Title:
  14e4:4727 [Asus 1225B] BCM4313 not working with D-Link DIR-645 AP

Status in bcmwl package in Ubuntu:
  Fix Released
Status in bcmwl source package in Trusty:
  Triaged

Bug 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".

  [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).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1289746/+subscriptions