Re: Weird Nmap behaviour on Windows (Latest SVN version)

["Luis MartinGarcia." <luis.mgarc () gmail com>]

On 07/14/2010 06:51 PM, David Fifield wrote:
> On Tue, Jul 13, 2010 at 09:59:29AM +0200, Luis MartinGarcia wrote:
>   
> > On Mon, Jul 12, 2010 at 11:11 PM, David Fifield <david () bamsoftware com> wrote:
> >     
> > > On Wed, Jul 07, 2010 at 07:29:19PM +0200, Luis MartinGarcia wrote:
> > >       
> > > > > Luckily we had prepared a debug release around the time of this change.
> > > > > Try running --iflist with these two releases and send me the output.
> > > > >           
> > > > Done. I'm sending you the output in a separate message.
> > > >         
> > > I can see where the program is failing, but it's not failing in the way
> > > I expected. I though that the interface description and "friendly name"
> > > would be mismatched, but instead it seems like there is a problem
> > > getting the "friendly name" at all.
> > >
> > > Please try this patch and send me the output of --iflist again.
> > >       
> > Ok, Done. I'll send you the output off the list.
> >     
> Rob and Luis, please try r18810. In this revision I've relaxed the
> requirement to match an interface description string along with the
> hardware address. Now a hardware address match is considered good
> enough, just like before r17542, but if all we have is an address match
> we will keep searching in case there's an interface that also matches
> the description.
>
> The strategy of requiring a description match was failing for the two of
> you in different ways. For Luis, the function call to PacketRequest to
> get the description string was failing for unknown reasons. For Rob, the
> description we got from PacketRequest was slightly different from the
> one provided by libpcap. I assumed that these were always coming from
> the same source, but I guess I was wrong.
>
> This isn't a perfectly clean solution. If there is a teamed interface
> somewhere whose description string can't be retrieved, or a teamed
> interface whose description string differs from the pcap description, it
> will fail again. I think this will further reduce the number of
> interfaces that can't be matched by intf_get_pcap_devname. To make this
> really bulletproof I think we need to make libdnet and libpcap get their
> interface tables from the same source. Either both from the registry or
> both from GetIfTable.
>
> David Fifield
>   


Hi David,

I am happy to report that the problem is solved. Windows 7 now detects
my network interface without problem.

Regards,

Luis MartinGarcia.



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