Complete noob here sorry if this is an easy question.

AKEGEC

@gertjan, @JKnott, the problems with IPv6 , it's not completely implemented while it's been almost 30 years later since the birth of IPv6, but there is no or little improvement. Why? M.A.G.A. don't want to invest in it, just recently they have changed of heart. So you wonder when I will use IPv6 for my clients? When all internet connections use IPv6 only network. By then new technology are equip with IPv6 security futures.

Does anyone know what M.A.G.A. stand for? Microsoft, Amazon, Google and Apple or Make America Great Again?

JKnott

@akegec said in Complete noob here sorry if this is an easy question.:

Why you must disable IPv6: https://www.youtube.com/watch?v=Vt4Jl4t43ug

I just watched the first segment of that video. What a load of nonsense.

JKnott

@akegec

I first read about IPv6 in the April 1995 issue of Byte magazine. I have been using it at home for 11 years, next month. These days, many ISPs provide both IPv4 and IPv6, as mine does, though some (including my cell phone company) use 464XLAT to provide IPv4. Sadly, some ISPs are still stuck in the dark ages and provide only IPv4.

As for "MAGA", we'll have to see what happens now that there's a competent president in office.

johnpoz

There is really only 1 reason to disable IPv6 - and that is your not up to implementing it. There is a learning curve for sure. There is also some really crappy implementations out there from some ISPs. These can many times be overcome with say a tunnel as mentioned.

As of yet I have not seen any public resource that would require a user to have IPv6.. So unless there is something the user needs that requires it. Love to hear what that is ;) Then sure there is nothing say they have to use it. And it can make their network simpler and easier to manage by just not enabling it.

Saying you "must" disable it is pure and utter BS.. It for sure is the future, but as of yet - unless your on a mobile device.. Many of them use IPv6 only, with gateway on the provider to allow talking to IPv4 addresses.. T-Mobile here in the US is that way, at least in my part of the country. Cell phones going to IPv6 has for sure reduced the strain on the IPv4 space that is for sure.

Or your in part of the world where ISP will not give you an IPv4, or they only give you cgnat IPv4 and if you want to allow for unsolicited inbound traffic and you can do that via IPv6.

But I would say - if the user is having issues with it, and they do not have the desire or skill or time to fix whatever the issue is. Then sure a simple solution is to just not use it at this time. Also if you feel that IPv6 might be part of a problem your trying to troubleshoot - there is nothing wrong with turning it off to test/troubleshoot to validate that yes indeed something is not right with the IPv6 connection, or the configuration or the client use of it, etc. etc.

IPv6 is a bit more than just a longer IP address - there are some fundamental differences for sure. And if the user is not up to speed on understanding these, then turning it off is valid advice.

Users smart enough to disable it, and doing so sure and the hell is not going to slow down the global migration to it ;)

JKnott

@akegec said in Complete noob here sorry if this is an easy question.:

So you wonder when I will use IPv6 for my clients?

Several years ago, your clients would likely be running IPX, yet I bet they've probably moved to IP by now.

johnpoz

IPX was not something that could have ever scaled to what is now the internet ;)

So yeah if you wanted to be on the "internet" you had to use tcp/ip.. While not an overall bad example of transition to a new protocol for communication.

It fails in that to use xyz you needed to use IP. With ipv4 vs ipv6 - I can still use xyz, without having to use ipv6.. When I can not get to xyz without ipv6 is when you will see the migration accelerate.

JKnott

@johnpoz

At the time, IPX was used in businesses and connected offices within an organization. However, there was initially no concept of an "Internet". Also, when Vint Cerf came up with IPv4, his intent that it was only an experiment to demonstrate the concept and the final version would have a larger address space. Unfortunately, IPv4 "escaped". There were other routeable protocols, such as DECNet, SNA and Appletalk, too.

BTW, the idea of connected networks goes back long before IP. Many years ago, I used to work on a network in the Air Canada reservation system. This network was created by (Rockwell) Collins, for use with their computers. Instead of packets, it used time slots (TDM). The idea was several of these networks could be interconnected, in the way IP did later. I first worked on the network in 1978, but it had been around for a few years before that.

AKEGEC

@johnpoz @JKnott oh you guys bring back mIRC nostalgia.

JKnott

@akegec

We also bring a lot of knowledge, based on experience. For example, I'm probably the only one here who has actually hand wired an Ethernet controller. I don't know how many others who have worked with 10base5 "Thicknet" and DECNet or SNA & token ring, as I have.

AKEGEC

@jknott there is one Asian saying that I know from former colleague. "Like rice paddy, the more contains they have, the more they bow."

rice paddy