From owner-freebsd-net@FreeBSD.ORG Tue Aug 10 21:13:22 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62E8A16A4CE for ; Tue, 10 Aug 2004 21:13:22 +0000 (GMT) Received: from exch2.verniernetworks.com (dns.verniernetworks.com [65.200.185.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id 087CA43D49 for ; Tue, 10 Aug 2004 21:13:22 +0000 (GMT) (envelope-from ddhokte@verniernetworks.com) X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 10 Aug 2004 14:13:12 -0700 Message-ID: <085485A8ADCB4B49874A54D6185A21FD3B75BC@exch2.verniernetworks.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: IPv6 wireless stumbler Thread-Index: AcR+io/hpAB+pa6sRF28kiesif9sDAAj1LTg From: "Deepti Dhokte" To: "User Ernie" cc: freebsd-net@freebsd.org Subject: RE: IPv6 wireless stumbler X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Aug 2004 21:13:22 -0000 AP is a L2 device, so the upstream IPv6 L-3switch/router to which AP connects to, If configured to do prefix advertisements, and your client if properly configured to use IPv6 stack, client can auto-configure global unicast IPv6 addresses. Technically your client might have already configured fe80:: based link-local address, for all the active interfaces when you install IPv6 stack, if the site allows link local addresses to be used to access IPv6 internet, you are all set. But that is not a normal scenario. In short:=20 associate to an AP, and find out if the ipv4 (if DHCP is enabled on that interface) and global Unicast IPv6 addresses (if stack is already in place) are getting configured on your client. If yes, try to visit www.kame.net if you see moving turtle You are connected on IPv6 :-) Hopefully you are dealing with fewer AP's around. Another try would be: Check packet dumps. When you associate to an AP and the packet trace displays IPv6 prefix advertisements, that AP is probably associated to IPv6 network as well. Check, if your client might have configured the address with given prefix; (since you are able to see these prefix advertisements in the packet dumps, started on the wireless card that is associating with different APs, it is likely that client if has IPv6 stack could have already auto-configured IPv6 address.). (Prefix advertisements are ICMP6 type Neighbor solicitation messages on top of IPv6 protocol. Packet sniffers such as Ethereal can parse these messages and provide useful Differentiation at very detail level) I hope it helps. If anyone knows better methods, I am eager to know.=20 -Deepti -----Original Message----- From: owner-freebsd-net@freebsd.org [mailto:owner-freebsd-net@freebsd.org] On Behalf Of User Ernie Sent: Monday, August 09, 2004 8:31 PM To: freebsd-net@freebsd.org Subject: IPv6 wireless stumbler I am trying to find out if there are any IPv6 community access wireless nodes in my area the I can become a client for. There are dozens of AP's that come up with a scan using kismet but I don't know how to tell if=20 they are issuing IPv6 addresses. Can anyone suggest a method? - Ernie. _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"