On Sat, Apr 05, 2003 at 04:23:35PM -0800, Joel Jaeggli wrote: > On Sat, 5 Apr 2003, David Young wrote: > > I suggest that people who aspire to build an ad hoc wireless network do > > not concentrate on the hard problems until they become hard problems. > > Hard problems that have needlessly distracted our tiny group in Urbana > > include channel allocation and scalability. We only found out the real > > problems when we started building things. As usual, the devil was in the > > details; details of 802.11 IBSS network coalescence, 802.11 multicast > > lossage, NetBSD's ARP implementation, and Prism2.x firmware bugs have > > been worse problems for us than the routing, which has ordinarily > > "just worked." > > Some of the hard problems bite you in a big hurry as you start adding > nodes and aps... After a while having one broadcast ethernet domain gets > old in a hurry, as the background traffic goes up. Want to add multicast > and ipv6 and all of a sudden the incentive to subnet and turn layer2 ports > into layer 3 ports gets bigger in a hurry. In places where most > high-speed access links are via wireless (cities like lome, or lagos or > accra all in west africa) they are starting to learn this the hard-way.
Urbana's and Kingsbridge's ad hoc networks are both IP networks, so the problems of running a bridged network are not a concern. Dave -- David Young OJC Technologies [EMAIL PROTECTED] Urbana, IL * (217) 278-3933 -- general wireless list, a bawug thing <http://www.bawug.org/> [un]subscribe: http://lists.bawug.org/mailman/listinfo/wireless
