Return-path: Received: from mail-ey0-f174.google.com ([209.85.215.174]:57681 "EHLO mail-ey0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752329Ab1IZVc5 (ORCPT ); Mon, 26 Sep 2011 17:32:57 -0400 Received: by eya28 with SMTP id 28so4022123eya.19 for ; Mon, 26 Sep 2011 14:32:56 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <1317048872.2400.4.camel@wwguy-ubuntu> <1317049160.1958.8.camel@wwguy-huron> <1317050380.1958.13.camel@wwguy-huron> <1317053131.1958.15.camel@wwguy-huron> <1317062004.1958.18.camel@wwguy-huron> Date: Mon, 26 Sep 2011 23:32:55 +0200 Message-ID: (sfid-20110926_233300_327108_76765BEF) Subject: Re: iwlagn: "Intel Centrino Advanced-N 6205 AGN" and "AVM Fritz!Box (7390)" incompatible From: Henrik Friedrichsen To: "Venkataraman, Meenakshi" Cc: linux-wireless@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Mon, Sep 26, 2011 at 11:24 PM, Venkataraman, Meenakshi wrote: > [MV] Well...what I'm interested in is really the IEEE802.11 packets for when you attempt to browse the web (or other workloads) where you're seeing the issue. Of course, TCP traffic that these packets are carrying will also be helpful. I see. You're going to have to excuse me here, though. I have never done WiFi debugging. What would be the easiest (and for you most useful) way to capture IEEE802.11 packets?