[29] in SIPB IPv6
Re: IPv6 coordination
daemon@ATHENA.MIT.EDU (Ken Raeburn)
Thu Jul 11 19:14:57 2002
To: Noah Meyerhans <noahm@lcs.MIT.EDU>
Cc: sipbv6@MIT.EDU
From: Ken Raeburn <raeburn@MIT.EDU>
Date: Thu, 11 Jul 2002 19:14:49 -0400
In-Reply-To: <20020711224604.GT9051@locust.lcs.mit.edu> (Noah Meyerhans's
message of "Thu, 11 Jul 2002 18:46:04 -0400")
(Someone pointed out to me a little while ago that IETF is coming up,
so Bill may already be on his way to Tokyo -- another reason we might
not hear from him right away.)
> Yes, I've heard back from the person in charge of the tunnel endpoint
> (Robert Morris), and he says that he's completely done with it and we
> can have it. That's convenient, because it means that you only need to
> reconfigure your router to point to a different end point. The end
> point (for now) will be 18.24.4.45. That will change eventually, when
> we are more comfortable with its behavior and want to move the tunnel to
> one of our production machines.
That's fine. I've set it up to use that machine for now. Our
endpoint is 18.187.1.231, and packets should be flowing now. I tried
a ping, but it looks like your end isn't accepting yet:
19:08:15.497981 18.187.1.231 > 18.24.4.45: 3ffe:1ce1:0:fe30::1 > 3ffe:1ce1:2::1: icmp6: echo request (len 16, hlim 63) (ttl 30, id 8712)
19:08:15.500579 18.24.4.45 > 18.187.1.231: icmp: 18.24.4.45 protocol 41 unreachable [tos 0xc0] (ttl 251, id 23267)
>> Let me know whether you want to switch the existing tunnel or get a
>> new one, where your endpoint machine is, and the nameservers to
>> delegate the ip6.int subdomain to.
>
> The DNS servers will be mintaka, ossipee, and lampang.lcs.mit.edu.
Updated on limekiller, should be propagating to the other nameserver
(one of Bill's machines) soon, if not before I get this sent off.
> For your records, the contact for tunnel maintenence will be
> bug-network@lcs.mit.edu.
Thanks. I've noted it in the config file.
Ken
