7 ms·
IPv6 Fundamentals: A Straightforward Approach to Understanding IPv6, 2nd Edition
- woleium 5y agoI first learned ipv6 22 years ago when I did my CCNP. Since then we've been two years away from migration every year.
- betaby 5y agoClose to 90% mobile phones in USA/Canada have IPv6 connectivity for about 5 years.
- bikingbismuth 5y agoMy home ISP gives me an IPv6 address as well. Much of the internal infra that I use at work has AAAA records in our local DNS. I feel comfortable saying IPv6 is here.
- thecybernerd 5y agoI wish Verizon would start offering IPV6 across their wireline footprint.
- tomschlick 5y agoThey are. I was part of the test rollout of IPv6 when I lived in Richmond, VA last year. It worked flawlessly so I'd assume they should be set for a greater rollout sooner rather than later.
- deathanatos 5y agoWhen was that? It's been "coming soon" on Verizon's own FAQ[1] for almost half a decade now. I'm in one of the major MSAs along the eastern megalopolis, and there's no IPv6 here. [1]: https://web.archive.org/web/20171220092540/https://www.verizon.com/support/residential/internet/getting-started/learn-about-ipv6 https://web.archive.org/web/20171220092540/https://www.veriz...
- tomschlick 5y agoLast year. I got it at the beginning of 2020 IIRC and I moved from VA to another state in sept 2020.
- bushbaba 5y agoI’ve often wondered if ipv6s less human readable addresses is the primary cause. I dread using and interacting with ipv6, compared to ipv4. Sure ipv6 solves a lot of scaling challenges, but it is so much harder to grock at first glance.
- ashton314 5y agoAddress abbreviation helps a bunch. IPv6 (not an expert, but I’m in a class right now!) suffers from severe 2nd system syndrome: it overhauls DHCP in a totally convoluted way, overhauls so much of how the IP layer works, etc. It really is a mess.
- 1ncorrect 5y agoI think it would have been better to label everything that DHCPv6 covers with an entirely new name. Its functionality is fine for what it’s tasked to do, and much of the confusion I’d argue stems from those who (think they) know IPv4 trying to map their understanding to IPv6 unmodified.
- ospray 5y agoFor all of it's faults Port Address Translation (NAT) sure has a way of making the address size more manageable.
- hansel_der 5y agowe managed to connect a few billion devices using about 200mio addresses and a protocol that was designed for a few thousand hosts. successfull technology indeed.
- jml7c5 5y agoIt's a silly bikeshed, but I wish they'd gone for hyphens as separators rather than colons. There's something about [abcd-ef12-3456-7890-abcd-ef12-3456-7890] that's nicer to read than [abcd:ef12:3456:7890:abcd:ef12:3456:7890]
- TrumpRapedWomen 5y agoThe fundamental mistake was not making IPv6 backwards compatible with IPv4. You can't just migrate to IPv6, you need to run dual stack which means twice as much work a lot more complexity. I'm 40 and don't expect to ever be able to not need an IPv4 IP to browse the Internet.
- rjsw 5y agoI have had native IPv6 from my ISP for 11 years now.
- pvtmert 5y agoMeanwhile, entire countries missing it today...
- hansel_der 5y agoand there are those having ipv6 access from the isp but disabling it in the router because it caused some (badly timed) fuckups in the past.
- harshreality 5y agoOver 30% global adoption for google users, to the extent of having a public ipv6 address and using ipv6 preferentially: https://www.google.com/intl/en/ipv6/statistics.html https://www.google.com/intl/en/ipv6/statistics.html
- usr1106 5y agoIf you watch the graph in smaller time scale you see adoption is higher on weekends than on weekdays. I guess that means consumers using Google and similar from their mobile phones have a high rate of adoption. They did not do it themselves. While the average medium (and why not big) company IT department has not started to do anything and is IPv4 only. Seen in the graph when people work Monday to Friday and especially around Christmas.
- Scott_Sanderson 5y agoBoth of my ISPs offer IPv6 gateways. I set them up and visited several IP6 websites. I crypto exchange I use frequently, Bittrex, allows to whitelist an IP address. Since I have a static IPv4, I did so. Problem is, my request to bittrex always goes out the IP6 gateway and Bittrex does not recognize me. I had to shut down the IP6 gateway to get into the account.
- scrollaway 5y agoYou have a static ip4 but not a static ip6? Or does bittrex not allow whitelisting an ip6?
- usr1106 5y agoStatic IPv6 are rare by default because computers for end users should use IPv6 privacy extensions. In Ubuntu 16.04 LTS timeframe privacy extension was still broken a bit, so it did not work on every network adapter. Nowadays it just works, unless a crazy network gives you only /128. I have no idea about Windows and MacOS.
- Symbiote 5y agoThe whole address changes, but there's usually a prefix that doesn't change, e.g. /64. Whitelisting the /64 is then equivalent to whitelisting a single IPv4 address with a NATted network behind it, although since ISPs may use different IPv6 prefix lengths it might not be easy for users to know what they should use. ("ip ad" etc show the current address with prefix.)
- hansel_der 5y ago> unless a crazy network gives you only /128 like the incumbant cable network in germany (vodafone) ...
- usr1106 5y agoWhat? Germany is one of the most privacy-aware countries. So people should make some noise. Of course internet is still a bit new for all of us as the still-chancellor noted to too long ago... So technical incompetence does not surprise me. Vodafone prefers to make headlines with criminal sales practices.
- vkdelta 5y agoWhat is special with this book? It is standard Cisco press book.
- 1_player 5y agoNo one is talking about it, the rest of the comments are unrelated war stories about IPv6 deployment with have nothing to do with TFA.
- doingtheiroming 5y agoThe fact that the current version was published 2017 (so 2016 info) and IPv6 is still a moving target? I suspect that isn’t the reason to post it but it’s relevant.
- Asmod4n 5y agoYou might also be interested in https://ipv6.he.net/certification/ https://ipv6.he.net/certification/
- znpy 5y agoIt seems that no one is actually debating the book itself. So I ask: - is it good as a first book on ipv6? - does it require Cisco hardware or is it generic enough?
- justshowpost 5y agoYou are asking in vain, Reddit News clientele are worrying about globalist stuff like saving our planet from climate hoax etc. While the book is typical Cisco Press style, very in-depth, CCNP+ tier complex, that's too much for redditors.
- usr1106 5y agoHas anybody read the book? How would you describe the writing style?
- yardstick 5y agoTaken from a previous comment I’ve made re IPv6: IPv6 is fundamentally not ready for real world use within small/medium businesses and homes IMO. At least not without NAT. Why? - Can’t just simply put one IPv6 router/firewall behind another. Not all IPv6 routers support DHCP-PD, and even if they did, you could have 2-3-4 levels of routers/firewalls at a business. I’m not making this up- retail/gas/food industries often have a plethora of networks at a location, and the business/franchise owner is not tech literate, or even if they were, the equipment is managed by third party vendors and they don’t want to customise their IP network for each location. It makes for messy deployment and maintenance. - Can’t just simply open a firewall rule on the main site router to forward say HTTPS to an internal service. Why? Not all ISPs give static IPv6 prefixes, not all PCs/servers/devices support DHCP6 for static leases, and then there’s IPv6 privacy addresses. Yes, you can statically configure (only if ISP is static too!). No, I don’t want to open the port to all devices on the LAN and no I can’t rely on each device to be running their own firewall (let alone a properly configured one!). - WAN failover / multiple ISPs is hard. You have a fibre primary feed, and a secondary cellular/5G feed. Each has different IPv6 addresses. How do you ensure the right ISP is used at any given point? IPv6 shifts this decision to the client. This makes load balancing and policy based traffic routing (eg VoIP over fibre 1, FTP over fibre 2, etc). Also the cost of using a multi-homed IPv6 subnet & BGP in a SME/retail business is out of the question (plus the cellular ISP wouldn’t support it anyway). All the above works fine out of the box with IPv4 and NAT. It’s bread and butter easy. At the cost of not having dedicated unique public IPs but these places simply don’t need them. What IPv6 should have done to ensure a smooth migration is allowed for NAT from the very start. That would have let everyone who needed public IPs get them straight away, and those that didn’t to still migrate anyway with as little drama as possible. But it’s just not the case, NAT has been slowly added but it’s support is far from ubiquitous that IPv4 has.
- jiggawatts 5y agoThe only "problem" here that is caused by IPv6 is the SD-WAN / multi-provider scenario. Even that is solvable. There are so many IPv6 addresses that your local router can have a unique routable range that it can hand out to the local network, "masking" the external internet provider addresses in the same way that IPv4 routing does it. That's not NAT, that's just routing. E.g. I have a customer that uses a non-RFC1918 public range internally and they have 5 ISP uplinks. They don't need to renumber their internal range just to fail over to another link. ALL of the other issues are caused by vendors selling garbage products that have IPv6 as a "checkbox" tick without real support. The real problem is that network engineers around the world let them get away with it, because they avoid IPv6 because of this perception that it isn't mature. The protocol is over two decades old! It's been fully supported since Windows 2000! My phone is IPv6. My fibre LAN is IPv6. It just works. What doesn't work is this attitude where people just like you continue to pay for products that only pay lip service to the future. I've gone on rants here before about enormous service providers like AWS and Azure providing IPv6 "support" that is an absolute garbage fire. Totally worthless. Useless beyond belief. Literally counterproductive in the case of Azure, where turning on IPv6 anywhere will break unrelated IPv4 functionality! Nobody ever chimes in to say: "Yes, we agree, this is bad." Nobody ever says "Microsoft should fix this!" Nobody has a problem. So now we have situations like the one you just described, where people are still buying routers in 2021 that that can't handle the most basic IPv6 functionality. IPv4 addresses are now USD $40 each and rising exponentially. I really do hope the COVID case number graphs taught some of you in a visceral sense what the world "exponential" means. Hint: it doesn't mean that it'll cost $60 in a decade. Try $40000, each. My ISP uses carrier-grade NAT on IPv4, breaking sites all over the place. I had to call them to enable a dedicated IPv4 address. Their annual investor report says that they will run out within a couple of years. Get one now while you can is the message. Do you have any idea how much code is required for two PCs to communicate directly now, with up to 4 NAT layers as a common scenario? It's a huge library you have to integrate in your code and then you need a cloud service to assist it. This is madness, and network engineers around the world are perpetuating it.
- gorgoiler 5y agoI highly recommend the Cisco material. I learned IPv4 from blog posts written by people who read other blog posts and HOWTOs. It worked because I came along when everyone had (and needed) the experience. IPv6 is harder because it’s the upgrade path, not a necessity. For that, I needed good professional source material. As do you: treat yourself!
- justshowpost 5y agoShould be (2017)