Finally, a good introduction to IPv6. Systematically walking through the development process makes it all come together very nicely at the end. looking forward for more brilliant videos on IPv6 from you!
Even seasoned network engineers such as myself are confused by IPv6 because, as you noted, it requires us to "forget" everything we know about IPv4 and start from scratch. This is not easy to do but your video has helped me make progress on coming to terms with the IPv6 space. Thank you for providing this excellent resource!
Yeah - In college for me (1992-1993) we learned IPv4. The TCP vs UDP protocols are familiar, as we learned in Operating Systems. The organization of the IPv6 addresses is completely new. I'm playing with OpenWRT now, and at least I know why my PCs Link Local address starts with fe80:: Seems like ICMP is still used for ping.
The best set of IPv6 videos on youtube. Thanks for the clear and concise explainer. Most stop at a simple explanation of "what is IPv6". You actually explain how to use it. I was finally able to set up IPv6 on my network.
Excellent introduction to IPv6. I really hope that you will follow this up with many more topics like dual stack, firewalling and others (like VLANs) that an average person needs to understand when creating a small office or home IPv6 network. We are more than happy for you to do this as part of the next OpenWRT episode.
Hi Manoj, the topics that you mention are definitely the right ones - I'd add to these: Unicast, Anycast, Multicast (Router solicitation, Router Advertisement, Duplicate Address detection), NDP ;-) Thanks for the feedback !!!
As a network instructor for many years (decades even!) I totally endorse your approach to describing IPv6 - do NOT try to compare its features with IPv4. It is a new protocol. Loved the address scope explanation. One thing though - it is still the same old UDP and TCP - regardless of the Network layer protocol. Looking forward to your explanation of anycast - that often causes students difficulty (mostly because they try to compare it to broadcast.)
Many thanks Aubrey! W/r to anycast, my preferred analogy is calling the emergency number- you always call the same number but you would land in a different call center depending on the network you place the call from and the time of the day ;-)
He's right though, there's is no TCPv6 or UDPv6. What you're referencing is the field that occurs in the IPv4 and IPv6 header that indicates *what type* of layer 4 header *follows* after the IPv4/v6 header. TCP and UDP are the same for either one.
Absolutely! I don’t contradict ;-) The only reason I emphasize on udpv6 and tcpv6 is to build context for the importance of icmp for the ipv6 protocol ;-)
Personally I feel like the addressing part is not that complicated and not that different from IPv4. IP address of a certain number of bits with a subnet mask of a certain number of bits (cidr) is all the same just longer addresses. The explanation of scopes is good though and important but also this is not too dissimilar to rc1918 addresses. The part I think that a lot of people get confused about is routing, how it happens and why as well as different configuration setups besides SLAAC, like DHCPv6, RA/router advertisements, prefix delegation and interface tracking. A lot of people are used to thinking in terms of NAT which is why I don't disagree with this approach but even without comparison or even mentioning it might be important to stress especially for home users who are used to having to forward ports that this isn't a thing. No forwarding ports, instead you block ports with a firewall on the router or local machine. I'm not sure a lot of people fully understand with IPv6 and a typical home router that their pc is now directly accessible on the public internet instead of hiding behind a NAT (which isn't a firewall - it just doesn't know where to send incoming traffic unless you tell it).. While I understand this is an introduction, I had to understand all of that when setting up my own home network even. Though I still don't understand why I can't seem to track or delegate to my 2nd WAN interface, only get one /56 over dhcp and I can't ask for several smaller prefixes or seem to delegate a /64 or something to secondary wan..works fine for lan interfaces though.. not a huge deal but my ocd doesn't like seeing an adapter with unassigned address.
@@forbiddenera > with IPv6 and a typical home router that their pc is now directly accessible on the public internet that obviously depends on the router, I'm not sure what you mean by "a typical home router" but all the ones I've encountered do not allow incoming traffic by default, as should be true for any network device that isn't garbage.
This is an absolutely excellent video and in my opinion it's a must-watch for anyone starting out on IPv6. I can honestly say that if I'd been able to watch this 15 minute introduction when I first looked at IPv6 it would have saved me many many many hours of going back and forth through text books trying to get my head around the concepts - and your approach to explaining it is brilliant, and I totally get what my problem has been until now in learning IPv6 - I was always trying to find an IPv4 analogy! Your video has got me over that hurdle, explained what the fundamentals are and what I should always keep in mind. It's made understanding and mastering the conceptual basis of v6 so much easier. Keep up the good work and I say that as one very Patreon patron!👌👍😄
Hi Ray, first off - thank you very much for being a patron!!! I am so glad that so many people seem to like the video (at least from what I read in the comments) - it looks like disconnecting from IPv4 is really the key for everyone here. Many thanks for the friendly feedback!
Thank you Marc. Your video helped me to turn the fear, to something that looked very strange, into a will to delve further into it to learn something new. With your guidance, I am ready to take that journey and learn along from your future videos about this topic.
Hi, that's great feedback, many thanks. I experienced exactly the same. It was a great unknown until I took all my courage and stepped into that course. And after all now I realize that it is fun. I'll definitely do follow ups.
The key realisation for me was around the fact that hosts will almost always have multiple IPv6 addresses. Of course we could always have multiple addresses in IPv4 as well, but it was typically the exception rather than the rule. In IPv6, everything has multiple addresses. I also have a /56 prefix delegation from my ISP, and I've enjoyed the challenge of setting this up on my pfSense based firewall / router. Compared to the 1 I(public) Pv4 address , the numbers of IPv6 addresses I get is just staggering!
Hi Aaron - I went through exactly the same experience here. When I saw the many IPv6 addresses on my laptop the first time it totally freaked me out. And - as you say - the size of the address space is just overwhelming ;-)
"Of course we could always have multiple addresses in IPv4 as well, but it was typically the exception rather than the rule." Not entirely true. Your host always has 127.0.0.1 - though that's a bit cheeky. What's less cheeky is if a NIC is configured with address 192.0.2.1/24, it can receive/listen for messages destined to 192.0.2.255 (local broadcast). While not particularly obvious, your host has multiple IP addresses. It just doesn't really send with the broadcast address as source. Your IPv4 host also uses another address - 0.0.0.0. This one comes into play specifically for DHCP. If you look at the source address of a DHCP discover packet, you'll see this as the source address. In fact there's nothing stopping you from say, booting up a host on a network without DHCP (or disabling the DHCP client), grabbing an IPv4 link-local address (APIPA), configuring that statically on the interface, and then re-enabling DHCP for an additional address.
@@Jamesaepp "Your host always has 127.0.0.1" It's actually more than you think ^^. Even though IPv4 has such a limited address space, they dedicated a whole class A net to the local host, not just a single address. 127.0.0.1 is just the most commonly used and is usually mapped locally to "localhost". However 127.45.12.42 is also a local loopback address. The entire 127 net is local loopback. So 1/256th of the whole v4 address space is wasted. In IPv6 they decided that a single address is enough. If you need more, you can always assign more, but it's not implicit. Note that (0.0.0.0) is not really an address, it's merely a wildcard for the whole network to indicate no particular address. As you may know, when binding a socket, you can either bind it to a local address that the socket should listen to, or bind it to (0.0.0.0). That means the socket would be bound to all local addresses. In other words if a packet arrives at your NIC, it doesn't really care what the destination address is. Since it arrived at your NIC, it's meant for you. A lot servers by default bind to (0.0.0.0) so they accept any packets, no matter to which IP they were directed to. However explicit binding is needed if you want to run several servers on the same machine on the same port. You just need to bind each it to different local addresses. Locally you can bind servers to different local host addresses and it would work fine, locally. So you can run a server on 127.0.0.1:5555 and one on 127.0.0.2:5555. Of course you can only connect to those two servers locally, so this is just an example. Though If you bind a server to (0.0.0.0), you can't bind another socket to the same port as it 0.0.0.0 binds to all addresses. A single end point (IP + protocol + port) can only be used / bound once.
Hi Ben, I am honestly and fundamentally happy each time someone tells me that my videos could help them to achieve something. Thanks a lot for your friendly feedback.
03:40 and 3:58 Please note you always HAVE TO shorten the longest run of consecutive 16bit 0 fields, therefore FF:0:0:0:1::1 would be wrong too. When the length of the consecutive 16-bit 0 fields are equal, the first sequence of zero bits MUST be shortened.
This guy is a genius MashAllah what an explanation and how he describe step by step that's wonderful. Amazing, Bravo!! I want a teacher like you, please make more videos on IPV6 Thanks for the good knowledge and explaination.
Going to learn IPV6 for future reference. For now, I have two lan adaptors on both my desktop and laptop. On each machine, I have one adaptor handling IPV4, and the other handling IPV6. The adaptors handling the IPV6 are ALWAYs moving more data than the IPV4. Almost twice as much sometimes. Anyone hating on IPV6 better get with it. Its more prominent than you think. I have Starlink as an ISP.
Well explained from scratch, thank you Marc. Good approach in asking us to forget what we know about IPv4 and in the end, after all is as clear as muddy water, I would say IPv6 is still quite similar to IPv4
Hi Thomas - yes it is after all. Just people (including myself of course) tend to be "mentally stuck" in NAT. WE tend to forget that NAT is a workaround and that it is not Firewall ;-)
amazing video, loved how you kept it simple and made sure it's not redundant. SO THANKFUL FOR THIS VIDEO, it has been super helpful in terms of wrapping up how the big picture looks like and also how the little details work together.
Your introduction was spot on. It's still frustrating to me and shutdown ipv6 as much as i can in my home because of it. My modem has a IPv6 address but I have IPv4 on my WAN port. I don't think I need v6 on my LAN. It would just be a learning tool if anything.
Finally a comprehensive explanation... hope you had underlined/marked the digits when talking about subnetting for easy visualization... waiting for your video explaining why broadcast is not anymore... and how anycast mechanism works along the route in the intermediate nodes... ;-)
ABSOLUTELY the best one of these I have ever watched...and there have been 100s. I love how you break it all down, and I too struggle with differentiating IPv4 and IPv6. I am still struggling with IPv6 (in my home with pfSense as router and a Windows 2019 server ADDS/DNS/DHCP setup). I cannot get that server to hand out addresses (well I can - but they cannot get to the Internet over IPv6 only (every test site I visit shows IPv6 failures). Looking forward to your other videos, and maybe I can figure this out. 👍
Thank you! I’m very curious if one would use 2 VLANs, one setup as v6 only and another v4 only for your local devices if the speeds etc would be same? Also wandering if your local network is v6 only, if your ISP router could act as a ‘v4 gateway’ to the internet.
Thank you Marc for this! Very helpful! I look forward to your IPV6 episode on OPENWRT, it would be super useful to see how to correctly impalement that at home.
Thank you for making this video and sharing it with all of us! I have been putting off learning IPv6 for a long time now. This was exactly the correct video for me to find and get motivated to get back into learning this. I am of course, subscribe with notifications turned on, and that was it up.
First off let's say brilliant video. Crazy that I'm celebrating my 25th year as a tipple CCIE and I still have never used it. That's going to change today. Wife is born in raised in Kassel in Hesse, go at least 5 times a year from the US. Such an amazing county, love it! Father-in-law was a helicopter pilot in the Bundeswehr, holds all sorts of stunt pilot records it's just insane, and the coolest man ever. He flew me under a bridge one day at 300km/h at 10 Meters from the water, about had to change my shorts. Was based at Heeresflugplatz Fritzlar, to us US folks Fritzlar Air Base, home of the Attack Helicopter Regiment 36. The stuff he showed me there was just mind blowing. Thanks again for starting me on my journey.
Thank you very very much for this explanation. You're right, you need to forget everything about V4 to understand V6. Without V6 in mind I do now understand why I got so many IPv6 Adressess on my devices. And good to know about Deutsche Telekom. I'm switching to this ISP in two weeks from Vodafone. Knowing my pfSense thats great knowledge :)
Hi Stephan, please do keep in mind that if you want to get a /56 prefix from Deutsche Telekom, then this will not work with their speedport routers (at least the one I had, don't know about the recent ones). I had to replace the Speedport with a DSL Modem ( I am using a VIGOR modem for this) in order to get full IPv6 functionality. Also lowered my ping time by 2 ms.
About local LANs, while some protocols do use link local addresses, most apps still use GUA or ULA addresses. However, they don't pass through the router. They communicate directly. You can see this by monitoring traffic with Wireshark. Also, when link local addresses are used, it is often necessary to specify which interface is to be used. GUA addresses can start with 2 or 3, but I don't know that 3 is used yet. A single /64 subnet, which is the only size allowed for a LAN, contains 18.4 billion, billion addresses. As mentioned, a /56 prefix is often provided. I have one of those, but some ISPs provide a /48, which is 256x larger. There are enough GUA addresses to give each and every person on earth over 4000 /48s! BTW, I have been running IPv6 on my own LAN for over 12 years. At first, it did take some getting used to. But now I have become the IPv6 expert in some forums. The sooner we can abandon IPv4, the better!
Hi James, I believe that I have seen your name pop up in some of the IPv6 related forums / questions a couple of times. Great to see you here ! Many thanks for the feedback ;-) You are right with everything you say - there are so many IPv6 address spaces - I realize how difficult it is for a human being to grasp exponential models ;-) Also - if I think about people trying to use IPv6 with a single /128 address - that's so disappointing because it makes it impossible for them to discover the real beauty of it ;-(
@@OneMarcFifty Quite so. A lot of people have been misled by the IPv4 address shortage and NAT, to the point they don't understand how things are supposed to work. Incidentally, customers are often provided a /128 for their WAN address. This address cannot be used for routing, as there is only one device supported by it. Even a point to point link must be at least a /127, allowing for 2 devices. A /128 is only used to identify an interface, with routing typically done with a link local address. BTW, If you really want to get into IPv6, I can recommend "IPv6 Essentials", from O'Reilly.
Many thanks for your reply and explanation James. I was thinking about making a video for an IPv6 test lab - enabling viewers to test everything in a sandbox before they go live in the real world. Some are suggesting hurricane electric as 6in4 tunnel. Any opinion on this?
@@OneMarcFifty I started out with a 6in4 tunnel, in May 2010, and it worked well. I wasn't with Hurricane Electric, but I understand they're about the largest tunnel provider. My own ISP started providing native IPv6 almost 7 years ago, but provided 6to4 and 6rd tunnels for a couple of years before that. So, including a 6in4 tunnel would be a good idea, as many are still stuck on an ISP that doesn't provide IPv6.
Thank you for these IPv6 videos. One thing I can't get my head around is my perception that there is a lack of privacy. For example, when you browse to a website, does the website see the complete IPv6 address for the client, or just the WAN portion assigned by the ISP? Does the ISP know what devices you have on your LAN? How do you handle port forwarding? I assume you would still need to open ports on your router's firewall and on your client's software firewall. All of these privacy related questions are fairly simple in IPv4, although, I do understand they are byproducts of NAT, which apparently is a bad thing (though I like it for network segregation and privacy). What am I missing here with IPv6? Why do the LAN clients even need to be aware of the WAN IP from the ISP?
Okay it's about networking. Well I have a question; is IPv6 going to be used for satellites in orbit? Would you get a recognizable address for Low Earth Orbit (LEO), Medium Earth Orbit (MEO), Geostationary (GEO), CisLunar, Lunar, Martian orbit etc.? Since we are currently on the dawn of an Interplanetary Internet, space agencies have already defined the Delay/Disruption Tolerant Networking protocols, and our space exploration is exploding right now. Will we need a new protocol if 'Global' is bigger than terrerstrial networks?
The expansion of networks to include space infrastructure like satellites, lunar operations, and interplanetary missions poses exciting challenges and opportunities for networking technologies. IPv6, with its vast address space and scalability, is a strong candidate for these applications, but the needs of space communication might push us beyond traditional IP networking in some cases. Here's a breakdown: - IPv6 in Space 1. Address Space and Hierarchy: - IPv6 can theoretically support addressing for the entire solar system and beyond. With \(2^{128}\) addresses, it can uniquely identify every satellite, rover, station, and sensor in space, from Low Earth Orbit (LEO) to Martian outposts. - Space networks can leverage hierarchical addressing schemes, grouping addresses by orbital regions (LEO, MEO, GEO) and planetary bodies. 2. Low Earth Orbit (LEO): - LEO satellite constellations, such as Starlink, already use IPv6. These satellites form a mesh network and route data efficiently to the ground. 3. Other Orbits and Deep Space: - Medium Earth Orbit (MEO) and Geostationary Orbit (GEO) satellites might adopt IPv6 for interoperability and to future-proof their networks. - CisLunar and Lunar networks could use IPv6 for communication between lunar stations, orbiters, and Earth ground stations. **EDIT 1:** - Delay/Disruption Tolerant Networking (DTN) For deep-space communication (e.g., Martian or interplanetary networks), traditional IP-based protocols face limitations: - High latency: Communication delays to Mars can exceed 20 minutes. - Disruptions: Signal interruptions due to planetary alignment or other factors. DTN protocols, defined by space agencies, address these challenges: - Bundle Protocol (BP): Functions like a "store-and-forward" system for data packets, ensuring reliable delivery even with long delays or intermittent connections. - DTN can work alongside IPv6, acting as an overlay to manage disruptions while still benefiting from IPv6's addressing capabilities. **Edit 2: ** - The Need for New Protocols 1. Interplanetary Scale: - As we expand beyond Earth, defining routing, addressing, and communication protocols for multiple planetary networks will require extensions to or replacements of current systems. - A "Solar System Internet" could involve adaptations of IPv6 or entirely new interplanetary addressing schemes. 2. New Challenges: - Time-varying connectivity (e.g., planets moving in orbit). - Energy constraints on deep-space devices. - Secure, autonomous operation in hostile environments. 3. Integration with Terrestrial Networks: - Seamless interoperability with Earth's internet might require hybrid systems, blending IP, DTN, and new protocols. - Future Outlook The dawn of the "Interplanetary Internet" will likely see IPv6 play a foundational role for Earth-centric networks and near-Earth space. For interplanetary communication, DTN protocols will dominate, potentially evolving into more robust systems that account for solar-system-scale networking. Space agencies and organizations like NASA, ESA, and private companies are already preparing for this future, ensuring our global networks can expand to the "global" scale of the solar system and beyond. Hope this helps! :D
Hi Eric, interesting topic! I would need to run experiments myself for this, haven't tested it yet - this seems to be a good primer: stevessmarthomeguide.com/multicast-dns/
Hi, that's very kind of you - thank you very much. It's only after that video and people leaving comments that I realized I had been saying it wrong for over 30 years ;-)
Hi Marc, I started to watch your IPv6 videos. Great, as mostly all your videos :) Just a comment to the IPv6 Cheat Sheet @ scopes and special adresses. The text goes down from "global" to "link local". But the table starts with localhost, then global and finishes with link-local. I would find it easier to understand if there was always the same direction. And as an inexperienced user, the representation of the ranges in normal form would also be very helpful. Maybe it would be better to integrate "scope" and "description" into the table to make it more easy to understand like this: "SCOPE" | "Range (CIDR)" | "Range" | "Purpose" "UNIQE LOCAL" | "FC00::7" | "FC00" .... "FDFF"" | Everything in our LAN (behind the internet gateway), Henning
I thought of taking that Udemy course (the 17h one, right?) to understand some of the differences from IPv4 that despite managing IP networks from the late 90s and using IPv6 for about 3 years, I wasn't able to understand, your videos were just what I was missing, these two and the OpenWRT one! Thanks a lot!
Many thanks Naveen. I really wanted to give viewers something to take away. Also I admit that I wanted to do a bit of publicity for my github repos ;-)
I just learned about the entire history of TCP and IP. From a modern corporate naming view, we'd probably name IPV4 "IP" and IPV6 "IP Pro/Advanced" as all of the old versions aren't relevant That aside, this video made ipv6 feel so simple. This may be one of the issues why it hasn't seen widespread commercial use yet, its immediate scaryness lol.
Hi, many thanks for the feedback - yes, you may see a lot of strong opinions on IPv6 in other comments here - I do agree it is more a human subject than a technological one that prevents adoption ;-) But I don't want to sound smarty-pants here because I felt exactly the same before ;-)
Great video! Could you please shortly reply to this question: Which Internet > Type of Connection > IPv6 Connectivity have you enabled in your FRITZ!Box?
Wondering if its the same course I started months ago but after the header stuff and the mass of special address spaces eventualy forgot about xD I watched alot of the paid courses on Udemy and LinkinLearning the past 3 years, and like Prof Messer here on YT, your videos and the way you present dense highly technical content in an understandable maner, for free, is nothing short of amazing and I thank you for doing so! Some say you best learn IPv6 by turning off IPv4 on your network and start from there ;)
Super gemacht! Wünschte mir mehr Infos zu Prefix Delegation, DNS bei Ipv6 (warum gibt es den bei einigen Routern zum Eintragen, bei anderen nicht), Gateway (ist das der nächste Hop oder der Router mit dem Prefix?), IGMP Proxy.
Kind of. if you type "ip route" on a device, then you will see IPv4 routes with global scopes (e.g. the default route) and "scope link" (i.e. subnets that can be reached via the interface directly). The latter ones would not need to be routed.
Thank you much for the easy simplified way of delivering that content I do recommend you to teach on udemy your courses will be very good add to the tech community
Thanks Pavel. Yes - as there is so much info floating around everywhere - that was the reason I decided to take that course. I never had to use IPv6 and could safely ignore it. But that left the "there is space to be discovered" voice in my head ;-)
Hi Nick, many thanks for the friendly comment. Yes - when I launched my "IPv6 only" testlab I realized how bad the coverage is really. ISPs, content providers, CDNs - there's still a lot of room of improvement left ;-)
We will have a deeper look into a couple of things in a follow up video. I just need to think over if I‘ll do that as a generic video or rather related to OpenWrt
Does the notation ::/x, where x denotes number of significant bits mean those bits are counted from the beginning of the address, or from the end of the scope prefix? In other words, is the prefix included in the significant bits or is it separate from them?
Wow -someone is opening the box of pandora, often thinking about it, never dared to. Okay watched the video, very good start, what itnerests me the most: what about security? Without NAT I feel a bit naked ;-)
Yeah - I felt the same honestly- but let’s not forget that NAT is just a workaround ;-) Firewall will do its job - with or without NAT. Privacy concerns could be addressed by changing the ipv6 frequently- as there are so many possible addresses it could in fact even be an improvement!
@@OneMarcFifty thanks for the awesome video, what I don't understand is if with ipv6 it will still be possible to hide your internal hosts from the outside world without them losing internet connectivity. Maybe i get it wrong but It seems this protocol implies no NAT so every device who needs internet connectivity must have a public ipv6 address. What if I don't want my crappy chinese IOT device to have a public ip address in first place ?
It's fairly simple once you play with it. It's mostly just automation for things you can already do in openwrt because normal router usage does not involve changing networks you're connected to.
Oh yeah, that would be very nice! There is a heise+ article about openwrt + travelmate in German (search for "Automatische WLAN-Verwaltung für Reiserouter mit OpenWrt"). Maybe it can serve as inspiration.
Yes please. I would like a guide that explain how to set up correctly IPv6 on OpenWRT at my home where i have 3 Devices with OpenWRT (the last 2 are dumb switches)
Hi Alex, i’ll give this a long thought but presumably this is not going to happen soon. There are a bunch of videos that I need to make before. Even though a captive portal is an interesting matter!
Hi, those are just examples how an IPv6 address could be generated. In a nutshell, a factor of entropy (or any pseudo-random) value is needed in order to avoid collision or make it unlikely. a Unique Identifier of any kind (UID) or time stamp (i.e. any counter that changes over time) could be such a factor.
Finally, a good introduction to IPv6. Systematically walking through the development process makes it all come together very nicely at the end. looking forward for more brilliant videos on IPv6 from you!
Hi Lionel, many thanks for your feedback. There will be a follow up.
Even seasoned network engineers such as myself are confused by IPv6 because, as you noted, it requires us to "forget" everything we know about IPv4 and start from scratch. This is not easy to do but your video has helped me make progress on coming to terms with the IPv6 space. Thank you for providing this excellent resource!
Yeah - In college for me (1992-1993) we learned IPv4. The TCP vs UDP protocols are familiar, as we learned in Operating Systems. The organization of the IPv6 addresses is completely new. I'm playing with OpenWRT now, and at least I know why my PCs Link Local address starts with fe80:: Seems like ICMP is still used for ping.
Thank you. For years I've only ever seen "Enable it vs. Disable it" with all kinds of myths. Nice to finally have an explanation!
The best set of IPv6 videos on youtube. Thanks for the clear and concise explainer. Most stop at a simple explanation of "what is IPv6". You actually explain how to use it. I was finally able to set up IPv6 on my network.
This is the most clean explanation of IPv6 I’ve ever seen. You are killing it Marc, thanks!
Many thanks Remy!
Excellent introduction to IPv6. I really hope that you will follow this up with many more topics like dual stack, firewalling and others (like VLANs) that an average person needs to understand when creating a small office or home IPv6 network. We are more than happy for you to do this as part of the next OpenWRT episode.
Hi Manoj, the topics that you mention are definitely the right ones - I'd add to these: Unicast, Anycast, Multicast (Router solicitation, Router Advertisement, Duplicate Address detection), NDP ;-) Thanks for the feedback !!!
As a network instructor for many years (decades even!) I totally endorse your approach to describing IPv6 - do NOT try to compare its features with IPv4. It is a new protocol. Loved the address scope explanation. One thing though - it is still the same old UDP and TCP - regardless of the Network layer protocol. Looking forward to your explanation of anycast - that often causes students difficulty (mostly because they try to compare it to broadcast.)
Many thanks Aubrey! W/r to anycast, my preferred analogy is calling the emergency number- you always call the same number but you would land in a different call center depending on the network you place the call from and the time of the day ;-)
He's right though, there's is no TCPv6 or UDPv6. What you're referencing is the field that occurs in the IPv4 and IPv6 header that indicates *what type* of layer 4 header *follows* after the IPv4/v6 header. TCP and UDP are the same for either one.
Absolutely! I don’t contradict ;-) The only reason I emphasize on udpv6 and tcpv6 is to build context for the importance of icmp for the ipv6 protocol ;-)
Personally I feel like the addressing part is not that complicated and not that different from IPv4. IP address of a certain number of bits with a subnet mask of a certain number of bits (cidr) is all the same just longer addresses.
The explanation of scopes is good though and important but also this is not too dissimilar to rc1918 addresses.
The part I think that a lot of people get confused about is routing, how it happens and why as well as different configuration setups besides SLAAC, like DHCPv6, RA/router advertisements, prefix delegation and interface tracking.
A lot of people are used to thinking in terms of NAT which is why I don't disagree with this approach but even without comparison or even mentioning it might be important to stress especially for home users who are used to having to forward ports that this isn't a thing. No forwarding ports, instead you block ports with a firewall on the router or local machine. I'm not sure a lot of people fully understand with IPv6 and a typical home router that their pc is now directly accessible on the public internet instead of hiding behind a NAT (which isn't a firewall - it just doesn't know where to send incoming traffic unless you tell it)..
While I understand this is an introduction, I had to understand all of that when setting up my own home network even.
Though I still don't understand why I can't seem to track or delegate to my 2nd WAN interface, only get one /56 over dhcp and I can't ask for several smaller prefixes or seem to delegate a /64 or something to secondary wan..works fine for lan interfaces though.. not a huge deal but my ocd doesn't like seeing an adapter with unassigned address.
@@forbiddenera
> with IPv6 and a typical home router that their pc is now directly accessible on the public internet
that obviously depends on the router, I'm not sure what you mean by "a typical home router" but all the ones I've encountered do not allow incoming traffic by default, as should be true for any network device that isn't garbage.
My boss tasked me to “git gud” on ipv6. And I’m so happy this was the first video I chose to watch.
This is an absolutely excellent video and in my opinion it's a must-watch for anyone starting out on IPv6. I can honestly say that if I'd been able to watch this 15 minute introduction when I first looked at IPv6 it would have saved me many many many hours of going back and forth through text books trying to get my head around the concepts - and your approach to explaining it is brilliant, and I totally get what my problem has been until now in learning IPv6 - I was always trying to find an IPv4 analogy! Your video has got me over that hurdle, explained what the fundamentals are and what I should always keep in mind. It's made understanding and mastering the conceptual basis of v6 so much easier. Keep up the good work and I say that as one very Patreon patron!👌👍😄
Hi Ray, first off - thank you very much for being a patron!!! I am so glad that so many people seem to like the video (at least from what I read in the comments) - it looks like disconnecting from IPv4 is really the key for everyone here. Many thanks for the friendly feedback!
Thank you Marc. Your video helped me to turn the fear, to something that looked very strange, into a will to delve further into it to learn something new. With your guidance, I am ready to take that journey and learn along from your future videos about this topic.
Hi, that's great feedback, many thanks. I experienced exactly the same. It was a great unknown until I took all my courage and stepped into that course. And after all now I realize that it is fun. I'll definitely do follow ups.
@@OneMarcFifty thanks
This is the best free software Ive seen. Respect.
Thank you.
The key realisation for me was around the fact that hosts will almost always have multiple IPv6 addresses. Of course we could always have multiple addresses in IPv4 as well, but it was typically the exception rather than the rule. In IPv6, everything has multiple addresses.
I also have a /56 prefix delegation from my ISP, and I've enjoyed the challenge of setting this up on my pfSense based firewall / router. Compared to the 1 I(public) Pv4 address , the numbers of IPv6 addresses I get is just staggering!
Hi Aaron - I went through exactly the same experience here. When I saw the many IPv6 addresses on my laptop the first time it totally freaked me out. And - as you say - the size of the address space is just overwhelming ;-)
"Of course we could always have multiple addresses in IPv4 as well, but it was typically the exception rather than the rule."
Not entirely true. Your host always has 127.0.0.1 - though that's a bit cheeky.
What's less cheeky is if a NIC is configured with address 192.0.2.1/24, it can receive/listen for messages destined to 192.0.2.255 (local broadcast). While not particularly obvious, your host has multiple IP addresses. It just doesn't really send with the broadcast address as source.
Your IPv4 host also uses another address - 0.0.0.0. This one comes into play specifically for DHCP. If you look at the source address of a DHCP discover packet, you'll see this as the source address.
In fact there's nothing stopping you from say, booting up a host on a network without DHCP (or disabling the DHCP client), grabbing an IPv4 link-local address (APIPA), configuring that statically on the interface, and then re-enabling DHCP for an additional address.
@@Jamesaepp "Your host always has 127.0.0.1"
It's actually more than you think ^^. Even though IPv4 has such a limited address space, they dedicated a whole class A net to the local host, not just a single address. 127.0.0.1 is just the most commonly used and is usually mapped locally to "localhost". However 127.45.12.42 is also a local loopback address. The entire 127 net is local loopback. So 1/256th of the whole v4 address space is wasted. In IPv6 they decided that a single address is enough. If you need more, you can always assign more, but it's not implicit.
Note that (0.0.0.0) is not really an address, it's merely a wildcard for the whole network to indicate no particular address. As you may know, when binding a socket, you can either bind it to a local address that the socket should listen to, or bind it to (0.0.0.0). That means the socket would be bound to all local addresses. In other words if a packet arrives at your NIC, it doesn't really care what the destination address is. Since it arrived at your NIC, it's meant for you.
A lot servers by default bind to (0.0.0.0) so they accept any packets, no matter to which IP they were directed to. However explicit binding is needed if you want to run several servers on the same machine on the same port. You just need to bind each it to different local addresses. Locally you can bind servers to different local host addresses and it would work fine, locally. So you can run a server on 127.0.0.1:5555 and one on 127.0.0.2:5555. Of course you can only connect to those two servers locally, so this is just an example. Though If you bind a server to (0.0.0.0), you can't bind another socket to the same port as it 0.0.0.0 binds to all addresses. A single end point (IP + protocol + port) can only be used / bound once.
Every single video you make…. They help me a lot with my network understanding. Thank you very much for all the effort you take doing them!
Hi Ben, I am honestly and fundamentally happy each time someone tells me that my videos could help them to achieve something. Thanks a lot for your friendly feedback.
Awesome video. I'm impressed with your teaching skills, making a hard topic easy to understand. It requires a lot of preparation. Many thanks.
Hi David, thank you very much- yes, it does require preparation.
03:40 and 3:58 Please note you always HAVE TO shorten the longest run of consecutive 16bit 0 fields, therefore FF:0:0:0:1::1 would be wrong too.
When the length of the consecutive 16-bit 0 fields are equal, the first sequence of zero bits MUST be shortened.
Hi Adrian, I was not aware of this. Is there any official documentation on this ?
@@OneMarcFifty Hi Marc, yes there is. Feel free to have a look at RFC 5952 section 4.2
Thank you - just checked it. It is explicit and states MUST. It even goes further and says that a..f MUST be written in lowercase!
This guy is a genius MashAllah what an explanation and how he describe step by step that's wonderful. Amazing, Bravo!! I want a teacher like you, please make more videos on IPV6 Thanks for the good knowledge and explaination.
Going to learn IPV6 for future reference. For now, I have two lan adaptors on both my desktop and laptop. On each machine, I have one adaptor handling IPV4, and the other handling IPV6. The adaptors handling the IPV6 are ALWAYs moving more data than the IPV4. Almost twice as much sometimes. Anyone hating on IPV6 better get with it. Its more prominent than you think. I have Starlink as an ISP.
Well explained from scratch, thank you Marc. Good approach in asking us to forget what we know about IPv4 and in the end, after all is as clear as muddy water, I would say IPv6 is still quite similar to IPv4
Hi Thomas - yes it is after all. Just people (including myself of course) tend to be "mentally stuck" in NAT. WE tend to forget that NAT is a workaround and that it is not Firewall ;-)
amazing video, loved how you kept it simple and made sure it's not redundant. SO THANKFUL FOR THIS VIDEO, it has been super helpful in terms of wrapping up how the big picture looks like and also how the little details work together.
Your introduction was spot on. It's still frustrating to me and shutdown ipv6 as much as i can in my home because of it. My modem has a IPv6 address but I have IPv4 on my WAN port. I don't think I need v6 on my LAN. It would just be a learning tool if anything.
Hi J B, yes - I totally agree - the fun is limited if you only get it LAN-side ;-(
Another great video from you. I'm really looking forward to upcomming videos about IPv6.
Many thanks Volker!
It definitely was the best explanation of the protocol I have seen.
Many thanks.
Nice job. Thank you for putting this together and sharing. IPv6 is much clearer for me.
Hi Robert. Awesome - I am glad it could help.
thank you for this great intro to IPv6, it's very helpful and you explain it very well in simple terms.
Finally a comprehensive explanation...
hope you had underlined/marked the digits when talking about subnetting for easy visualization...
waiting for your video explaining why broadcast is not anymore... and how anycast mechanism works along the route in the intermediate nodes...
;-)
Hey, thanks so much for your feedback. True, I should have visualized subnetting more. The follow up episode is available on my channel page btw ;-)
ABSOLUTELY the best one of these I have ever watched...and there have been 100s. I love how you break it all down, and I too struggle with differentiating IPv4 and IPv6. I am still struggling with IPv6 (in my home with pfSense as router and a Windows 2019 server ADDS/DNS/DHCP setup). I cannot get that server to hand out addresses (well I can - but they cannot get to the Internet over IPv6 only (every test site I visit shows IPv6 failures). Looking forward to your other videos, and maybe I can figure this out. 👍
Amazing way to simply everything! Can’t wait for the next video!
Hi Alex, thank you!
I'm a beginner so everything you say is strange but the cheat sheet helped me get curious and you've helped me grasp this subject. Amazing video !
Thank you! I’m very curious if one would use 2 VLANs, one setup as v6 only and another v4 only for your local devices if the speeds etc would be same? Also wandering if your local network is v6 only, if your ISP router could act as a ‘v4 gateway’ to the internet.
Wow - haven’t thought about this - I would have to take a closer look
Tremendous! Absolutely fantastic presentation. You're one heck of a great presenter!
Thank you very much ;-)
Thank you Marc for this! Very helpful! I look forward to your IPV6 episode on OPENWRT, it would be super useful to see how to correctly impalement that at home.
Thank you very much! I'll need to plan this episode - i've got some ideas but I'll probably set up a whole IPv6 test lab for that. I'll be back ;-)
Excellent and entertaining explanations. Thanks!
Many thanks Jörg - glad you liked it ;-)
Thank you for making this video and sharing it with all of us! I have been putting off learning IPv6 for a long time now. This was exactly the correct video for me to find and get motivated to get back into learning this. I am of course, subscribe with notifications turned on, and that was it up.
This is a great intro to IPv6. Thank you!
Many thanks Stephan.
Thank you for a great explanation and for making available such a clear and well paced video.
Finally a IPV6 fundamentals that kept my attention 😄👍💯
First off let's say brilliant video. Crazy that I'm celebrating my 25th year as a tipple CCIE and I still have never used it. That's going to change today.
Wife is born in raised in Kassel in Hesse, go at least 5 times a year from the US. Such an amazing county, love it! Father-in-law was a helicopter pilot in the Bundeswehr, holds all sorts of stunt pilot records it's just insane, and the coolest man ever. He flew me under a bridge one day at 300km/h at 10 Meters from the water, about had to change my shorts. Was based at Heeresflugplatz Fritzlar, to us US folks Fritzlar Air Base, home of the Attack Helicopter Regiment 36. The stuff he showed me there was just mind blowing. Thanks again for starting me on my journey.
Flying under a bridge is to IPv6 what apples are to oranges. Not even oranges. More like dust bin cover screws. Duuuude!
Excellent. Great way to introduce some new concept. Just loved it. Thank you so much for the video
Powerful explanation! Thank you! Much clearer now
Many thanks Roy.
Hi Marc, Great explanation. You are righ, it helps to forget IPV4 and start over :) Thank you.
Hi Bruce, many thanks for the feedback. Glad to hear that I am not the only person making that experience ;-)
This is great explanation, took out IPv4 concept is really helping to understand IPv6 concept
Many thanks for the feedback, benediktus
This was really helpful. Building it up was a great way to help me understand why it is the way it is!
I haven't watched the whole video yet but I love the idea behind your approach.
Simply the BEST IPV6 video so far !
Thank you so much!
+1 subscriber here !
Hi Igor - first and foremost - many thanks for subscribing. Glad you liked the video.
Great introduction for the IPv6 world. Thanks for sharing.
Thanks Mark, fantastic explanation.🖖
Thank you very much - I am glad you liked it.
Thank you very very much for this explanation. You're right, you need to forget everything about V4 to understand V6. Without V6 in mind I do now understand why I got so many IPv6 Adressess on my devices.
And good to know about Deutsche Telekom. I'm switching to this ISP in two weeks from Vodafone. Knowing my pfSense thats great knowledge :)
Hi Stephan, please do keep in mind that if you want to get a /56 prefix from Deutsche Telekom, then this will not work with their speedport routers (at least the one I had, don't know about the recent ones). I had to replace the Speedport with a DSL Modem ( I am using a VIGOR modem for this) in order to get full IPv6 functionality. Also lowered my ping time by 2 ms.
@@OneMarcFifty hey Marc,
Thanks for the hint. No worries, i bought a zyxel Modem to avoid the speedports 😂
Amazing content as usual, I was waiting for this one! :)
Hi Marco, many thanks. Glad you liked it.
About local LANs, while some protocols do use link local addresses, most apps still use GUA or ULA addresses. However, they don't pass through the router. They communicate directly. You can see this by monitoring traffic with Wireshark. Also, when link local addresses are used, it is often necessary to specify which interface is to be used.
GUA addresses can start with 2 or 3, but I don't know that 3 is used yet.
A single /64 subnet, which is the only size allowed for a LAN, contains 18.4 billion, billion addresses.
As mentioned, a /56 prefix is often provided. I have one of those, but some ISPs provide a /48, which is 256x larger. There are enough GUA addresses to give each and every person on earth over 4000 /48s!
BTW, I have been running IPv6 on my own LAN for over 12 years. At first, it did take some getting used to. But now I have become the IPv6 expert in some forums. The sooner we can abandon IPv4, the better!
Hi James, I believe that I have seen your name pop up in some of the IPv6 related forums / questions a couple of times. Great to see you here ! Many thanks for the feedback ;-) You are right with everything you say - there are so many IPv6 address spaces - I realize how difficult it is for a human being to grasp exponential models ;-) Also - if I think about people trying to use IPv6 with a single /128 address - that's so disappointing because it makes it impossible for them to discover the real beauty of it ;-(
@@OneMarcFifty Quite so. A lot of people have been misled by the IPv4 address shortage and NAT, to the point they don't understand how things are supposed to work. Incidentally, customers are often provided a /128 for their WAN address. This address cannot be used for routing, as there is only one device supported by it. Even a point to point link must be at least a /127, allowing for 2 devices. A /128 is only used to identify an interface, with routing typically done with a link local address.
BTW, If you really want to get into IPv6, I can recommend "IPv6 Essentials", from O'Reilly.
Many thanks for your reply and explanation James. I was thinking about making a video for an IPv6 test lab - enabling viewers to test everything in a sandbox before they go live in the real world. Some are suggesting hurricane electric as 6in4 tunnel. Any opinion on this?
@@OneMarcFifty I started out with a 6in4 tunnel, in May 2010, and it worked well. I wasn't with Hurricane Electric, but I understand they're about the largest tunnel provider. My own ISP started providing native IPv6 almost 7 years ago, but provided 6to4 and 6rd tunnels for a couple of years before that. So, including a 6in4 tunnel would be a good idea, as many are still stuck on an ISP that doesn't provide IPv6.
Thank you for these IPv6 videos. One thing I can't get my head around is my perception that there is a lack of privacy. For example, when you browse to a website, does the website see the complete IPv6 address for the client, or just the WAN portion assigned by the ISP? Does the ISP know what devices you have on your LAN? How do you handle port forwarding? I assume you would still need to open ports on your router's firewall and on your client's software firewall.
All of these privacy related questions are fairly simple in IPv4, although, I do understand they are byproducts of NAT, which apparently is a bad thing (though I like it for network segregation and privacy). What am I missing here with IPv6? Why do the LAN clients even need to be aware of the WAN IP from the ISP?
Okay it's about networking. Well I have a question; is IPv6 going to be used for satellites in orbit? Would you get a recognizable address for Low Earth Orbit (LEO), Medium Earth Orbit (MEO), Geostationary (GEO), CisLunar, Lunar, Martian orbit etc.? Since we are currently on the dawn of an Interplanetary Internet, space agencies have already defined the Delay/Disruption Tolerant Networking protocols, and our space exploration is exploding right now. Will we need a new protocol if 'Global' is bigger than terrerstrial networks?
Hi Jay, I have never asked myself that question to be honest. The address space of IPv6 would however be presumably large enough;-)
The expansion of networks to include space infrastructure like satellites, lunar operations, and interplanetary missions poses exciting challenges and opportunities for networking technologies. IPv6, with its vast address space and scalability, is a strong candidate for these applications, but the needs of space communication might push us beyond traditional IP networking in some cases. Here's a breakdown:
- IPv6 in Space
1. Address Space and Hierarchy:
- IPv6 can theoretically support addressing for the entire solar system and beyond. With \(2^{128}\) addresses, it can uniquely identify every satellite, rover, station, and sensor in space, from Low Earth Orbit (LEO) to Martian outposts.
- Space networks can leverage hierarchical addressing schemes, grouping addresses by orbital regions (LEO, MEO, GEO) and planetary bodies.
2. Low Earth Orbit (LEO):
- LEO satellite constellations, such as Starlink, already use IPv6. These satellites form a mesh network and route data efficiently to the ground.
3. Other Orbits and Deep Space:
- Medium Earth Orbit (MEO) and Geostationary Orbit (GEO) satellites might adopt IPv6 for interoperability and to future-proof their networks.
- CisLunar and Lunar networks could use IPv6 for communication between lunar stations, orbiters, and Earth ground stations.
**EDIT 1:**
- Delay/Disruption Tolerant Networking (DTN)
For deep-space communication (e.g., Martian or interplanetary networks), traditional IP-based protocols face limitations:
- High latency: Communication delays to Mars can exceed 20 minutes.
- Disruptions: Signal interruptions due to planetary alignment or other factors.
DTN protocols, defined by space agencies, address these challenges:
- Bundle Protocol (BP): Functions like a "store-and-forward" system for data packets, ensuring reliable delivery even with long delays or intermittent connections.
- DTN can work alongside IPv6, acting as an overlay to manage disruptions while still benefiting from IPv6's addressing capabilities.
**Edit 2: **
- The Need for New Protocols
1. Interplanetary Scale:
- As we expand beyond Earth, defining routing, addressing, and communication protocols for multiple planetary networks will require extensions to or replacements of current systems.
- A "Solar System Internet" could involve adaptations of IPv6 or entirely new interplanetary addressing schemes.
2. New Challenges:
- Time-varying connectivity (e.g., planets moving in orbit).
- Energy constraints on deep-space devices.
- Secure, autonomous operation in hostile environments.
3. Integration with Terrestrial Networks:
- Seamless interoperability with Earth's internet might require hybrid systems, blending IP, DTN, and new protocols.
- Future Outlook
The dawn of the "Interplanetary Internet" will likely see IPv6 play a foundational role for Earth-centric networks and near-Earth space. For interplanetary communication, DTN protocols will dominate, potentially evolving into more robust systems that account for solar-system-scale networking.
Space agencies and organizations like NASA, ESA, and private companies are already preparing for this future, ensuring our global networks can expand to the "global" scale of the solar system and beyond.
Hope this helps! :D
@There-was-nothing-we-could-do F U ChatGPT
This was an excellent introduction, same with your follow up video. 👍
This was very helpful, thank you. I might even be able to start using the IPV6 settings on my router.
Hi Mark, that’s great. There will be episodes on how to use it with routers. At least for OpenWrt and maybe for OPNSense/pfSense
Great explanation! I'd love to see a primer on .local TLDs in the IPv6 world
Hi Eric, interesting topic! I would need to run experiments myself for this, haven't tested it yet - this seems to be a good primer: stevessmarthomeguide.com/multicast-dns/
Learned a lot from your videos, loving the way you say host 😂
Hi, that's very kind of you - thank you very much. It's only after that video and people leaving comments that I realized I had been saying it wrong for over 30 years ;-)
Excellent video. Extremely helpful.
Many thanks Torin !
I made it finally, I forgot IPv4!!
Great content, still having some doubts though. See you on Discord ;)
Hi Euxhenio - great to hear ;-) But don't forget to remember it again in the end ;-)
Another video with marc, making easy the hard things.
Hi luis, thank you ;-)
Hi Marc,
I started to watch your IPv6 videos. Great, as mostly all your videos :)
Just a comment to the IPv6 Cheat Sheet @ scopes and special adresses.
The text goes down from "global" to "link local". But the table starts with localhost, then global and finishes with link-local. I would find it easier to understand if there was always the same direction. And as an inexperienced user, the representation of the ranges in normal form would also be very helpful.
Maybe it would be better to integrate "scope" and "description" into the table to make it more easy to understand
like this:
"SCOPE" | "Range (CIDR)" | "Range" | "Purpose"
"UNIQE LOCAL" | "FC00::7" | "FC00" .... "FDFF"" | Everything in our LAN (behind the internet gateway),
Henning
maybe adding the abbreviations like ULA, SLAAC to the table is helpful to ...
Hi Henning, maybe this has already been fixed on the Github - github.com/onemarcfifty/cheat-sheets/blob/main/networking/ipv6.md
that was very helpful Marc. The biggest single piece of advice that really helped was to forget IPv4. That really made a big difference. 😀👍
Hi, thanks for the feed back ;-) Yes, that was big (yet simple) discovery for me as well ;-)
It seems that the world will never move on from ipv4
Please. Never let go!
I thought of taking that Udemy course (the 17h one, right?) to understand some of the differences from IPv4 that despite managing IP networks from the late 90s and using IPv6 for about 3 years, I wasn't able to understand, your videos were just what I was missing, these two and the OpenWRT one!
Thanks a lot!
Hi Didi, glad you could use it! I can't remember where the course was listed - but it was long. Really long ;-)
Great video! Kudos for the cheat sheet style approach ✨.
Many thanks Naveen. I really wanted to give viewers something to take away. Also I admit that I wanted to do a bit of publicity for my github repos ;-)
Needed just a few extra words and seconds to cover the '/N' part for number of bits (counted from which end, etc.).
Rather good.
Many thanks Philip.
That was excellent! Thank you very much for this walkthrough.
Thank you - glad you liked it
I just learned about the entire history of TCP and IP. From a modern corporate naming view, we'd probably name IPV4 "IP" and IPV6 "IP Pro/Advanced" as all of the old versions aren't relevant
That aside, this video made ipv6 feel so simple. This may be one of the issues why it hasn't seen widespread commercial use yet, its immediate scaryness lol.
Hi, many thanks for the feedback - yes, you may see a lot of strong opinions on IPv6 in other comments here - I do agree it is more a human subject than a technological one that prevents adoption ;-) But I don't want to sound smarty-pants here because I felt exactly the same before ;-)
I am seeing different articles on the fc00::/7 and it is listed as fc00:/8. So which is correct regarding Unique Local Addresses?
Awesome video. I've finally started to understand ipv6 🎉
Mark this is simply awesome! Thank you very much!! Looking forward for the OpenWrt IPv6 implementation video :D
Hi Tomás - thank you so much for your feedback. Yes - I am already planning follow ups - just need to make up my mind which one to do first ;-)
Great video! Could you please shortly reply to this question: Which Internet > Type of Connection > IPv6 Connectivity have you enabled in your FRITZ!Box?
This is actually a very good explaination of ipv6 thanks !
Wondering if its the same course I started months ago but after the header stuff and the mass of special address spaces eventualy forgot about xD
I watched alot of the paid courses on Udemy and LinkinLearning the past 3 years, and like Prof Messer here on YT, your videos and the way you present dense highly technical content in an understandable maner, for free, is nothing short of amazing and I thank you for doing so!
Some say you best learn IPv6 by turning off IPv4 on your network and start from there ;)
Many thanks for the feedback :-)
Ah... Great video. I knew I would have to learn this stuff one day. So far my ISP has not implemented IPv6 yet... but I live in Wyoming.
Hi Matthew - I think we are all the same ;-) We know we have to do this one day ;-)
Super gemacht! Wünschte mir mehr Infos zu Prefix Delegation, DNS bei Ipv6 (warum gibt es den bei einigen Routern zum Eintragen, bei anderen nicht), Gateway (ist das der nächste Hop oder der Router mit dem Prefix?), IGMP Proxy.
Simply brilliant ! Thank you !
Thanks for sharing your knowledge!
Thank you - you’re welcome.
At 06:59 do you perhaps mean broadcast domain instead of collision domain?
Thank you so much bro. Sending virtual hugs. Worked like a charm ;-)
Hi, thank you very much
10:57 Is it also true for IPv4 that link-local will use switch and routing ?
Kind of. if you type "ip route" on a device, then you will see IPv4 routes with global scopes (e.g. the default route) and "scope link" (i.e. subnets that can be reached via the interface directly). The latter ones would not need to be routed.
I like the look of IPv6 addresses and prefer them over IPv4 actually!
don't judge an address by its look would be the lesson to me then ;-)
Great video mate, really well done.
Thank you much for the easy simplified way of delivering that content
I do recommend you to teach on udemy your courses will be very good add to the tech community
How to make fun from crazy IPv6 mess :-) Good job.
Thanks Pavel. Yes - as there is so much info floating around everywhere - that was the reason I decided to take that course. I never had to use IPv6 and could safely ignore it. But that left the "there is space to be discovered" voice in my head ;-)
Excellent clarity of thought as always. Still waiting for Virgin Media/UK to implement IPv6...
Hi Nick, many thanks for the friendly comment. Yes - when I launched my "IPv6 only" testlab I realized how bad the coverage is really. ISPs, content providers, CDNs - there's still a lot of room of improvement left ;-)
Fantastic! I really enjoyed the video. Would you consider doing a SLAAC vs dhcpv6 video as well?
We will have a deeper look into a couple of things in a follow up video. I just need to think over if I‘ll do that as a generic video or rather related to OpenWrt
You deserve more than like, thank you
Thank you thank you thank you!!! Such a clear and well explained video!
very good👍
I was wondering how to play with ipv6 on my network and this helps a lot.
nice .just what i was waiting for.
Awesome, many thanks Richard - glad it helped ;-)
thank you so much. keep making videos you explain so well
I love IPV6, which I think is just better.
Hi Damalia, I have learnt to love it as well ;-)
Awesome explenation, helped me a lot
Thank you Arne, glad you could use it!
Does the notation ::/x, where x denotes number of significant bits mean those bits are counted from the beginning of the address, or from the end of the scope prefix?
In other words, is the prefix included in the significant bits or is it separate from them?
They are counted from the beginning, i.e. the prefix is included. A single address could hence have /128
Wow -someone is opening the box of pandora, often thinking about it, never dared to. Okay watched the video, very good start, what itnerests me the most: what about security? Without NAT I feel a bit naked ;-)
Yeah - I felt the same honestly- but let’s not forget that NAT is just a workaround ;-) Firewall will do its job - with or without NAT. Privacy concerns could be addressed by changing the ipv6 frequently- as there are so many possible addresses it could in fact even be an improvement!
@@OneMarcFifty thanks for the awesome video, what I don't understand is if with ipv6 it will still be possible to hide your internal hosts from the outside world without them losing internet connectivity. Maybe i get it wrong but It seems this protocol implies no NAT so every device who needs internet connectivity must have a public ipv6 address. What if I don't want my crappy chinese IOT device to have a public ip address in first place ?
Can you also do a video on the Travel mate plugin for OpenWrt ? ( Thanks for the video , simple and great explainer )
Oh - I didn’t know travelmate - looks really interesting - I‘ll think it over ;-) thanks for the hint!
It's fairly simple once you play with it. It's mostly just automation for things you can already do in openwrt because normal router usage does not involve changing networks you're connected to.
Oh yeah, that would be very nice! There is a heise+ article about openwrt + travelmate in German (search for "Automatische WLAN-Verwaltung für Reiserouter mit OpenWrt"). Maybe it can serve as inspiration.
Simple method, many thanks for sharing
Hi Sandra, many thanks for watching.
Yes please. I would like a guide that explain how to set up correctly IPv6 on OpenWRT at my home where i have 3 Devices with OpenWRT (the last 2 are dumb switches)
Hi, many thanks for the feedback- I‘ve taken note ;-)
Marc, great video thank you so much for the break down of IPv6. Would you ever consider making a video on OpenNDS?
Hi Alex, i’ll give this a long thought but presumably this is not going to happen soon. There are a bunch of videos that I need to make before. Even though a captive portal is an interesting matter!
Thank you!! Very informative and fun to watch :)
9:34 What is UID and Timestamp and other things that come under "similar"
Hi, those are just examples how an IPv6 address could be generated. In a nutshell, a factor of entropy (or any pseudo-random) value is needed in order to avoid collision or make it unlikely. a Unique Identifier of any kind (UID) or time stamp (i.e. any counter that changes over time) could be such a factor.