× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On Thu, Apr 25, 2019 at 3:04 PM Rob Berendt <rob@xxxxxxxxx> wrote:
I hear that many internal networks will remain IPv4 for years to come as there is little chance of busting the numbers in an internal network.

Interesting topic.

1-If you were starting a new business setup from scratch with modern equipment would you set up the internal side with IPv4 or just do it all with IPv6?

Personally, as long as I didn't need the specific features of IPV6, I
would go with IPV4 as I can't be 100% sure that _EVERYTHING_ that
might connect to my network will support IPV6.

If I did need IPV6 for some reason, I would run both IPV4 & IPV6
alongside each other just in case.

2-Are there other compelling reasons to go to IPv6 internally? Nothing on the horizon like some future equipment not supporting IPv4? New security stuff requiring IPv6? Anything in that genre?

I can't imagine any networking equipment NOT supporting IPV4 unless it
was designed for something specific to IPV6.

Granted, my knowledge of IPV6 is somewhat limited at this point.

It's on my list of things to study up on.

david



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.