Comment 38 for bug 1349572

Thanks, Marcel. The problem does look very similar to that in bug #1293569, but apparently that fix isn't working for you.

Let's try to get some more data. Please download http://people.canonical.com/~sforshee/wifi-debug, then open a terminal and make it file executable ("chmod u+x wifi-debug" in the directory where you downloaded the file). Run "sudo apt-get install iw trace-cmd tcpdump" to install some needed tools, then run "./wifi-debug -t -p". This will start collecting data. Leave it running until you experience wireless problems, then press Enter to stop collecting data (this collects a lot of data, so if this problem takes a long time to happen you may want to periodically stop and restart wifi-debug as long as the connection is stable as well).

Once the script finishes you should have a file named wifi-debug-files.tar.gz. Please give me this file either via email or by uploading it to some kind of online storage and providing me a link. I don't suggest attaching it to this bug report.

Please note that this script will log your network activity and the activity of other wireless clients on the same channel (though traffic from other clients will be encrypted if connected to a protected network), so anything you do on the wireless connection while it's running will be captured. I won't be looking at the actual data sent over the network, and anything sent over a secure SSL connection will still be encrypted, but you may want to restrict your activity while the script is running to avoid having any personal or confidential information captured. If you aren't comfortable with having network activity logged you can omit the -p option to wifi-debug. In that case only mildly private information such as network addresses will be collected, but that will also limit what I'm able to do to help you.

Thanks!