From: wwguy <wey-yi.w.guy@intel.com>
To: Henrik Friedrichsen <hrkfdn@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwlagn: "Intel Centrino Advanced-N 6205 AGN" and "AVM Fritz!Box (7390)" incompatible
Date: Mon, 26 Sep 2011 14:29:32 -0700 [thread overview]
Message-ID: <1317072572.2400.12.camel@wwguy-ubuntu> (raw)
In-Reply-To: <CAJTrwG5ydoheYzYuRZaaR0AfqBgE9KnfYQ8X_0esRNVog3hF=g@mail.gmail.com>
On Mon, 2011-09-26 at 14:31 -0700, Henrik Friedrichsen wrote:
> On Mon, Sep 26, 2011 at 11:17 PM, wwguy <wey-yi.w.guy@intel.com> wrote:
> > how about just doing a flood ping to your AP
> > #sudo ping -f <AP's ip address>
>
> 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.
$sudo ping -f fritz.box
Wey
next prev parent reply other threads:[~2011-09-26 21:34 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 13:57 iwlagn: "Intel Centrino Advanced-N 6205 AGN" and "AVM Fritz!Box (7390)" incompatible Henrik Friedrichsen
2011-09-26 14:07 ` Henrik Friedrichsen
2011-09-26 14:54 ` wwguy
2011-09-26 15:20 ` Henrik Friedrichsen
2011-09-26 14:59 ` Guy, Wey-Yi
[not found] ` <CAJTrwG5eELbDuGFXU4=3gSunPSkKLFvcpSe6gGE_Wc0s5BXZ+A@mail.gmail.com>
2011-09-26 16:03 ` Henrik Friedrichsen
2011-09-26 15:19 ` Guy, Wey-Yi
2011-09-26 16:10 ` Henrik Friedrichsen
2011-09-26 16:00 ` Guy, Wey-Yi
2011-09-26 16:05 ` Guy, Wey-Yi
2011-09-26 17:06 ` Henrik Friedrichsen
2011-09-26 17:58 ` Venkataraman, Meenakshi
2011-09-26 18:26 ` Henrik Friedrichsen
2011-09-26 18:33 ` Guy, Wey-Yi
2011-09-26 20:23 ` Henrik Friedrichsen
2011-09-26 20:59 ` Venkataraman, Meenakshi
2011-09-26 21:02 ` Henrik Friedrichsen
2011-09-26 21:06 ` Venkataraman, Meenakshi
2011-09-26 21:18 ` Guy, Wey-Yi W
2011-09-26 21:19 ` Henrik Friedrichsen
2011-09-26 21:24 ` Venkataraman, Meenakshi
2011-09-26 21:32 ` Henrik Friedrichsen
2011-09-26 21:11 ` wwguy
2011-09-26 21:21 ` Henrik Friedrichsen
2011-09-26 21:17 ` wwguy
2011-09-26 21:31 ` Henrik Friedrichsen
2011-09-26 21:29 ` wwguy [this message]
2011-09-26 21:40 ` Henrik Friedrichsen
2011-09-26 21:56 ` Larry Finger
2011-09-26 22:12 ` Henrik Friedrichsen
2011-09-26 22:19 ` Venkataraman, Meenakshi
2011-09-26 23:03 ` Henrik Friedrichsen
2011-09-27 0:36 ` wwguy
2011-09-26 22:44 ` Larry Finger
2011-09-26 15:41 ` Larry Finger
2011-09-26 15:02 ` Guy, Wey-Yi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1317072572.2400.12.camel@wwguy-ubuntu \
--to=wey-yi.w.guy@intel.com \
--cc=hrkfdn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).