Date: Wed, 4 Apr 2001 17:13:36 -0700 (PDT) From: Guangrui Fu <guangruifu@yahoo.com> To: Jim Binkley <jrb@cs.pdx.edu>, freebsd-mobile@freebsd.org Subject: Re: 802.11 interop testing Message-ID: <20010405001336.21395.qmail@web3104.mail.yahoo.com> In-Reply-To: <200103301906.LAA13593@sirius.cs.pdx.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, do you or anyone have tried to enable TWO wireless LAN cards(for different AP) simultaneously for one labtop in FreeBSD? I'm interested to know what will happen when a host(one or more IP addresses) have more than one wireless access at the same time. Can it receive/send packets from both? Thanks, ---- Jim Binkley <jrb@cs.pdx.edu> wrote: > > I've been informally testing a few things with the > following setup (mostly). > One goal is to learn if promiscuous mode works on > the lucent boxes. > Another is to learn if 802.11 interop (especially in > IBSS) mode exists. > > Cisco AIRONET access-point in infrastructure mode > > | | > | | > | | > FreeBSD 4.2 FreeBSD 3.2, but 4.2 wi driver > equivalent... > Cisco aironet 350 Lucent older 802.11 card, > firmware update made > aka cisco laptop/card aka lucent laptop/card > > 1. promiscuous mode test in infrastructure mode > > 1.1 lucent card does promiscuous mode (tcpdump) > Cisco laptop pings external IP host. > result: > Lucent laptop CANNOT read unicast packets. Can read > broadcast/multicast > packets, and see ARP broadcast from Cisco. > > So basically promiscuous mode doesn't work, but you > can still > steal other people's MAC addresses. Just wait for > the arp broadcast. :-> > > > 1.2 cisco card does prom. mode > Lucent laptop pings external IP host. > Cisco laptop CAN read unicast lucent packets for 3rd > party with tcpdump. > > consider: 2 end systems in infrastructure mode and > in promiscous mode > could talk to each other directly sans AP ... if > they are willing to pay the price. > > 2. promiscuous mode test in "old" lucent ad hoc mode > with same driver. NO. > > Different setup at layer 3, but roughly similar > > Mobile-IP agent (lucent card) using "old" ad hoc > > | <----- linux box with lucent card in > promiscuous mode > > Mobile-IP mobile node (lucent card) > > The mobile node pings an external IP address (thus > all packets are unicast). > The linux box with the lucent card (redhat 6.2 and a > lucent driver of some vintage > known to work with redhat 6.2) CANNOT see the > promiscuous unicast packets. > It can see broadcast. > > I think this is a firmware bug ... > > 3. can old lucent ad hoc talk to Cisco box in IBSS > mode. NOPE. > > 4. can new lucent firmware update IBSS talk to Cisco > laptop in IBSS. YES, but > this can stand more testing. > > 5. can two laptops in infrastructure mode talk to > each other sans AP. NOPE. > > 6. can two laptops in IBSS mode talk to each other > sans AP. YES. > > 7. Can cisco box in ad hoc mode (IBSS) talk to AP in > infrastructure mode. NO. > This was a sanity check on #8. > > 8. Can lucent box in IBSS/ad hoc (just to be clear) > talk to AP in infrastructure > mode. Needs more testing. I swear it happened. > > Things that go bump in the night: > > I could not get the lucent cards in any mode (didn't > try IBSS though), (old > ad hoc, and infrastructure) to do promiscuous mode. > Linux driver or freebsd > driver. Didn't matter. > > However in one case (infrastructure mode) the lucent > cards were reading unicast > 802.11 control packets of some sort that the Cisco > end system was sending. If > someone knows what these things MIGHT be, please let > me know. Note the per 10 > second granularity. A packet > trace follows: > > 15:25:48.959186 0:40:96:51:a1:93 0:40:96:40:65:97 > 0000 14: [|llc] > 15:25:59.952318 0:40:96:51:a1:93 0:40:96:40:65:97 > 0000 14: [|llc] > 15:26:10.945185 0:40:96:51:a1:93 0:40:96:40:65:97 > 0000 14: [|llc] > 15:26:21.938203 0:40:96:51:a1:93 0:40:96:40:65:97 > 0000 14: [|llc] > 15:26:32.931882 0:40:96:51:a1:93 0:40:96:40:65:97 > 0000 14: [|llc] > 15:26:43.924225 0:40:96:51:a1:93 0:40:96:40:65:97 > 0000 14: [|llc] > 15:26:54.917238 0:40:96:51:a1:93 0:40:96:40:65:97 > 0000 14: [|llc] > 15:27:05.910245 0:40:96:51:a1:93 0:40:96:40:65:97 > 0000 14: [|llc] > 15:27:16.903271 [|ether] > 15:27:27.896274 0:40:96:51:a1:93 0:40:96:40:65:97 > 0000 14: [|llc] > 15:27:38.889427 0:40:96:51:a1:93 0:40:96:40:65:97 > 0000 14: [|llc] > 15:27:49.882302 0:40:96:51:a1:93 0:40:96:40:65:97 > 0000 14: [|llc] > > MAC addresses are cisco aironet addresses (end node > and AP). > > Jim Binkley > jrb@cs.pdx.edu > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message __________________________________________________ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010405001336.21395.qmail>