Thanks for watching! Here is the lab: networkdirection.net/labsandquizzes/labs/lab-introduction-to-vlans/ Here is the quiz: networkdirection.net/labsandquizzes/quizzes/introduction-to-vlans-quiz/
I'm loving this course but what app do yu use to run the labs? I cant run a single one because there is no apk that can be used to run it. It saves in .virl so i think thats why. GNS3 also dosent work.
@@ifeoluwaadeyemi8442 They're created in VIRL. however, you can import the running-configs into GNS3 if you want to. The VIRL lab was exported in GNS3 format, but it doesn't seem to work out of the box
I've never gained so much in a RUclips video. Gained my CCNA in 2019 and I've been in IT as Infrastructure engineer ever since, but I've learnt so much from your videos than I've from any other. This is beautiful
Its like you are reading my mind with the viewer questions you simulate, no one else seems to talk about the basic use case information you bring up, thank you.
So, why isn't the switch also the router in this case? Is it due to separation of duties and that the switch is not powerful enough / not equipped to route packets? And why two physical interfaces to the router for each VLAN? Wouldn't it be more efficient to just have one?
It's true that switches can often act as routers in many cases (they are called layer-3 switches). There are a few different reasons why we might prefer to use a dedicated router. For one, in these videos I often use routers to make my point more clear In the real world though, as you've mentioned, sometimes it's best to separate those duties. Switch hardware is often tuned to switch frames very quickly, while routers are tuned for other technologies. Also, routers sometimes have special hardware to support specific WAN types, which switches don't have. The summary is that it can change on a case by case basis. As you get further into network engineering, you will start to learn some design principles, which will help to understand why and when to do things a certain way
You said that I can use two subnet devices in one vlan if I do so and device of one subnet broadcast a message then will it go to devices of another subnet attached to Same vlan without router?
Yes, that's right. The other device will "see" the broadcast message. Normally it will discard it, but it is possible to see the information in the broadcast. That makes it a security issue
Hey, great video as always! Your channel helped me a lot in understanding the fundamentals about networking :) I think I found a typo though: in the logical diagram (10:50) both networks are called 192.168.10.0/24. But when you ping from workstation 1 (15:45) you use the IP 192.168.20.1 for server 1. So I guess the server network really is 192.168.20/24?
Hi M Marcello, great spotting! You are absolutely right, I would like to say that I did this to see who was really paying attention but unfortunately typos happen. Have a great day!
Thank you again for the great content and easy learning experience. I went on your website and checked out your "labs" my question is do you need and "special" software to run the "labs" ? I was also wondering if you would do a tutorial/promo video about your "labs" Thanks for all your help with simplifying "networking" You definitely have easy to follow content. May God bless you and your channel !
Hi Global Faith, thanks for your comment! I use "VIRL" for labs, which is what you see in my videos. However, you can use other software. The downloadable labs on my website include configuration files that you can import into other lab software. If you would like more information, towards the end of my Cisco CLI for Beginners video (Part 10 Network Fundamentals series) we look at some lab options. Thanks again. Have a great day!
It finds this information from the Ethernet header. This header includes a source and destination MAC address. The MAC address table will tell the switch or router which interface to forward the frame on. As for the VLAN, this could be known in one of two ways. A frame may have a VLAN tag in the ethernet header. Or, for untagged frames, the VLAN is assigned based on the interface it arrives on (remember the 'switchport access vlan ...' command?)
OK, so I pick up some fancy smartswitch or managed switch used on eBay.. And I hook it up to my edge-router. If I have 10 VLANs configured on my 24 port managed switch, do I need 23 routers to tie them all together? My edge router only has a couple ports, the "LAN" ports are just switched so really only 2 right?
This is where you would look at running a trunk to your router (a link with multiple vlans), and configuring your router with sub-interfaces. This is called 'router on a stick'
Oh it must be the first, i am sorry, i forgot to said, thank you so much for the videos. I have watched almost all of your videos in Fundamental Playlist and it's was more help me for understanding "what the network is" instead when i am in the class. Btw Sorry for my grammar, it was so suck 😂
1 question it may be dumb If your home network is assigned a private IP address of say 192.168.0.1 /24 and you have a switch that you have 2 VLANs on, does Vlan 1 get to use the same address (192.168.0.1/24) what gives vlan 2 a different address? Does the router get a second public IP address for communicating with Vlan1? Or is there something I'm missing?
What do you mean by "a second public IP address"? If you were thinking of the IP address that your ISP gives you, then no. First of all, if you leave your home network separate and create a VLAN that would operate on the same IP network it's only going to work if you completely isolate them and don't connect them anywhere in the whole network. The router that's routing traffic between your two VLANs should have two IP addresses: one for the VLAN 1 and another for the VLAN 2.
You would use entirely different subnets for each VLAN. You may configure a router to forward packets between the two subnets/VLANs The public IP is separate to this. Both of these VLANs can 'use' the public IP through NAT/PAT
![Seungmin "그렇게, 천천히, 우리(As we are)" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/kAzmhLHePqU/mqdefault.jpg)
Thanks for watching! Here is the lab: networkdirection.net/labsandquizzes/labs/lab-introduction-to-vlans/
Here is the quiz: networkdirection.net/labsandquizzes/quizzes/introduction-to-vlans-quiz/
very good video.
I'm loving this course but what app do yu use to run the labs? I cant run a single one because there is no apk that can be used to run it. It saves in .virl so i think thats why. GNS3 also dosent work.
@@ifeoluwaadeyemi8442 They're created in VIRL. however, you can import the running-configs into GNS3 if you want to.
The VIRL lab was exported in GNS3 format, but it doesn't seem to work out of the box
I've never gained so much in a RUclips video. Gained my CCNA in 2019 and I've been in IT as Infrastructure engineer ever since, but I've learnt so much from your videos than I've from any other. This is beautiful
This is one of the best lectures all over the network!!! So understandable so easy to swallow. I love it.
Thank you!
Its like you are reading my mind with the viewer questions you simulate, no one else seems to talk about the basic use case information you bring up, thank you.
I love hearing this! I've tried to deliberately take this approach, so I'm glad its working
Best channel for networking, by far. I would highly recommend it to anyone interested in learning
Thanks Adam! I really appreciate your comment! 😀
Thanks once again for this great series!
You're very welcome!
Thank you ! Thank you ! Thank you ! Thank you ! Thank you !
You're very very very very very welcome!
thanks for mentioning cisco packet tracer in one of the previous videos, I did the whole course in one go and it was fun
Thank you so much for sharing this information
You're welcome
This must be one of the best networking tutorials not only in RUclips but also Udemy and all other paid services…
So good to hear, thanks!
This channel is underrated .. thank you guys
Thank You!
As always very informative.
Just excellent and enjoyable to watch. Keep it up Network Direction 👍
very good one, easy to understand
Thanks, glad you like it
I simply love your Channel... Really congrats✌🏻
It is really useful for me
Glad it’s useful 😎
Love your vids! They are really helpful and easy to understand. Thanks for making them. ^u^
Thanks Radin, glad you like them!
11:37 left image, is that vlan 20 for server-1, and server-2?
Yes, that's right. Server 1 and 2 both belong to VLAN 20
Please are you using the CISCO packet tracer I am trying to do what you're using for the labs on a IMAC
thank you so much!
You're welcome!
Thank you
You're welcome
So, why isn't the switch also the router in this case? Is it due to separation of duties and that the switch is not powerful enough / not equipped to route packets? And why two physical interfaces to the router for each VLAN? Wouldn't it be more efficient to just have one?
It's true that switches can often act as routers in many cases (they are called layer-3 switches).
There are a few different reasons why we might prefer to use a dedicated router.
For one, in these videos I often use routers to make my point more clear
In the real world though, as you've mentioned, sometimes it's best to separate those duties. Switch hardware is often tuned to switch frames very quickly, while routers are tuned for other technologies.
Also, routers sometimes have special hardware to support specific WAN types, which switches don't have.
The summary is that it can change on a case by case basis. As you get further into network engineering, you will start to learn some design principles, which will help to understand why and when to do things a certain way
You said that I can use two subnet devices in one vlan if I do so and device of one subnet broadcast a message then will it go to devices of another subnet attached to Same vlan without router?
Yes, that's right. The other device will "see" the broadcast message. Normally it will discard it, but it is possible to see the information in the broadcast. That makes it a security issue
Hey, great video as always! Your channel helped me a lot in understanding the fundamentals about networking :)
I think I found a typo though: in the logical diagram (10:50) both networks are called 192.168.10.0/24. But when you ping from workstation 1 (15:45) you use the IP 192.168.20.1 for server 1. So I guess the server network really is 192.168.20/24?
Hi M Marcello, great spotting! You are absolutely right, I would like to say that I did this to see who was really paying attention but unfortunately typos happen. Have a great day!
@@NetworkDirection man that caused alot of confusing for a network dummy like me, btw thank you for your knowledge and big efforts
Thank you again for the great content and easy learning experience. I went on your website and checked out your "labs" my question is do you need and "special" software to run the "labs" ?
I was also wondering if you would do a tutorial/promo video about your "labs"
Thanks for all your help with simplifying "networking" You definitely have easy to follow content.
May God bless you and your channel !
Hi Global Faith, thanks for your comment! I use "VIRL" for labs, which is what you see in my videos. However, you can use other software. The downloadable labs on my website include configuration files that you can import into other lab software.
If you would like more information, towards the end of my Cisco CLI for Beginners video (Part 10 Network Fundamentals series) we look at some lab options. Thanks again. Have a great day!
Nice animations, clear voice and explanation. Just wondering which program you are using for making such nice video.
Thanks
can we buy this video
series
Sorry, what do you mean?
@@NetworkDirection the video u have . Can I buy them
Yes, I have trouble understanding VLANS, also.
But how does the router know which VLAN and which specific device in the VLAN the frame is meant for?
It finds this information from the Ethernet header. This header includes a source and destination MAC address.
The MAC address table will tell the switch or router which interface to forward the frame on.
As for the VLAN, this could be known in one of two ways. A frame may have a VLAN tag in the ethernet header. Or, for untagged frames, the VLAN is assigned based on the interface it arrives on (remember the 'switchport access vlan ...' command?)
what happened if different Vlan have same network address like 192.168.10.0/24
OK, so I pick up some fancy smartswitch or managed switch used on eBay.. And I hook it up to my edge-router. If I have 10 VLANs configured on my 24 port managed switch, do I need 23 routers to tie them all together? My edge router only has a couple ports, the "LAN" ports are just switched so really only 2 right?
This is where you would look at running a trunk to your router (a link with multiple vlans), and configuring your router with sub-interfaces.
This is called 'router on a stick'
1 vlan is 1 network, so between one vlan to another vlan is different IP network??
But if i used the switch without separate it to several Vlan (not using vlan methode) . Is all of the end devices have a same IP network?
Oh it must be the first, i am sorry, i forgot to said, thank you so much for the videos. I have watched almost all of your videos in Fundamental Playlist and it's was more help me for understanding "what the network is" instead when i am in the class.
Btw Sorry for my grammar, it was so suck 😂
It's tracert -d in Windows.
1 question it may be dumb
If your home network is assigned a private IP address of say 192.168.0.1 /24 and you have a switch that you have 2 VLANs on, does Vlan 1 get to use the same address (192.168.0.1/24) what gives vlan 2 a different address? Does the router get a second public IP address for communicating with Vlan1? Or is there something I'm missing?
What do you mean by "a second public IP address"? If you were thinking of the IP address that your ISP gives you, then no.
First of all, if you leave your home network separate and create a VLAN that would operate on the same IP network it's only going to work if you completely isolate them and don't connect them anywhere in the whole network.
The router that's routing traffic between your two VLANs should have two IP addresses: one for the VLAN 1 and another for the VLAN 2.
You would use entirely different subnets for each VLAN. You may configure a router to forward packets between the two subnets/VLANs
The public IP is separate to this. Both of these VLANs can 'use' the public IP through NAT/PAT
is -n an abreviation to -names
Are you still making videos
plenty