From owner-freebsd-mobile Thu Feb 22 9: 3:55 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from rigel.cs.pdx.edu (rigel.cs.pdx.edu [131.252.208.59]) by hub.freebsd.org (Postfix) with ESMTP id 7338737B503 for ; Thu, 22 Feb 2001 09:03:52 -0800 (PST) (envelope-from jrb@cs.pdx.edu) Received: from sirius.cs.pdx.edu (root@sirius.cs.pdx.edu [131.252.208.57]) by rigel.cs.pdx.edu (8.9.1/8.9.1) with ESMTP id JAA06306 for ; Thu, 22 Feb 2001 09:03:51 -0800 (PST) Received: from sirius.cs.pdx.edu (jrb@localhost [127.0.0.1]) by sirius.cs.pdx.edu (8.8.6/8.8.5) with ESMTP id JAA02104 for ; Thu, 22 Feb 2001 09:03:50 -0800 (PST) Message-Id: <200102221703.JAA02104@sirius.cs.pdx.edu> To: freebsd-mobile@freebsd.org Subject: wi and promiscuous mode Date: Thu, 22 Feb 2001 09:03:49 -0800 From: Jim Binkley Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Try tcpdump -p ... meaning don't do promiscous mode. There isn't any reason to believe that in BSS mode, prom. mode will help much. Unless I am incredibly wrong (and if I am, please bash me, because someday I want to actually understand the technical ramifications of BSS mode), you can't see 3rd party wireless traffic anyway by definition. In BSS mode, I think all you can see is your traffic, the AP's traffic, and broadcast (or multicast) leaks from the ethernet side (and maybe the occasional unicast leak from the ethernet side too?). Two comments: 1. IMHO, APs suck for the 1 millionth time in a row. Sorry, I can't help it. :-> A layer 3 approach beats a layer 2 approach. This was a paid political announcement. 2. please if you post a problem like this, state whether you are in ad hoc mode or BSS mode. Jim Binkley jrb@cs.pdx.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message