JPIX started XLATE trial service for our IX members in July 2010.
I talked about this service status at APRICOT 2011 last month.
Please see a presentation material below.
http://www.apricot-apan.asia/__data/assets/pdf_file/0018/31365/Masataka_Mawatari_IPv6v4_Exchange_Service_for_sharing_IPv4_addre
On Fri, 4 Mar 2011, Simon Perreault wrote:
On 2011-03-04 08:32, Francois Tigeot wrote:
http://ecdysis.viagenie.ca/
What about its integration in upstream software ?
None of it is integrated yet.
but I've not
seen any real information for the nat part in pf or iptables.
Pf has changed a
On 2011-03-04 08:32, Francois Tigeot wrote:
>> http://ecdysis.viagenie.ca/
>
> What about its integration in upstream software ?
None of it is integrated yet.
> The dns64 part is integrated in the newly released Bind 9.8
That's not our code. ISC made their own DNS64 implementation for Bind 9.8.
On Fri, Mar 04, 2011 at 08:25:15AM -0500, Simon Perreault wrote:
> On 2011-03-03 15:31, Elliot Finley wrote:
> > So as not to re-invent the wheel - if you are currently doing NAT64 in
> > production and are willing to share:
> >
> > What software/hardware are you using?
>
> http://ecdysis.viageni
On 2011-03-03 15:31, Elliot Finley wrote:
> So as not to re-invent the wheel - if you are currently doing NAT64 in
> production and are willing to share:
>
> What software/hardware are you using?
http://ecdysis.viagenie.ca/
> Why?
Dogfooding.
http://en.wikipedia.org/wiki/Eating_your_own_dog_foo
Apologies, was thinking 6over4 ... And I still think we could have done
better at naming these (DSTM, anyone?)
Thanks, TJ's Droid2
On Mar 4, 2011 2:40 AM, "Owen DeLong" wrote:
> He is mistaken... HE Tunnels are an example of 6in4 and it is not
deprecated,
> but, some original mechanisms for 6in4
9:27 +0900
Para: Jordi Palet Martinez
CC:
Asunto: Re: Real World NAT64 deployments
>> 6to4 is an automatic transition mechanism
> ^ non-
>
>which allows an end site to have horrible v6 pseudo-connectivity over a
>provider who ha
> 6to4 is an automatic transition mechanism
^ non-
which allows an end site to have horrible v6 pseudo-connectivity over a
provider who has not deployed ipv6
randy
On Thu, 2011-03-03 at 16:33 -0700, Elliot Finley wrote:
> You are correct. I'm talking about the NAT64 portion of NAT64/DNS64.
>
> Elliot
Andrews & Arnold (http://aaisp.net.uk) have a NAT64 gateway which is
operated by a Firebrick 6202, IIRC.
As an ISP this is really for a handful of IPv6-only
He is mistaken... HE Tunnels are an example of 6in4 and it is not deprecated,
but, some original mechanisms for 6in4 to which he may be referring were
deprecated.
http://en.wikipedia.org/wiki/6in4
Owen
On Mar 3, 2011, at 11:17 PM, Karl Auer wrote:
> On Thu, 2011-03-03 at 20:27 -0500, TJ wrote:
> > 6to4 is handy as a toy or for experimenting, but it relies on a loose
> > network of generous volunteers who, while generous, are neither
> > generous nor numerous enough to support production traffic.
>
> Any ISP that is delivering IPv6 to their clients would be insane
> to not run a 6to4 rel
On Thu, 2011-03-03 at 20:27 -0500, TJ wrote:
> 6in4 == deprecated automatic tunneling mechanism ... HE is an example of
> manually configured Protocol41 encaps.
Deprecated? Do you have a reference...?
Thanks, K.
--
~~~
Karl Aue
HE uses 6in4. 6in4 is basically the same protocol as 6to4, but, with defined
end-points for point-to-point tunneling packets from multipoint to multipoint.
6to4, conversely, uses anycast to identify the tunnel exit point towards the
IPv6 network or to identify the tunnel entry point towards the IP
On Mar 3, 2011, at 1:54 PM, William Herrin wrote:
> On Thu, Mar 3, 2011 at 3:41 PM, Hammer wrote:
>> I need a cheat sheet.
>>
>> nat64
>> 6to4nat
>> 6in4nat
>> etc...
>
> 6to4 and 6in4 are not NAT. They're tunnels (VPNs) that allow two IPv6
> nodes to talk to each other via an IPv4 backbone.
>
2011 7:17 PM
To: William Herrin
Cc: nanog@nanog.org
Subject: Re: Real World NAT64 deployments
Any ISP that is delivering IPv6 to their clients would be insane
to not run a 6to4 relays for return traffic to 2002::/16.
Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Austral
In a message written on Thu, Mar 03, 2011 at 08:27:18PM -0500, TJ wrote:
> And 6to4 doesn't allow IPv6 to talk to IPv4, contrary to what the name seems
> to imply :).
>
> Some poorly chosen names for our tunneling, yes?
I think 6automaticallyover4 was determined to be too long. :P
--
Leo
6in4 == deprecated automatic tunneling mechanism ... HE is an example of
manually configured Protocol41 encaps.
And 6to4 doesn't allow IPv6 to talk to IPv4, contrary to what the name seems
to imply :).
Some poorly chosen names for our tunneling, yes?
Thanks, TJ's Droid2
On Mar 3, 2011 6:27 PM, "
In message , Will
iam Herrin writes:
> On Thu, Mar 3, 2011 at 5:01 PM, Hammer wrote:
> > A little better. So what's the difference between 6to4 and 6in4?
> Isn't 6in4 what HE uses?
>
> I haven't used 6in4 so I couldn't tell you.
>
> 6to4 is a stateless tunnelling protocol. You have a dual-stack
>
> Ok, apparently there is NAT64 and there is NAT64. I don't believe the
> poster was talking about a v6 load balancer VIP with v4 servers. I
> think the OP is talking about the NAT64 portion of NAT64/DNS64 where
> native v6 source and destination IPs are NATed to v4 destination and
> source IPs
On Thu, Mar 3, 2011 at 5:01 PM, Hammer wrote:
> A little better. So what's the difference between 6to4 and 6in4? Isn't 6in4
> what HE uses?
I haven't used 6in4 so I couldn't tell you.
6to4 is a stateless tunnelling protocol. You have a dual-stacked
router. It has an IPv4 address, 1.2.3.4. Theref
> From: Elliot Finley
> Sent: Thursday, March 03, 2011 12:31 PM
> To: nanog@nanog.org
> Subject: Real World NAT64 deployments
>
> So as not to re-invent the wheel - if you are currently doing NAT64 in
> production and are willing to share:
>
> What software/hardw
> -Original Message-
> From: Elliot Finley
> Sent: Thursday, March 03, 2011 12:31 PM
> To: nanog@nanog.org
> Subject: Real World NAT64 deployments
>
> So as not to re-invent the wheel - if you are currently doing NAT64 in
> production and are willing to s
Regards,
Jordi
-Mensaje original-
De: Hammer
Responder a:
Fecha: Thu, 3 Mar 2011 16:01:29 -0600
Para: William Herrin
CC:
Asunto: Re: Real World NAT64 deployments
>A little better. So what's the difference between 6to4 and 6in4? Isn't
>6in4
>what HE uses?
>
&g
A little better. So what's the difference between 6to4 and 6in4? Isn't 6in4
what HE uses?
-Hammer-
"I was a normal American nerd."
-Jack Herer
On Thu, Mar 3, 2011 at 3:54 PM, William Herrin wrote:
> On Thu, Mar 3, 2011 at 3:41 PM, Hammer wrote:
> > I need a cheat sheet.
> >
> > nat64
>
On Thu, Mar 3, 2011 at 3:41 PM, Hammer wrote:
> I need a cheat sheet.
>
> nat64
> 6to4nat
> 6in4nat
> etc...
6to4 and 6in4 are not NAT. They're tunnels (VPNs) that allow two IPv6
nodes to talk to each other via an IPv4 backbone.
nat64 is NAT. It allows IPv6 endpoints to communicate with IPv4 end
I need a cheat sheet.
nat64
6to4nat
6in4nat
etc...
-Hammer-
"I was a normal American nerd."
-Jack Herer
On Thu, Mar 3, 2011 at 2:31 PM, Elliot Finley wrote:
> So as not to re-invent the wheel - if you are currently doing NAT64 in
> production and are willing to share:
>
> What software/h
So as not to re-invent the wheel - if you are currently doing NAT64 in
production and are willing to share:
What software/hardware are you using?
Why?
TIA
Elliot
27 matches
Mail list logo
