[12] in SIPB IPv6
ipv6 traffic on e40 (18.177) subnet
daemon@ATHENA.MIT.EDU (Ken Raeburn)
Fri Dec 10 23:47:18 1999
Date: Fri, 10 Dec 1999 23:47:01 -0500 (EST)
Message-Id: <199912110447.XAA24441@dcl.mit.edu>
From: Ken Raeburn <raeburn@MIT.EDU>
To: sipbv6@MIT.EDU
There's now an ipv6 tunnel endpoint on the 18.177 subnet. If your
machine has ipv6 capability (e.g., NetBSD-current as shipped; Linux or
Solaris with add-on packages), it's on 18.177, and you want to start
experimenting, go for it. Please send email to sipbv6, or at least to
Bill and me, so we know you're doing stuff.
The subnet prefix is 3ffe:1ce1:0:b1::/64. The router address is
3ffe:1ce1:0:b1::1. (The "b1" is hex for "177", the rest is MIT's /48
prefix.)
Eventually, I may get my 6to4 patches installed, and we'll probably
have a second prefix, probably something like 2002:12b1:01ba::/64 or
possibly 2002:12b5:26:b1::/64. Get used to the idea of having
multiple addresses on your machine.
Address assignment:
I *think* everything is set up for autoconfiguration to just work, but
I haven't got a machine to test it with. Autoconfiguration will query
the router for the local subnet's prefixes, and generate an EUI64
value (based on the ethernet id) to produce complete network
addresses. Anyone got a netbsd-current box on the floor they can help
test with?
If this doesn't work, or your system doesn't have the
autoconfiguration software, or for whatever other reason you want to
configure it manually, then for simplicity and ease of administration,
please use an ipv6 address derived from your ipv4 address as follows:
If your ipv4 address is 18.177.xxx.yyy, convert the decimal values of
xxx and yyy to hex, and use the suffix ::1:XXYY with the above
prefix(es) to get the address for your machine. For example, if your
ipv4 address is 18.177.19.6, 19=0x13 and 6=0x6, so one
manually-configured ipv6 address would be 3ffe:1ce1:0:b1::1:1306.
The machine acting as an ipv6 router, mumps-11, is in my office, and
is running one of the netbsd-current snapshots. In case something
goes wrong, or in case it's suspected of being broken, I've set up
krb5 root login access for some network and ops people, as well as
Bill and myself. There are currently no user accounts set up.
Eventually we can probably get people on it to do application hacking
if they don't have other machines available, but kernel hacking should
be avoided on the router, which means no AFS for now...
The network card on the machine is a little flaky. It occasionally
drops off the air for 2-4 seconds, but the kernel always seems to get
it back online.
Ken
