All new I might buy that. But it DOES limit the techs you can bring it
to set it up at this point. And that IS an issue for a small company
especially if a startup.
I have the FrankenLab completely set up for IPV6 Internally largely for
learning. Once you get your head around the addressing rules and how
that works and what's legal etc and it works fine. I frequently now see
shares and even telnet using IPV6 here because Windows 7 and Ubuntu
default to that if they can.
Maybe I'll set up the entire COMMON lab and conference to be IPV6 just
to mess with their heads. :-) :-)
I tried to get IPV6 on the outside but my ISP (a rural wireless
provider) had the classic response: "It figures that YOU would be the
first guy to ask!" They don't have IPV6 provisioned yet.
- Larry "DrFranken" Bolhuis
www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com
On 3/30/2015 8:00 AM, rob@xxxxxxxxx wrote:
Actually Jim, I agree with you. But, if you were starting up a whole new
company, branch, etc. With the latest state of the art networking
equipment and all data processing gear using the latest versions of their
respective operating systems, why not start out with IPv6 for internal
use?
After all, it's not like going from the English system to Metric. :-)
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.