Re[2]: nmap not scanning networks?

From: FreeBSD User (FreeBSD_at_access.sanet.ge)
Date: 06/17/04

  • Next message: Zoran Kolic: "Re: nmap not scanning networks?"
    Date: Thu, 17 Jun 2004 16:22:07 +0500
    To: Oliver Eikemeier <eikemeier@fillmore-labs.com>
    
    

    OE> Chuck Swiger wrote:

    >> Alex Povolotsky wrote:
    >>> Attempt to scan a network with any method except plain ping results in
    >>> an error:
    >>> truss nmap -sT -p 21 '172.19.17.*'
    >>
    >> I can confirm the problem, anyway, although I'm not sure it's germane
    >> to freebsd-security. :-)
    >>
    >>> [...]
    >>> sendto(0x4,0x8094200,0,0x0,{ AF_INET 172.19.17.0:0 },0x10) ERR#49
    >>> 'Can't assign requested address'
    >>> [...]
    >>> What's strange that man on send(2) doesn't state that EADDRNOTAVAIL
    >>> can ever be returned from sendto().

    OE> Have you checked the firewall rules and routing tables on your machines?
    OE> Do you have the same problems with non-private IP ranges?

    I had the same problem because my host IP address was inclusive in the
    IP range. Make sure your host IP is not inclusive and see the result.

    OE> -Oliver

    OE> _______________________________________________
    OE> freebsd-security@freebsd.org mailing list
    OE> http://lists.freebsd.org/mailman/listinfo/freebsd-security
    OE> To unsubscribe, send any mail to
    OE> "freebsd-security-unsubscribe@freebsd.org"

    -- 
    Best regards,
     FreeBSD                            mailto:FreeBSD@access.sanet.ge
    _______________________________________________
    freebsd-security@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-security
    To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org"
    

  • Next message: Zoran Kolic: "Re: nmap not scanning networks?"

    Relevant Pages

    • Re: ip forwarding woes
      ... It turns out routing table on the 10.0.0.2 host was wrong, ... I can ping the firewall at both 192.160.0.1 and 10.0.0.1. ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
      (Debian-User)
    • Re: backports.org routing fixed
      ... > Hopefully this will clearn up the routing issues for anyone else still ... It's working here now from this host. ... To UNSUBSCRIBE, email to debian-user-request@lists.debian.org ...
      (Debian-User)
    • Re: scp problem
      ... scp -p file 192.168.1.1:./ssh ... The authenticity of host '192.168.1.105 ' can't be established. ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
      (Debian-User)
    • Re: configuration of a linux router
      ... only on my private LAN? ... Especially if you later add a host, you don't have to go around ... Now you're using shaw.ca for your home domain. ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
      (Debian-User)
    • Re: illegal access using ssh
      ... When a new connection attempt is made, the ssh daemon will first check ... hosts.allow to see if the host is permitted. ... config files, to make this behavior occur for all daemons on the server ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
      (Debian-User)