Posts Tagged ‘Data Center’

IPV6: clatd, a component of 464XLAT, for Fedora and EPEL

Friday, September 2nd, 2016

The World is running out of IPv4 addresses, but luckily, we have IPv6 here now, and running the whole data center on IPv6 only is not just happening, it’s becoming the standard. But what if you have an app, a daemon, or a container that actually needs IPv4 connectivity? Then you may use 464XLAT to provide an IPv4 tunnel through your IPv6 only infrastructure. clatd is one component in 464XLAT.

clatd is a CLAT / SIIT-DC Edge Relay implementation for Linux. From the github wash label:

clatd implements the CLAT component of the 464XLAT network architecture specified in RFC 6877. It allows an IPv6-only host to have IPv4 connectivity that is translated to IPv6 before being routed to an upstream PLAT (which is typically a Stateful NAT64 operated by the ISP) and there translated back to IPv4 before being routed to the IPv4 internet. This is especially useful when local applications on the host requires actual IPv4 connectivity or cannot make use of DNS64 (…) clatd may also be used to implement an SIIT-DC Edge Relay as described in RFC 7756.

Note that clatd relies on Tayga for the actual translation of packets between IPv4 and IPv6.

Yesterday, I pushed clatd for fedora testing and epel testing. Please test and report feedback by bugzilla.

For more information on clatd, see the documentation included in the package, or the clatd github home. For more info on Tayga, visit http://www.litech.org/tayga/.

For general information about the process of transisioning to the britght future of IPv6, consider https://en.wikipedia.org/wiki/IPv6_transition_mechanism

Redpill Linpro is the market leader for professional Open Source and Free Software solutions in the Nordics, though we have customers from all over. For professional managed services, all the way from small web apps, to massive IPv4/IPv6 multi data center media hosting, and everything through container solutions, in-house, cloud, and data center, contact us at www.redpill-linpro.com.

Tayga, stateless NAT64 implementation

Monday, January 25th, 2016

If you are planning for an IPv6 only Data Center (and if you plan for the future, you are doing that) you may have noticed that there are applications out there that are just not ready for IPv6 yet. So you need some kind of 6-4 translation, either locally or in the network. From the Tayga wash label:

TAYGA is an out-of-kernel stateless NAT64 implementation for Linux that uses the TUN driver to exchange IPv4 and IPv6 packets with the kernel. It is intended to provide production-quality NAT64 service for networks where dedicated NAT64 hardware would be overkill.

Tayga is production quality software. We use it for ipv4 access for large amounts of production nodes every day. It is for example well suited for giving 6-to-4 network access for docker nodes. You may find more information about Tayga on it’s homepage: http://www.litech.org/tayga/

I pushed tayga-0.9.2-3 to Fedora 22 and 23 stable today. It will trickle down to your local mirrors in a couple of days. I have also forked tayga for epel5, epel6, and epel7. Please contribute by testing tayga for EPEL: https://bodhi.fedoraproject.org/updates/?packages=tayga

Update: tayga is now available in EPEL

Redpill Linpro is the market leader for professional Open Source and Free Software solutions in the Nordics, though we have customers from all over. For professional managed services, all the way from small web apps, to massive IPv4/IPv6 multi data center media hosting, and everything through container solutions, in-house, cloud, and data center, contact us at www.redpill-linpro.com.