linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Wade Berrier <wberrier@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	Michael Wu <flamingice@sourmilk.net>,
	linux-wireless@vger.kernel.org
Subject: Re: realtek 8185
Date: Fri, 19 Oct 2007 02:32:48 -0400	[thread overview]
Message-ID: <1192775568.14897.22.camel@localhost.localdomain> (raw)
In-Reply-To: <bbbeeccd0710182154h5b42384cxb4bd49f5159504eb@mail.gmail.com>

On Thu, 2007-10-18 at 22:54 -0600, Wade Berrier wrote:
> Hi,
> 
> On 10/18/07, John W. Linville <linville@tuxdriver.com> wrote:
> > On Thu, Oct 18, 2007 at 11:13:00AM -0600, Wade Berrier wrote:
> > > On 10/17/07, Michael Wu <flamingice@sourmilk.net> wrote:
> > > > On Wednesday 17 October 2007 18:52:28 Wade Berrier wrote:
> > > > > Another thing I'm noticing is that I can't connect to an 802.11b open
> > > > > network with a hidden essid.
> > > > >
> > > > For those, you should specify the channel, and bssid in one iwconfig command,
> > > > and then ssid in another command. Everything needs to be specified for hidden
> > > > networks. Never tried connecting to hidden networks with network manager so I
> > > > dunno if that's suppose to work.
> > >
> > > I've been able to connect to this hidden network via network manager.
> > > >From a users experience, I enter in the essid from the "Connect to
> > > other wireless network" dialog, and it connects.  I'm not sure how
> > > networkmanager makes the connection between the essid and the ap.
> >
> > If anything, I usually find that I can connect to the hidden networks
> > using iwconfig but _not_ with NetworkManager.  FWIW, mac80211 will
> > send probe requests for unknown SSIDs when trying to associate.
> 
> I can connect to this same network with an intel 2200.  The network
> comes up in the networkmanager list, but without and essid.
> 
> Is a hidden network the same thing as a network that doesn't broadcast
> the essid?

Yes.

> >
> > Unfortunately, I'm not really sure how this relates to the problem
> > you are having.  Perhaps probe responses are being lost somehow?
> 
> I'd assume it was driver related since I can with the intel 2200, but
> not with the realtek 8185.  I'm not sure; I guess I'd have to do some
> more digging.
> 
> Wade
> -
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2007-10-19  6:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bbbeeccd0710160658p7f127bb9if2239287bee33d6c@mail.gmail.com>
     [not found] ` <bbbeeccd0710162220u3b276506s68457b4220bec8ae@mail.gmail.com>
     [not found]   ` <bbbeeccd0710171552x37986f68m906a603e793c7996@mail.gmail.com>
     [not found]     ` <200710171938.48414.flamingice@sourmilk.net>
2007-10-18 17:13       ` realtek 8185 Wade Berrier
2007-10-18 17:41         ` John W. Linville
2007-10-19  4:54           ` Wade Berrier
2007-10-19  6:32             ` Dan Williams [this message]
2007-10-19  6:38           ` Dan Williams

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=1192775568.14897.22.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=flamingice@sourmilk.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=wberrier@gmail.com \
    /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).