6to4 in Internet aaaa records

[Nick Edwards]

Speaking of 6to4, can anyone recommend an understandable by non
networking types, easy  setup how-to?

Preferably with the entire thing on the one box (we have only one bit
of software that does not understand ipv6, everything else does, so
are not wanting a specific dedi router type config to remote ipv4
boxes, the box is dual stack, we just need 6yp4 to send ipv6 onto its
ipv4 address -  oh and before some bright spark says it, because we
know someone will, no,  the software can not be changed, it is a
closed source binary, and they have no future plans to add ipv6 to it,
and since  it is a news server daemon, which has an enormous amount of
spool storage,we are not looking to start it fresh with something
else)

So any pointers to URLs appreciated.


On 10/5/14, Brian E Carpenter <brian.e.carpenter at gmail.com> wrote:
> On 05/10/2014 00:04, Jeroen Massar wrote:
>> On 2014-10-04 12:56, Gert Doering wrote:
>>> Hi,
>>>
>>> On Sat, Oct 04, 2014 at 12:49:00PM +0200, Gert Doering wrote:
>>>> On Thu, Oct 02, 2014 at 10:31:25PM -0400, Jeroen Massar wrote:
>>>>>> <http://www.azdes.gov>)... 2002::cf6c:8846
>>>>> That is an invalid 6to4 address as it would have a 6to4 gateway of
>>>>> 0.0.0.0.
>>>> Uh, what?
>>>>
>>>> Who are you and what happens to the Jeroen I know who understands IPv6,
>>> [..]
>>>
>>> Aliens stole the body of Gert Doering, and now he can't find the button
>>> "withdraw this e-mail" in his Outlook mail client anymore...
>>
>> Hmmm, yeah a Gert using Outlook would be an excuse, but it seems more
>> that an alien stole his dog: "User-Agent: Mutt/1.5.23 (2014-03-12)" :)
>>
>> Dear Aliens: please return our Gert!
>>
>>> Sorry, of course Jeroen is right here, and I need to sleep more before
>>> typing.  While anycast *is* the problem, of course the "exit side" of
>>> the tunnel needs an address, aka "gateway"...
>>
>> Can anybody local to Munich deliver some fresh coffee to Gert? :)
>
> I'm drinking coffee here in Auckland at 08:21, but there is no
> "send coffee" feature in Web RTC yet.
>
> Yes, everybody go and read RFC 6343 again please.
>
> Just to be clear though, a return relay for 6to4 will advertise
> a route to 2002::/16, since it must accept traffic for any 6to4
> host. But any packets sent to that AZDES address will black hole
> because the return relay will encapsulate them in IPv4 and deliver
> them to 0.0.0.0.
>
>    Brian
>