Is anyone deploying Tayga in any capacity (production, test networks, at home, 
with clatd, …)?

I’ve decided to ‘adopt’ the open source project, given it’s ability to both be 
very standards compliant (at least to the standards as they were in 2011), and 
act in virtually any translation-related role (not restricted to just CLAT or 
just NAT64 or just SIIT)

But I’m interested in hearing how you are using it, what friction you have in 
deploying it, etc.

This is mostly motivated by my desire to stand up demonstration networks for a 
variety of transition tech options, and with how versatile Tayga is, it can act 
in essentially all of the major roles involving v4-v6 translation with 
different configuration and routing tables and without any complex namespace 
setup. I’m also an embedded programmer by trade, so dealing with low level C is 
very much my thing.

https://github.com/apalrd/tayga/
[tayga.png]

[apalrd/tayga: Tayga NAT64 Daemon](https://github.com/apalrd/tayga/)
[github.com](https://github.com/apalrd/tayga/)
is where I've put the repo. I started with the original tar.gz, merged in all 
of the patches from the Debian project, plus one patch from FreeBSD, and went 
from there. I'm mostly working on an RFC7915 test suite and fixing any bugs 
identified by the test suite, and after that I can make more changes / 
improvements without worrying about hidden breakage.

Yes, I know Github does not support IPv6, but I felt like that collaborators 
are more likely to have Github accounts and know how to use it vs self hosting 
or other platforms).

Andrew
_______________________________________________
NANOG mailing list 
https://lists.nanog.org/archives/list/[email protected]/message/TQV7WOUOF2BZPSVQVWHNCOMXJ7G4DIE4/

Reply via email to