David Bustos writes: > Quoth John Beck on Fri, Oct 20, 2006 at 06:58:17PM -0700: > > Bart> What information can you see on a wireless link w/o getting our own > > DHCP > > Bart> address? > > > > You can query the DHCP server for what address it would give you, and > > possibly > > some other info (DNS domain, DNS server, etc.) as well, though Kacheong is > > working on a proposal for this and I don't recall its current status. > > Can't we also sniff packets? Won't that get us nearby MAC addresses, > which we could potentially use to identify a network?
Only in a hit-or-miss fashion. It sounds like quite a hack to me. > And if the > network is unencrypted, won't that also get us IP addresses, which we > could also use to identify a network? Again, hackish at best. I thought we were supposed to be building something that'd be robust, at least by default. I agree that it'd be nice to have some sort of plug-in interface that allows users or community members to develop less-than-completely- reliable mechanisms that suit some tastes. I don't agree that those should necessarily be part of Solaris -- or at least that they must be used by default. For what it's worth, on most switches, you get only broadcast packets and the few multicast messages for which you've registered (via IGMP). This limits the scope of what you can actually observe passively in most cases. And that even leaves 802.1X and wireless issues out. -- James Carlson, KISS Network <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
