Re: Scanning 255.255.255.255 from Windows

["Hans Nilsson" <hasse_gg () ftml net>]

Hi! Thanks for your reply.

Your suggestion helped me make som progress:
nmap -sU -PN -n -p 53 255.255.255.255 -e eth4
nexthost: Failed to determine dst MAC address for target 255.255.255.255
QUITTING!

Quoting myself from the earlier post:
"And allowing you to manually set the destination MAC or automatically
setting the destination MAC for broadcast packets would be great too."

As far as I know there is no such option and thus it's not possible to
proceed? (Of course I could go into the source and attempt to fix it
that way.)

/Hans

On Sun, 15 Nov 2009 21:04:16 -0700, "David Fifield"
<david () bamsoftware com> said:
> On Tue, Oct 27, 2009 at 02:55:07PM -1100, Hans Nilsson wrote:
> > I was just trying to scan the IP 255.255.255.255 from my Windows box but
> > Nmap doesn't allow me to do that. It says that Windows doesn't allow you
> > to scan localhost in that way, but I don't want to scan localhost, I
> > want to scan 255.255.255.255. Surely Windows allows you to set
> > 255.255.255.255 as the destination IP?
>
> Hey, can you try running with the -e option to specify the outgoing
> interface? Like
>
> nmap -e eth0 255.255.255.255
>
> You can run "nmap --iflist" to see what interfaces you have.
>
> That message "Skipping scan against 255.255.255.255 because Windows does
> not support scanning your own machine (localhost) this way" is printed
> whenever the outgoing interface type is determined to be a loopback
> interface. You might be able to avoid it by naming the interface
> explicitly.
>
> David Fifield
-- 
  Hans Nilsson
  hasse_gg () ftml net

-- 
http://www.fastmail.fm - A no graphics, no pop-ups email service

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