This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ipv6-wg] IPV6 IPV4 work around
- Previous message (by thread): [ipv6-wg] IPV6 IPV4 work around
- Next message (by thread): [ipv6-wg] [training] RIPE NCC Webinars - new dates
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jan Zorz @ go6.si
jan at go6.si
Mon May 19 12:01:28 CEST 2014
On 19/05/14 05:51, Timothy Roy wrote: > I realize that there will still be a lot of networks that will have > to be able to translate over to IPV4 from IPV6 and vice versa. I also > know that most are not too willing to obtain another piece of > equipment for their system, but using a LTM (F5 LTM (which is what we > will be using this year)) to do the translation from IPV6 to IPV4. > This would be an excellent work around for quite a few issues that I > have read about such as email. I have not tested this with email but > will be testing it with our DNS very soon as I want to get our system > on the IPV6 Internet so to speak. Hi, there are several different ways how to do this, depending what you want to achieve. Let me point you to an excellent deployment oriented document written by Sander Steffan, that tells you how to enable your IPv4-only content or services on IPv6 network. http://www.internetsociety.org/deploy360/resources/making-content-available-over-ipv6/ I've been testing and running numerous mechanisms in this area in go6lab just to understand what works and what doesn't ;) Cheers, Jan
- Previous message (by thread): [ipv6-wg] IPV6 IPV4 work around
- Next message (by thread): [ipv6-wg] [training] RIPE NCC Webinars - new dates
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]