Re: Issue with the network interfaces

[Prasad Asokan <prasadasokan () gmail com>]

Thanks a lot for the information. When this comes into the beta or
stable release how can one find information related to this fix? Is
there a reference number or similar that one can look in the change
logs? Thanks again for the information.

Regards,
Prasad Asokan

On 11-May-2013, at 3:07 AM, David Fifield <david () bamsoftware com> wrote:

> On Tue, May 07, 2013 at 05:07:55PM +0530, Prasad Asokan wrote:
> > While using nmap to discover an asset, if an user switches from ethernet to
> > wireless, or vice versa, nmap quits saying "failed to determine dst mac
> > address for target". While we invoke "nmap --iflist", what we observe is,
> > the disconnected network interface still shows up in the list of
> > interfaces. To make things work, either one of the following needs to be
> > done.
> >
> > i) Disable the disconnected network adapter from the network connections
> > and re-enabling it helps nmap to pick the right adapter.
> > ii) Figure out the right adapter from the iflist output and use it to
> > launch nmap. "nmap -e eth5 10.1.5.1"
> >
> >
> > Is there a way by which one can force nmap to re-enumerate
> > available/connected interfaces? Or a windows service that can be restarted
> > which help nmap find the right adapters in any point in time? Thanks in
> > advance.
>
> Thanks for this report. I think the bug might have been fixed with route
> metric awareness, which was introduced in February of this year. The
> change is not in any released version yet. In the meantime your
> workaround works.
>
> David Fifield
_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/