Return-path: Received: from mail-ey0-f174.google.com ([209.85.215.174]:46940 "EHLO mail-ey0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752492Ab1IZVbj (ORCPT ); Mon, 26 Sep 2011 17:31:39 -0400 Received: by eya28 with SMTP id 28so4020992eya.19 for ; Mon, 26 Sep 2011 14:31:38 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <1317071853.2400.11.camel@wwguy-ubuntu> 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> <1317071501.2400.10.camel@wwguy-ubuntu> <1317071853.2400.11.camel@wwguy-ubuntu> Date: Mon, 26 Sep 2011 23:31:38 +0200 Message-ID: (sfid-20110926_233143_277320_D0E419FF) Subject: Re: iwlagn: "Intel Centrino Advanced-N 6205 AGN" and "AVM Fritz!Box (7390)" incompatible From: Henrik Friedrichsen To: wwguy 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:17 PM, wwguy wrote: > how about just doing a flood ping to your AP > #sudo ping -f Okay, here's what's happening: ~ > ping -f fritz.box PING fritz.box (192.168.178.1) 56(84) bytes of data. ping: cannot flood; minimal interval, allowed for user, is 200ms When I send regular pings: ~ > ping -c5 fritz.box PING fritz.box (192.168.178.1) 56(84) bytes of data. 64 bytes from fritz.box (192.168.178.1): icmp_req=1 ttl=64 time=1.31 ms 64 bytes from fritz.box (192.168.178.1): icmp_req=2 ttl=64 time=1.26 ms 64 bytes from fritz.box (192.168.178.1): icmp_req=3 ttl=64 time=1.30 ms 64 bytes from fritz.box (192.168.178.1): icmp_req=4 ttl=64 time=2.51 ms 64 bytes from fritz.box (192.168.178.1): icmp_req=5 ttl=64 time=1.22 ms --- fritz.box ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 32046ms rtt min/avg/max/mdev = 1.226/1.524/2.515/0.496 ms As you can see, the packets get there and the response goes back to me. But it seems to take ages for the package to be sent. I've sent five pings and got my response back in regular latency, however the whole process took 32 seconds.