Linux wireless drivers development
 help / color / mirror / Atom feed
From: Gerry Gavigan <gerry@gavigan.f9.co.uk>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Sujith Manoharan <sujith@msujith.org>, <linux-wireless@vger.kernel.org>
Subject: Re: ath9k problems on openSUSE 12.3
Date: Wed, 01 May 2013 16:55:18 +0100	[thread overview]
Message-ID: <dbd61eaa1560cbc7d0e603cf77e04aa4@imap.force9.net> (raw)
In-Reply-To: <CAJ-Vmon9uK52yJDWCEpCwffnL90S0MVdZWdVGivLEymTWSrFtg@mail.gmail.com>

On 01.05.2013 16:38, Adrian Chadd wrote:
> .. what was the problem?

I had connected a wifi network extender which borked (at the same time 
that I upgraded the kernel for better gma500 support)

I removed the wifi extender but subsequently had all the problems.

However the source was a tick box in my Netgear router that I don't 
remember setting (or it gets set by using an extender, I've not explored 
that)

This provided wirelss isolation limited to the extender and prevented 
authentication directly with the router. (This might be how extenders 
work but that seems strange to me)

I identified it after I dug out a slow but known working AAO with an 
Intel wifi card and which mysteriously failed to authenticate, so from 
then I knew I was looking in the wrong place.

      reply	other threads:[~2013-05-01 15:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-22 12:30 ath9k problems on openSUSE 12.3 Gerry Gavigan
2013-04-22 17:30 ` Adrian Chadd
2013-04-22 17:31   ` Adrian Chadd
2013-04-22 23:35     ` Gerry Gavigan
2013-04-23  0:56       ` Adrian Chadd
2013-04-23  8:43 ` Sujith Manoharan
2013-04-23  9:28   ` Gerry Gavigan
2013-04-23  9:56     ` Sujith Manoharan
2013-04-24  9:50       ` Gerry Gavigan
2013-04-24 16:37         ` Sujith Manoharan
2013-05-01  8:35       ` Gerry Gavigan
2013-05-01 15:38         ` Adrian Chadd
2013-05-01 15:55           ` Gerry Gavigan [this message]

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=dbd61eaa1560cbc7d0e603cf77e04aa4@imap.force9.net \
    --to=gerry@gavigan.f9.co.uk \
    --cc=adrian@freebsd.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sujith@msujith.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