IETF Logo Mail Archive

Re: Network Scanning

Jeroen Massar <jeroen@unfix.org> Fri, 04 April 2008 21:51 UTC

Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8034D28C14F; Fri, 4 Apr 2008 14:51:29 -0700 (PDT)
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8E40D3A6CA7 for <ipv6@core3.amsl.com>; Fri, 4 Apr 2008 14:51:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_42=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MEMJQW7jc5YA for <ipv6@core3.amsl.com>; Fri, 4 Apr 2008 14:51:26 -0700 (PDT)
Received: from abaddon.unfix.org (abaddon.unfix.org [IPv6:2001:41e0:ff00:0:216:3eff:fe00:4]) by core3.amsl.com (Postfix) with ESMTP id 5CA9F28C3A0 for <ipv6@ietf.org>; Fri, 4 Apr 2008 14:51:17 -0700 (PDT)
Received: from [IPv6:2001:41e0:ff42:b00:216:cfff:fe00:e7d0] (spaghetti.ch.unfix.org [IPv6:2001:41e0:ff42:b00:216:cfff:fe00:e7d0]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by abaddon.unfix.org (Postfix) with ESMTPSA id 53D0B402045; Fri, 4 Apr 2008 23:51:21 +0200 (CEST)
Message-ID: <47F6A2D0.3040602@spaghetti.zurich.ibm.com>
Date: Fri, 04 Apr 2008 23:51:12 +0200
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12) Gecko/20080213 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Prasanna Ram Venkatachalam <vpram86@gmail.com>
Subject: Re: Network Scanning
References: <d4f670930804041235y773e5994g8168b5e2533ee59d@mail.gmail.com>
In-Reply-To: <d4f670930804041235y773e5994g8168b5e2533ee59d@mail.gmail.com>
X-Enigmail-Version: 0.95.6
OpenPGP: id=333E7C23
X-Virus-Scanned: ClamAV version 0.92.1, clamav-milter version 0.92.1 on abaddon.unfix.org
X-Virus-Status: Clean
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0940948162=="
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

Prasanna Ram Venkatachalam wrote:
> Hi all,
> 
> With the evolving IPv6 which will be a mandate soon(as far as i know), 
> the network discovery is going to be very difficult. Is there any 
> optimized way proposed so far which can be used with IPv6 for network 
> discovery??

ping6 ff02::1

Which should make every single host on a link answer to it.

For the rest, read the excellent paper by Steven M. Bellovin:

http://www.cs.columbia.edu/~smb/papers/v6worms.pdf

Greets,
  Jeroen


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email