Master IP Subnetting (and cloud considerations)
Ғылым және технология
Per user requests I have created a deep dive around IP subnetting and what are the cloud specific considerations!
Whiteboard at github.com/johnthebrit/Random...
00:00 Introduction
01:38 Delivering letters in England
06:30 IPv4 addresses and subnet mask
10:22 IPv4 delivery
16:25 SDN delivery differences
19:00 Binary overview
23:40 Binary masking
28:25 Usable IP addresses
31:40 CIDR and smaller subnets
34:53 Smaller subnet use
37:37 Why use subnets in Azure/cloud
39:50 How many bits are needed for addresses
41:50 Using subnet calculator
45:12 Detail around a /26 network
50:41 /26 usable IP detail
51:55 Example vnets in Azure
55:26 Summary and close
Пікірлер: 61
You've got a really great way of explaining things John! I've actually been listening to your videos while I do my 5am walk because I can picture everything you're saying... Anything I don't get I use the lap-marker on my watch to bookmark where to go back to. Thank you!
@NTFAQGuy
3 жыл бұрын
Great. Also remember I have bookmarks on the video.
So glad I found this video. I have always struggled understanding CIDR. You explained it so easily. Thank you very much!
@NTFAQGuy
3 жыл бұрын
Glad it was helpful!
Mate, best video ever! Refreshed my knowledge of networking as I haven't had to touch to concept for ages and helped me understand the CIDR stuff for Azure. Thank you so much.
Really great !!! You simplify any hard topics. I am not from network background, your teaching helped me to understand how to plan for network and subnet.
@NTFAQGuy
3 жыл бұрын
Awesome, thanks
Your videos are extremely helpful. Thank you for all the effort you put into it!
@NTFAQGuy
2 жыл бұрын
Thank you!
Great explanation as always. A little trick that I learned in IPv4: try to ping 127.1 . Yes, 127.1, not 127.0.0.1. Should not work, right? Instead, it works! Why? Because the 3 octects are converted in a single number, so .1 becomes .0.0.1. You can also try to ping 127.12345 and it will resolve to 127.0.48.57. Little fun! :)
Thank you so much for this! Been struggling with subnetting and you explain things well
@NTFAQGuy
3 жыл бұрын
Glad it was helpful!
Amazing content, thanks much for sharing the vital information, related to IP and subnet mask.
@NTFAQGuy
3 жыл бұрын
Glad it was helpful!
A very important topic. Thank you. (I have finished your PS Masterclass by the way. What a ride it was. Thanks. )
@NTFAQGuy
3 жыл бұрын
Glad you enjoyed it!
You are awesome, John! It helped me pickup subnet masking quickly. Thanks for mentioning about Software Defined Networking too. I did not know about it. Thanks a lot.
@NTFAQGuy
3 жыл бұрын
Glad to help!
@mystiqkc
3 жыл бұрын
@@NTFAQGuy Thanks for the great tutorials. You inspire me to learn more and also be fit and healthy at the same time. How can I buy you a cup of coffee? :-) I think KZread did start a way to accept contributions.
@NTFAQGuy
3 жыл бұрын
@@mystiqkc that’s very kind but not required. I run this channel to give back to the community not to make any money. That is why I have no advertising on the site. Please enjoy the content. Take care
@mystiqkc
3 жыл бұрын
@@NTFAQGuy Got it. Thanks!
Thank you! best tutorial on subnetting that I've watched, look forward to you next video and shirt :)
@NTFAQGuy
3 жыл бұрын
Awesome, thank you!
Thank you John for the excellent video!
From 0.0.0.0 to Hero! Nice, once again - that is brilliant :)
2023 and still the best :-D ...wanted to do Designing and Implement Azure Networking Study SUPER Guide! And I was like ok let me refresh Networking Basics and this was totally worth it and a game changer basics :-) ...thanks a lot.
Completed! Beautifully explained. I wanted to see more of the demo over the Azure platform, anyways I will explore them myself. 😁 #P.S. I really would like to see how you looked with hairs?😁 Any medium for that?🙄
terrific ! well explained 👍
John, great job, as always! P.S. Nice t-shirt ;-)
Very clear - many thanks 👍
@NTFAQGuy
10 ай бұрын
You are welcome!
This is a great video and you always explain things so easily and simply. I do have a question on subnetting and it’s more from a security sense. This could be too broad of a question but when should you use a subnet to segregate environments at a more granular level. For example let’s say you have multiple SQL PaaS managed services running and they are connected to a front end web app. Should you segregate each deployment in its own subnet. May be a bad example but I’m struggling to know when to use them
@NTFAQGuy
3 жыл бұрын
You can think about if you want to control the flow of data between systems placing them in different subnets help control that since you can then apply things like network security groups. Note you can segment even within subnet by the rules but at subnet is easier to manage.
Thank you !
finally a good video!
Nice work thanks!
@NTFAQGuy
3 жыл бұрын
You bet!
Haha nice shirt dude. Also great content keep on going!
@NTFAQGuy
3 жыл бұрын
Appreciate it!
Thank you!!
@NTFAQGuy
3 жыл бұрын
You're welcome!
Hi, John, excellent videos, could I ask you to do one on Pwsh DSC in Azure if you know smart ways to do it?
@NTFAQGuy
3 жыл бұрын
Azure automation works with dsc
Nice explanation, thanks! Finally something good comes out of being, well, quite old - I can do binary (almost) in my sleep :-) Not that I'd want to, though...
@NTFAQGuy
3 жыл бұрын
Lol
Any videos of how you recommend subnetting a 3 tier/4 tier (with nested microservices behind a second load balancer), multi region, multi availability set web application?
@James5976
3 жыл бұрын
I found docs.microsoft.com/en-us/azure/architecture/reference-architectures/n-tier/n-tier-sql-server helpful for my question
@NTFAQGuy
3 жыл бұрын
Nothing specific but multi region means multi vnet. I have virtual networking videos which may help you architect and also have load balancer deep dives. Availability sets have no impact really. Look at peering for between the vnets. Mesh may help with the micro services.
Hello John Sir - you videos are always useful .. Thanks ..any paid training is available ?
@NTFAQGuy
3 жыл бұрын
No paid training really. I post everything to KZread. I have some things on Pluralsight that are certain certification track specific.
@prasadshivrajurkar6032
3 жыл бұрын
@@NTFAQGuy Thanks Sir ..
@Travelwandrer
3 жыл бұрын
Just to add what John mentioned, he has covered most of Az 104 topics in his KZread videos. In case, anything left, you must find some other videos from somebody covering other topics or in different way. *I haven't watched this video yet but must be good content as usual, might be bcoz I am from Networking background with needing info. John's other videos are really thorough on the subject per my knowledge and experience so far. So, don't pay for items those available for free. Kudos John!
@prasadshivrajurkar6032
3 жыл бұрын
@@Travelwandrer True .. kudos John Sir ..
I like the logo on the T-shirt. HA HA HA HA!!!!!!
@NTFAQGuy
3 жыл бұрын
Thanks :-)
I thought Azure moved to VXLAN instead of NVGRE?
@NTFAQGuy
3 жыл бұрын
No. Hyperv added support for vxlan but that didn’t change sdn in azure.
Why does 255.255.255.0 always start with 192.128..... I mean, why cant I just say 11.3.4.(hostid, for example 5)
@NTFAQGuy
2 жыл бұрын
because 192.168.0.0/16 is part of RFC 1918 and non Internet routable so commonly used and divided up into "class C" which is the /24. Does not have to start with 192.168 at all, just commonly used for demos and internal environments along with rest of RFC1918 space.
@deb62615
2 жыл бұрын
@@NTFAQGuy is there any reason to use class a over b or c? In your video you said there are no problems anymore, and the reason there are many subnets is because for example to organise. If that is the case, why not always use class a so you never have not enough hosts? I find it really really really hard to understand how to decide what the submask should be... there is no reason for me to chose the one above the other I feel like...
@NTFAQGuy
2 жыл бұрын
@@deb62615 subnet mask size is based on how many hosts you want to put in one segment. /24 is very common. in your private network yes 10/8 would give you maximum possible address range. Just need to consider connecting to other networks in the future and not overlapping etc.