Re: Issue with nmap on wireless Vista interface

["Scott Burch" <camberwind () gmail com>]

Yes,

I know the 169.x address space has historically been used only for
link local addresses (e.g. when dhcp is not available, etc.), but the
firmware I am using for my mesh config uses this be default for the
mesh network. What I find interesting is that nmap does not report the
wireless interface correctly..it shows up as net0..you will not that
it has no corresponding MAC address. If I connect via the wired
Broadcom interface nmap works just fine. (My first post shows this
output).

I think I will change the mesh to use 10.x and see if that makes a difference.

Could also be something with HP's wireless config utility..which I use
to disable bluetooth and wireless easily.

I'll do some more testing.


On 4/2/07, Dude VanWinkle <dudevanwinkle () gmail com> wrote:
> On 4/2/07, Scott Burch <camberwind () gmail com> wrote:
> > Hi,
> >
> > No that is not the problem. I have a wireless mesh network configured
> > at my home. I think nmap does not like this. I can access the Internet
> > just fine. :-)
>
> so you have your home net configured for 169.254 addy's?
>
> i guess thats a new one for introducing plausible deniability :-)
>
> well, all i can say is make sure you installed pcap after enabling and
> logging in as the Administrator account in vista.
>
> if you dont want to run the app as Admin, change the acl's in
> hklm/software/winpcap and "x:\program files", blah blah.
>
> I had nmap 420 (no .1) working fine on my TM4200+ulitmate+3945abg in
> the last release of vista from the TAP program, so it is possible..
> unless nmap checks for the 169.254 and then craps out..
>
> -JP

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org