From owner-freebsd-questions@FreeBSD.ORG Thu Feb 12 14:20:54 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C99A1065670 for ; Thu, 12 Feb 2009 14:20:54 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: from ibctech.ca (v6.ibctech.ca [IPv6:2607:f118::b6]) by mx1.freebsd.org (Postfix) with SMTP id 54A468FC17 for ; Thu, 12 Feb 2009 14:20:54 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: (qmail 33672 invoked by uid 89); 12 Feb 2009 14:21:50 -0000 Received: from unknown (HELO ?IPv6:2607:f118::5?) (steve@ibctech.ca@2607:f118::5) by v6.ibctech.ca with ESMTPA; 12 Feb 2009 14:21:50 -0000 Message-ID: <4994303A.8010206@ibctech.ca> Date: Thu, 12 Feb 2009 09:20:42 -0500 From: Steve Bertrand User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: ipfreak@yahoo.com References: <528659.6218.qm@web52102.mail.re2.yahoo.com> In-Reply-To: <528659.6218.qm@web52102.mail.re2.yahoo.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd general questions Subject: Re: ipv6 and freebsd X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2009 14:20:55 -0000 gahn wrote: > Thanks Steve: > > the router that sending RA is juniper and the protocol router-advertisement has been activated: > > ga@lab_1> show interfaces fe-0/0/3 > ... > > Logical interface fe-0/0/3.170 (Index 70) (SNMP ifIndex 59) > ... > Addresses, Flags: Is-Preferred > Destination: fe80::/64, Local: fe80::214:f600:aa2c:d403 > Addresses, Flags: Is-Preferred Is-Primary > Destination: fec0:10:5::/64, Local: fec0:10:5:0:214:f600:aa2c:d403 fec0::/10 was deprecated per RFC3879. Perhaps the Juniper unit is obeying this and just not sending the prefix in the advertisement? Everything else looks good, so lets test that possibility (as remote as it is). Take your tcpdump one step further: > lab# tcpdump -n -i bge1 ip6 > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > listening on bge1, link-type EN10MB (Ethernet), capture size 96 bytes > 17:55:44.027565 IP6 fe80::214:f600:aa2c:3c03 > ff02::1: ICMP6, router advertisement, length 24 > 18:02:46.283353 IP6 fe80::214:f600:aa2c:d403 > ff02::1: ICMP6, router advertisement, length 24 # tcpdump -n -i bge1 -s 0 -w /path/to/file.pcap ip6 After a time of that running (there won't be any STDOUT output), stop the capture, and open the file in Wireshark. (I've never figured out how to get tcpdump to read the data portion of the packets from a file). With the -s0, it will capture the headers and the data of each packet, so you should be able to tell whether the RA announcements do actually contain the prefix you are trying to get configured. Something that I should have asked from the get-go...do you have any sort of firewall running on the box? I'll set this up in my lab here today. Although we don't have any Juniper units, I'll see if I can recreate the problem with Cisco hardware. You may also want to test using a non-deprecated address space. The documentation address may work for instance. Steve