Re: Hi, NM and hidden ESSIDs

["Ey Ez" <noeyez gmail com>]

Hey everyone,
I had a chance to test this recently. For some reason, it still won't pick up my AP. the one thing i noticed was that there was a discrepancy in what network iwlist eth1 scan picked up and what network manager discovered....

On 4/17/06, Bruno Marc-Aurèle <tox_yray hotmail com> wrote:

Fedora Core 5

Thanks,
Bruno MA


>From: "Ey Ez" <noeyez gmail com>
>To: "Bruno Marc-Aurèle" < tox_yray hotmail com>
>Subject: Re: Hi, NM and hidden ESSIDs
>Date: Mon, 17 Apr 2006 12:42:48 -0400
>
>what flavor of linux are you using?
>
>On 4/17/06, Bruno Marc-Aurèle < tox_yray hotmail com> wrote:
> >
> > Gconf.... how can I see if the essids are saved in gconf? Sorry, I'm a
> > noob
> > who wants to learn...
> >
> > Bruno M-A
> >
> >
> > >From: "Ey Ez" <noeyez gmail com>
> > >To: "Dan Williams" <dcbw redhat com >
> > >CC: networkmanager-list gnome org
> > >Subject: Re: Hi, NM and hidden ESSIDs
> > >Date: Mon, 17 Apr 2006 00:04:10 -0400
> > >
> > >Unfortunatly, when i type iwlist eth1 scan it doesn't detect my
>wireless
> > >network even though it has saved its ESSID and BSSID correctly in
>gconf.
> > >I'm
> > >using WPA2 personal with CCMP.....
> > >
> > >
> > >On 4/15/06, Dan Williams <dcbw redhat com> wrote:
> > > >
> > > > On Fri, 2006-04-14 at 08:53 -0400, Bruno Marc-AurXle wrote:
> > > > > Hello,
> > > > >
> > > > > I use NetworkManager with my IPW2200 and it works like a charm!
>The
> > >only
> > > > > thing I was wondering is if there was a way for NM to remember a
> > >hidden
> > > > > ESSID. For a non-encrypted network, it wouldn't be a problem, but
> > for
> > >a
> > > > WEP
> > > > > encrypted network, is causes me a problem: always rewrite the WEP
> > key.
> > > > >
> > > > > Is there a possibility of doing this witht the current
> > implementation
> > >or
> > > > is
> > > > > there a way to add this feature (remembering hidden ESSIDs)
>without
> > > > > reprogramming a whole buch of stuff?
> > > >
> > > > NM should be remembering hidden ESSIDs once you've successfully
> > > > connected to a specific AP/BSSID at least once.  When NM sees that
> > BSSID
> > > > again, it looks up the ESSID for that BSSID and then tries to
>connect.
> > > > It may be broken, but if an 'iwlist eth1 scan' shows the BSSID of
>your
> > > > access point, then NM should be doing the right thing.
> > > >
> > > > For example:
> > > >
> > > >       Cell 08 - Address: 00:14:BF:8C:90:28  <--- BSSID
> > > >                 ESSID:""
> > > >                 Protocol:IEEE 802.11bg
> > > >                 Mode:Master
> > > >                 Channel:6
> > > >                 Encryption key:off
> > > >                 Bit Rates:54 Mb/s
> > > >                 Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48
>54
> > > >                 Quality:20  Signal level:0  Noise level:0
> > > >
> > > > It will probably look something like this from 'iwlist'.  If your AP
> > > > shows up, there's likely a bug in NM.
> > > >
> > > > Dan
> > > >
> > > >
> > > > _______________________________________________
> > > > NetworkManager-list mailing list
> > > > NetworkManager-list gnome org
> > > > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> > > >
> >
> >
> > >_______________________________________________
> > >NetworkManager-list mailing list
> > >NetworkManager-list gnome org
> > >http://mail.gnome.org/mailman/listinfo/networkmanager-list
> >
> >
> >