>1) Will WEP be fixed soon for use with the Promix cards ?
Promix?
>2) If someone were able to monitor a frequency that we are using with
>Turbocell, would they be able to determine the origin of the signal? In
>other words, does Turbocell send some kind of information in clear text
>every now & then?
Frequency can easily be determined
I know that the System Access Pass Phrase (like the ESSID) is sent in
Cleartext
As for the Network Name, I'll have to defer to Doug for that one
>3) RIP --> I am unfamiliar with RIP as we use OSPF on our network.
>However, I believe I could enable RIP-2 for the wireless segment of my
>network to avoid hard coding a bunch of static routes. With this in mind,
>since RIP-2 is a constant broadcast protocol, does it add much overhead to
>the network?
yes, IMO, the Bellman-Ford Algorithm does not make for an efficient routing
protocol
Also unlike OSPF, where you only have Hellos floating b/n neighbors, RIP, a
distance-vector routing protocol, sends periodic updates (consisting of its
entire routing tables) to directly connected neighbors, even when there are
no change to report
RIP uses hop count (and ONLY hop count) as it's routing metric - this can be
a PITA, especially w/ unequal paths when coupled w/ RIPs tendency to load
balance
Finally RIP's convergence time sucks
Honestly, if you have a network large enough where static routes won't cut
it, you probably shouldn't be using the same box to double up as your AP &
Router - just get a 2621, isolate your broadcast domains w/ VLANs, turn on
OSPF, and everyone's happy <g>
>Does anyone have any tips for me on implementing RIP-2 ?
>Anything that was weird or whatever?
yeah, don't bother
-Charles
|