[59855] in SIPB IPv6
Re: routing to fe60::1?
daemon@ATHENA.MIT.EDU (=?UTF-8?Q?Alejandro_R._Sede=c3=b1o)
Wed Oct 21 19:20:01 2015
To: Greg Troxel <gdt@lexort.com>, sipbv6@mit.edu
From: "=?UTF-8?Q?Alejandro_R._Sede=c3=b1o?=" <asedeno@mit.edu>
Date: Wed, 21 Oct 2015 19:19:59 -0400
In-Reply-To: <smud1w7kerv.fsf@linuxpal.mit.edu>
Yeah, I was seeing ipv6 connectivity issues from m64 as well. This
should be good now too.
Just got home,
-Alejandro
On 10/21/2015 19:01, Greg Troxel wrote:
>
> Earlier I wrote, I think, about how my sixxs tunnel to occaid/boston was
> broken. That seems to be about the sixxs prefix 2001:4830:1100::/48
> being missing from occaid's IGP.
>
> I got alerts that limekiller was down and then back. Now
>
> limekiller ping-ok v4
> limekiller ping-ok v6 (from bbn sixxs tunnel via uschi02)
> limekiller ping-ok v6 to its he tunnel endpoint (from bbn/uschi02)
> limekiller ping-ok v6 to its occaid tunnel endpoint (but this
> was not working just a bit earlier)
>
> linuxpal.ipv6.mit.edu cannot reach limekiller. I am sending ripng
> advertisements for 2001:4830:2446:fe60::1/64, which is on a
> gif because RLE has asked me not to have router advertisements on the
> 18.62 ethernet. But I am not seeing any MLD reports or a route
> advertisment from limeiller. After seeing an ndp packet from
> limekiller, I manually added a default route to the v6 ll addr via the
> gif, and now I am connected.
>
> So I wonder if ripngd is running on limekiller, or is configured not to
> send ripng on the gif towards linuxpal, or what else might be wrong.
>
>
>
>
