Le 14/09/2016 à 07:22, Stacy a écrit :
As for running NAT, why? One of the points of moving to IPv6 is to get away from using NAT.
A NAT rule takes 10 seconds to set up for any network administrator, and it just works. Moreover, for those who definitely do not like NAT, there are plenty of 44.x.y.z AMPR IPv4 adresses available to the HAM community. I'm working in IT services for small businesses. I do not use IPv6 at all. I absolutely do not need it, and most of our ISPs here do not provide IPv6 connectivity. Moreover, setting up an IPv6 network, and a dual-stack IPv4/IPv6 network, creates far more problems than it solves. For example, I spent dozens of hours last month to track a bug in my firewall's provider firmware, where IPv6 rules conflicted with IPv4 ones. IMHO, IPv6 is absolutely not a feature I would request and/or enjoy, at least for the next 10 years ! -- But, as Richard said, having all the code in a common GitHub repo, also with the Wiki, and an issue tracking system, would be a great feature for me ! Even if I'm just starting my app_rpt experience, and even if I have absolutely no skills in C programming, I'll need, sooner or later, to tune some things in the code. Having a common, centralized and documented way to do that would be, IMHO, a better usage of our free time. Git, and GitHub, are the perfect tools for that. My 0.02 € ;-)