Hi Arend,
On 03.12.2012 09:37, Arend van Spriel wrote:
On 26.11.2012 22:20, Daniel Wagner wrote:
On 26.11.2012 20:36, Seth Forshee wrote:
On Wed, Nov 21, 2012 at 08:35:28AM -0600, Seth Forshee wrote:
My 'test' setup is following: I downloaded a larger file and let a
youtube
video play. With tracing enabled the download and the playback did
work nicely.
Without tracing enabled playing back only a youtube video was
'triggering'
the problem. It downloads a few seconds of content in a burst and
then the playback
starts. Under normal conditions, the app will continue downloading
the video at a
lower rate. But this normally doesn't happen right now. Often it
will just stop
working and often the connection is completely blocked, e.g. pinging
a host
wont work.
I'll see if I can reproduce, but if it's specific to the AP then I may
not have any luck. Don't expect to hear much from me until next week
though; I'm on holiday starting today and will be visiting family.
It seems I'm unable to reproduce the problem with any of the APs
available to me, unfortunately.
I tried it again with disabled the TX trace but I can't reproduce it
either. Well, I am sick of this AP and I might just get a better one
(which should be fairly simple).
FYI, I got my old Netgear 11g AP out and I get a very 'smooth' wifi
experience.
If you like you can add Tested-by tag :)
You basically tested 11g operation is ok. Still interesting to know,
because it may indicate that problems start happening when doing 11n
rates and/or A-MPDU sessions.
A friend of mine have the same 11n AP and for them it also behaves
pretty shitty for him (Windows even worse then Linux...).
I don't know if it is worth to continue to debug with this this
particular 11n AP.
I had a good performance during LinuxCon which indicates that it is
really only my home AP. What I could do is to test with 11n APs at my
workplace and see if the it is really only my home 11n AP.
cheers,
daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
