[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
- <!--x-content-type: text/plain -->
- <!--x-date: Sun Mar 14 22:02:22 2004 -->
- <!--x-from-r13: wvzcbc ng lnubb.pbz (Xvz Bbcbivgpu) -->
- <!--x-message-id: 1079319604.31234.6.camel@blue -->
- <!--x-reference: 1079314759.30559.18.camel@blue -->
- <!--x-reference: [email protected] -->
- <!--x-reference: 1079317861.30881.3.camel@blue -->
- <!--x-reference: [email protected] --> "http://www.w3.org/TR/html4/loose.dtd">
- <!--x-subject: [ale] Dualing wireless APs -->
- <li><em>date</em>: Sun Mar 14 22:02:22 2004</li>
- <li><em>from</em>: jimpop at yahoo.com (Jim Popovitch)</li>
- <li><em>in-reply-to</em>: <<a href="msg00474.html">[email protected]</a>></li>
- <li><em>references</em>: <1079314759.30559.18.camel@blue> <<a href="msg00473.html">[email protected]</a>> <1079317861.30881.3.camel@blue> <<a href="msg00474.html">[email protected]</a>></li>
- <li><em>subject</em>: [ale] Dualing wireless APs</li>
-Jim P.
On Sun, 2004-03-14 at 21:58, Keith Hopkins wrote:
> Jim Popovitch wrote:
> > On Sun, 2004-03-14 at 21:11, Keith Hopkins wrote:
> >
> >
> >>I'm still a beginner in the wireless world myself, but I believe if
> >>you set the ESSID on your client to match that of your AP, it will
> >>only connect to that AP. You should always change an AP's ESSID to
> >> something other than the default.
> >
> >
> > Well, that works at home... what do I do at the next network. ;)
> >
> > The underlying issue is that Linux wireless networking isn't too
> > friendly to roaming users who access multiple networks unless those
> > networks are completely isolated and either all running the same
> > encryption (which is weak anyways) or not running any encryption at all.
>
> Well...time to get your hands dirty I guess, and start customizing those startup scripts....
>
> Here's some ideas, some of which I have 1/2 implemented on my laptop:
>
> 1) after loading the wlan drivers, the network startup runs `iwlist scan` to see what APs are available;
>
> 2) cross check that list against know APs, in order to associate WEP keys, WPA, ESSID and other settings with it;
>
> 3) configure appropriately for known APs;
>
> 4) or optionally set some other values for `any` AP,
> 4) prompt to store new AP info in config file,
> 4) optionally delay wlan setup to end of normal startup and prompt user for which AP they want to attach to;
>
> 5) continue with IP config as normal.
>
> Basically, your setting a profile dynamically based upon the conditions at startup.
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00460" href="msg00460.html">[ale] Dualing wireless APs</a></strong>
<ul><li><em>From:</em> jimpop at yahoo.com (Jim Popovitch)</li></ul></li>
<li><strong><a name="00473" href="msg00473.html">[ale] Dualing wireless APs</a></strong>
<ul><li><em>From:</em> hne at hopnet.net (Keith Hopkins)</li></ul></li>
<li><strong><a name="00465" href="msg00465.html">[ale] Dualing wireless APs</a></strong>
<ul><li><em>From:</em> jimpop at yahoo.com (Jim Popovitch)</li></ul></li>
<li><strong><a name="00474" href="msg00474.html">[ale] Dualing wireless APs</a></strong>
<ul><li><em>From:</em> hne at hopnet.net (Keith Hopkins)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00474.html">[ale] Dualing wireless APs</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00475.html">[ale] OT: Laptops.</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00474.html">[ale] Dualing wireless APs</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00488.html">[ale] Dualing wireless APs</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00469"><strong>Date</strong></a></li>
<li><a href="threads.html#00469"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>