RE: Most final release candidate yet: Nmap 4.49RC6

["Fred" <sfred92 () free fr>]

Rob,

I had tried on my Vista laptop following versions: Nmap 4.20, 4.22RCx and
4.23RCx, all with 2 main bugs:

        - wireless interface, now corrected with 4.49RCx
        - already "failed to open eth4" on Ethernet interface with fixed IP
address

So, IMHO, I don't see no relation between David's modification and that last
bug.

Well, strange problem...

Fred

PS: to keep my network secured, I had to put a top-level security guard.
Worf was the right person ;-)))

-----Message d'origine-----
De : Rob Nicholls [mailto:robert () everythingeverything co uk] 
Envoyé : lundi 10 décembre 2007 13:14
À : Fred
Cc : nmap-dev () insecure org
Objet : RE: Most final release candidate yet: Nmap 4.49RC6

Fred,

I can't see anything obviously wrong there. With only one IP address (RC6
includes David's recent modification so --iflist should list every IP
address assigned to your adapters), it clearly has to use eth4 both times;
I'm not sure why it would work for one IP, but not for the other static
one. As you can list the IPs and routes, I think that means WinPcap is
happy.

David recently changed the way interfaces are handled

http://seclists.org/nmap-dev/2007/q4/0391.html

This fixed problems for wireless users on Vista, and although I haven't
noticed any problems with the fix, perhaps it's the cause of your problem
(a bit of a long shot, I know)? Are you able to try nmap-4.23RC3 or older
to see if the problem was only recently introduced? 4.23RC3 has the added
benefit of listing the interface number.

> Interesting ports on worf (192.168.10.1):

I like the hostname :)


Rob




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