Date: Mon, 23 Sep 2013 10:09:04 -0700 From: hiren panchasara <hiren.panchasara@gmail.com> To: Mark Moes <mark_moes@hotmail.com> Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: ath0 "monitor mode" mystery Message-ID: <CALCpEUE2Ax8h7MLQi9h0WrxYkPgvx9nJVdbLdDGZ0Ub4dJb6XQ@mail.gmail.com> In-Reply-To: <DUB119-W30E1C34EF8426D374112D9912D0@phx.gbl> References: <CALCpEUEti7WhS8rcvorrRUirEmDHEWL8fva6C=7_=zHXM_Vk2w@mail.gmail.com> <DUB119-W30E1C34EF8426D374112D9912D0@phx.gbl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Sep 23, 2013 at 5:14 AM, Mark Moes <mark_moes@hotmail.com> wrote: > > 18:56:23.803065 9838362989us tsft 1.0 Mb/s 60dBm tx power antenna 0 2427 > > MHz 11g Probe Request () [1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0 Mbit] > > That's what you're gonna see if it captures 802.11 frames; you already had > it working :) > I think you are right :-) I got confused with the tcpdump terminology. Just to conclude, for me, specifying flag MONITOR mode worked. But creating monitor mode vap did not. > > And a Probe Request is not a Beacon frame, it is sent by a device > (laptop/smartphone) when it actively scans for APs. See > http://www.wi-fiplanet.com/tutorials/print.php/1447501 > Thanks a lot! Cheers, Hiren
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALCpEUE2Ax8h7MLQi9h0WrxYkPgvx9nJVdbLdDGZ0Ub4dJb6XQ>