On Tuesday 08 November 2005 15:07, Curt Howland wrote: > On Monday 07 November 2005 21:01, Nate Bargmann was heard to say: > > Well, ipv6calc shows me: > > > > ipv6calc --ipv4_to_6to4addr 192.168.1.20 > > 2002:c0a8:114:: > > > > Not that I understand IPV4 to IPV6 conversion or anything, but I'm > > not sure if the 2002 at the head of the output is significant or > > the double colons at the tail. > > I think it's a literal conversion, one bit pattern mapped onto the > other. > > The "compatibility" address is "::192.168.1.20", but I have yet to > find out what the "compatibility" mode gains. There doesn't seem to > be any automatic address/header remapping going on, so maybe it > exists so that v4 to v6 gateways could be easily defined. > > I settled on fef::192:168:1:20 because "fef:" is private address > space, just like 10.x.x.x and 192.168.x.x in v4, and until someone > tells me what compatibility mode is good for, might as well go > straight to it. I think compatability mode also works for non-private addresses, i.e. should be routed outside the local network if possible. > The adjacent colons are shorthand for "all zeros, move along, nothing > to see here". Purely for human consumption, and it does make 128 bits > easier in human communications. But yeah, it's that committee thing. > More features. I think there is a restriction that only one colon pair is allowed Cheers, Kevin
Attachment:
pgph50ol_iieQ.pgp
Description: PGP signature