Some notes on this lab in PT: When I did this lab, the first 3 pings failed, and only the fourth and final ping succeeded. When I tried pinging again, all pings were successful. I re-did the lab to "reset the state" so that I could view the first pings again in simulation mode. What happened was this: PC1 initiated an ICMP process which triggered an ARP request for R1's G0/1 MAC. The ARP was successful and then the ICMP echo request successfully reached R1. But then R1 needed to look up the MAC address for R2 in its ARP table, which it did not have. So R1 dropped the ICMP packet, and initiated an ARP request for R2, which was successful. Then the second ICMP echo request was initiated at PC1, and this time it was successfully forwarded to R2 from R1, but then R2 didn't have R3's MAC in its ARP table! So R2 dropped the second ping request, and initiated an ARP request for R3, which was again successful. Then PC1 initiated the third ping request, and it successfully reached R3 this time, but of course R3 didn't have PC2's MAC, so R3 dropped this third ping packet and initiated an ARP request for PC2. Finally, once all the routers knew eachother's MAC addresses, the fourth and final ping request succeeded.
Thank you for confirming.. Same thing happened to me.. Whats crazy is I actually was able to comprehend what happened, and why in your explination. Hell I guess that means I am actually learning. lol
I think days and labs 11 - 18 are absolutely crucial to passing the CCNA. This is my weak point and I think after doing each lecture and lab like 3x each, I'm finally able to get things to click and progress. Strangely all that eigrp stuff and AD comes way easier to me. Thanks Jeremy and good luck all :)
I do agree.. not from the perspective of someone with a. CCNA but as someone learning. It's so easy to forget when setting up something simple like each port of the router is a different interface an different IP but these labs give you that clarity to know yea I pinged that
I love your channel. I am really learning and following without difficulty the ccna path. Your lessons aren’t boring. The concepts are explained very well. Greetings from Italy !
absolutely brilliant series for CCNA. first time ever I am really committed to completing the series just because of the Jeremy's way of teaching. one of the good thig in this series is all the content is explained with practical labs. Highly recomended to start career in networking.
Awesome lesson TY Jeremy. I have used several paid classes and even one bootcamp (work paid for it) you are the only one that I can truly follow. (I also enjoy Certbros explanations). I like that I get to lab next to you and check my work. This is the BEST method by far! MashAllah.
You are a fantastic instructor, one of the very best. I just never realized how difficult and boring it was to be a Cisco engineer. Respect to those that get their CCNA, I had to use just 6 months to pass my Network+ exam which is nothing close to this level.
@Real HIFI Help, bro you are my spirit human. It took me two tries and 6 months to pass the net+ exam as well. The concepts just weren't sticking. I'm better now but whewwww it took me longer than usual to get here, but im here now. lol
When I did the initial ping, it came back with 4 Time Outs, and I freaked out, checking all the routing tables, frantically trying to pin down the cause. After everything checked out, I nervously sent another ping, and -- voila! It must have been the ARP you mentioned!
I promise to send you at least $100 once I pass the exam. I would like to take exam before the end of the year. Will book it in and reach out to you as soon as I pass! Thank you for taking the time to make these detailed videos.
This was so informative and helpful! Of course, I had to pause the video a ton of times and double check my work against your CLI but it all matched up and once ARP got sorted, the ping came back with 0% loss! Who knew I could feel so satisified with a simple ping command?
This lab is great because I had this scenario as an interview question: "how many static routes are required for PC1 to be able to ping PC2?". Unfortunately I was not prepared for that question. I tried this out after the interview, and thought 6 routes were required (it works with 6 static routes as well). Today i tried this lab out on GNS3 with real Cisco images, and it works with the 4 static routes just as does in Packet Tracer. :-)
Yep, it works with 6 static route too. Just curious, why it works with only 4 static route? And At the end, When Jeremy tested the ping from PC1 to PC2, Unless I,m wrong, but I think he already tried the ping before because ping was supposed to fail (to resolve ARP) and especially when packet has to across multiple routers. Other than that, Jeremy gives clear explanation and he always goes beyond. Still want to know why it works with only 4 static routes :)
I hope you're enjoying the course! If you want another great set of FREE packet tracer labs for the CCNA, check out Neil Anderson's lab guide here: www.flackbox.com/cisco-ccna-lab-guide#jm1
Much appreciated Jeremy. You are the one and the only one. Waiting your CCNP course and CCIE as well. I have a question " Which situation I shall choose between using exist interface or next hope?"
I watch the lecture videos at least three time and coming on to these labs feels like a hot knife cutting butter. I configure them even before going though lab videos. Thanks Jeremy
I feel so great with your labs Jeremy, it makes me feel than I'm actually learning by putting into practice all the theory I have seen and read! You are the best!
hey Jeremy , I completed the lab first and then watched your explanation. I didn't know about "Description" command before. And I configured all the routes with next hop. 😀
Jeremy, Thank you for answering my question. Thank you for this video. I needed someone to walk me through it just one time and you did. You helped me find three things I was doing wrong. I don't have words to describe how awesome you are in every way. I wish you were my dad. Thank you.
Two additional things I did in the lab: 1. Configure routes to ALL target networks. (e.g. a route to 192.168.13.0/24 via 192.168.12.2 on R1) - on my first try all three pings failed. This however allowed me to ping all interfaces "in between" and thus help debugging (even tho in my case the issue was simply I didn't wait long enough for ARP) 2. If you configure a route with a next-hop IP where the corresponding interface is still in Protocol "down" state, the route won't show up in "show ip route". If you configure it with the Interface instead of the next-hop IP, it will show up.Confused me a good bit here on G2 not sure how relevant this is for the CCNA, but atleast for me it made it easier to visualize in my brain what I actually did and why.
Could I know how to get the lab exercises? Am I just supposed to get it from the link given or have to do something else. I tried but failed to download the labs.
Love this lesson, as others have stated, this is a VERY important one. My only critique would be it's pretty fast paced. Hard to pause in one window while working in the other at that pace. But still grateful to have it
@@DownCity I'm also a non-native English speaker from France (you know frenchies are unfortunately very bad at English). I learned English most of the time by watching videos about courses in English and then by whatching other videos in English like yours. Of course I had previouly some basic knowledge from school in English. But I encourage all the people to learn English because it is a lovely language and it is also the international one nowadays. If you want to improve your English I give you some very good youtube channels I already worked with. Speak English With Mr Duncan: ua-cam.com/users/duncaninchinaplaylists Anglo-Link: https: //ua-cam.com/users/MinooAngloLink. Have a nice day :)
In the simplest terms, IP Routing is the process of moving packets from its source to its destination across inter networks. To be able to route packets, a router must know at a minimum the following: Destination address Neighbor routers from which it can learn about remote networks Possible routes to all remote networks The best route to each remote network Be able to maintain and verify routing information
For some reasons, on my packet tracer lab at this point 9:44. it said invalid input detected at g0/0. However if I put a space between g and 0/0 it works, like this g 0/0
Hi Jeremy! thanks a lot for this amazing lab, I have question about configuring static route using the Gigabit Ethernet (video 9:44), we used g0/0, is the g0/0 belongs to R2 or R1? Thanks in advance and I appreciate your hard work with those videos.
I got a problem connecting the interfaces of the routers to the end devices. I don't know but in this vid, you didn't have a problem like that. I search over the net and solved it by configuring the speed and duplex of the routers, that it must be the same with the PCs. Thanks Jeremyyyyy!
@@JeremysITLab Yes, I mean the switches. I read that the speed and duplex must be the same, so I only checked the switch for int stat and set the router with the same speed/duplex, and it worked!
I ran into some issues but was able to figure it out by reviewing the routing tables. I was literally pumping my arms in the air with joy when pings were successful lol. You are an amazing teacher, thank you.
@@hzakaria5338 Might be a problem with packet tracer, I also did everything correctly but for some reason ping failed on PC1 but then I did it on PC3 and it went all well without changing anything. I'll retry the lab and report if the problem re-occurs.
@@hzakaria5338 I re-did it and tested it out in simulation mode, the first ping after setting everything up properly will still fail because of the ARP requests from the routers trying to find the next hop ip address' router's MAC address and add it to the ARP table. In my case now that I redid it the first three ICMP requests failed and the 4th one went trough so it was a 75% failure and 1 went trough. The first time I did the lab all 4 failed but after pining again everthing went properly so I assume I configured everything well there too but the ARP requests made all 4 ping attempts to fail.
@@hzakaria5338 I looked into it further, arp requests will vary depending on how you set the static address (ip address mask next hop address or ip address mask interface) so I assume that is why my 2 labs varied in amount of packets recieved on first ping (100% loss during first lab and 75% loss on second lab). In my first attempt doing the lab I set one of the statics in R2 to interface and the other via next hop address, I also configured R1 to have R2 as it's default route/gateway of last resort and the same for R3 for the sake of excercising the command. In my second lab I did things as shown in Jeremy's video. All of these factors must have influenced the amount of ARP requests and thus the difference in packet loss % during first ping attempt.
I followed the instructions for this lab, however the final steps were not same as showed in the lab, PC1 first failed to ping PC 2, after several attempts, it showed just 1 successful attempt, same was the case when PC2 tried to ping PC1. IS IT A PACKET TRACES ISSUE ?
I was a total beginner to IT and networking, so I just picked a course and followed it as the instructor said. I used Neil Anderson's course on Udemy by the way, check it out!
@@JeremysITLab CTP is Cisco Packet Tracer ;) Anyway everything is fine. What you are doing is great. You just said for instance that the description (using the "description" command on an interface) is not reporting in the "Name" column when typing the "switch# sh ip status" command. Also when changing manually the speed and/or the duplex values, it still appears as auto when typing the "switch# sh ip status" command. Anyway it is not so serious. Thank you so much for all :)
I try doing the labs with no video at first and try not to watch the video, unless I am truly stumped. Luckily I did found my problem without the assistance of the video. I did do something wrong at first, which when doing the "ip route" command, it showed "inconsistent address" or something like that. I was wondering why and then I did a "?". I realized that I needed the network destination address and I put the Address of PC3 the first time. I did an extra of implementing the "enable secret" and "service password-encryption" as well. I like this style of learning with the Anki Flashcards. It allows me to go at my own pace, unlike what I did in college, where it felt rushed.
Maybe this is a Packet Tracer bug but after following instructions twice I still could not ping PC2. Changing R2s route to the 192.168.1.0 network from the interface to the IP fixed this. So for anyone else having trouble, undo the route then fix it: no ip route 192.168.1.0 255.255.255.0 g0/0 ip route 192.168.1.0 255.255.255.0 192.168.12.1 Thanks Jeremy!
Hi Jeremy, I cant express how much I appreciate you putting this course together for us in the the networking IT community. I just have a quick question that I'm not so sure about. Around 9:48 min into the video (configuring Static Routes Day 11 Lab video), when configuring the static route to 192.168.1.0 255.255.255.0 g0/0, you choose to use the exit interface instead of the next hop ip address. I wanted to ask, if we didn't indicate the exit interface, what would be the next hop address be instead? Thanks
You can get the flashcards from the top line of the description: Free CCNA 200-301 flashcards/Packet Tracer labs for the course: jeremysitlab.com/youtube-join/
Great video from a great teacher, you make things look simple, I'd like to know how to get the packet tracer lab files tho as I can't find them in resources..
The end scared me a bit, I actually paused and worked oon a large portion of this myself...then when we went to ping at the end I got 3 time outs before I got a reply.
I did everything exactly the same as shown in the video, except at 10:32 I configured "R2(config)#ip route 192.168.3.0 255.255.255.0 g0/1", then if I ping from either PCs it will time out at every ping. Is there a reason exit-interface can't be configured at both ends of a router, or is it just some packet tracer quirks? It works fine if I set R2 to route 192.168.3.0 using next-hop ip instead of exit-interface.
Thanks so much for this great Course. God Bless you and keep you well I had a question please Why you don't use this IP route in R1? R1# ip route 192.168.13.0 255.255.255.0 192.168.12.2
Good question! The requirement is that PC1 can ping PC2, and R1 doesn't need to know the route to the 192.168.13.0/24 network for that. R1 just needs to know that to reach 192.168.3.0/24, it should send the packet to R2.
@@JeremysITLab Does this also apply for bigger networks? We were taught to always include the serial's network when routing. When is it okay to not include a route to the serial's network and when should you include it?
For those who are having proplem with the packet canoot reach its destination. I solved this problem by deleting R2 and set it up again. I hope it work with you.
For these practice labs I make, just download the lab file from the link in the description. For making your own labs, any kind will work. I usually use 2911 routers and 2960 switches in my labs.
I have no idea what I've done wrong but I cannot get a ping response from PC1 to PC. Following through the ICMP traffic, I can see it gets as far as PC2, then on the reply it is getting stuck at the G0/1. I've double and triple checked the interface settings on the PCs and routers and all the static routes. ARP doesn't seem to get past R1 either which is weird. Any ideas? Edit: I was able to sort it by adding in additional default routes: R1 (config) #ip route 0.0.0.0 0.0.0.0 192.168.12.2 R3 (config) #ip route 0.0.0.0 0.0.0.0 192.168.13.2 R2 (config) #ip route 192.168.3.0 255.255.255.0 192.168.13.3 R2 (config) #ip route 192.168.1.0 255.255.255.0 192.168.12.1 I'm getting ping responses now. I think Packet Tracer was having a moment.
Observation with packet tracer. I did the entire lab and the pings weren't working. I double checked up and down the config. After about 40 minutes of checking my work and comparing I restarted the lab from a clean starting point. On this next time through - the first time I pinged it timed out again... Then after looking but making no changes to any device in the chain I use the up arrow from the dos prompt and do the same command again - and it worked. I literally made no changes to any device. I'm not sure if that's a packet tracer thing or something else... but pack your patience when doing labs on it.
I initially had an issue with my first ping from PC1-PC3 and figured it had something to do with configuring the interface g0/0 for R2 dest: 192.168.1.0 and I went back Into the router and specified the IP to use for the interface and it worked immediately afterwards. I was thinking Jesus if this isn't the issue then im going to have go a mission in order to figure out where I went wrong!
Hello Jeremy, so I made the configurations once, and it did not send any ping, I remaked them twice, with opening new lab, and now it says Pinging 192.168.3.1 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Reply from 192.168.3.1: bytes=32 time=58ms TTL=125 Ping statistics for 192.168.3.1: Packets: Sent = 4, Received = 1, Lost = 3 (75% loss), Approximate round trip times in milli-seconds: Minimum = 58ms, Maximum = 58ms, Average = 58ms I did the same specifics twice P.S The only differences is on 1:32 in your programme says Gateway, on my programme says Default Gateway, Idk if it is a difference, but just saying!
Hello, thank you for making these informative videos. I have been recently getting into computer technology and came across your channel. There is so much information to learn about computers/internet etc. and it can be overwhelming for someone like me but the way you simplify it and reiterate points of the lesson along with providing flashcards and packet tracer labs has made it easier for me to keep pursuing my new passion. I really appreciate it. On a side note, I had one question, how do you delete a static route from the ip table?
Thanks Joshua, I'm glad the videos are helping! Deleting a static route is the same as deleting any configuration, put 'no' in front of the command. For example: Router(config)# no ip route 10.0.0.0 255.255.255.0 192.168.1.2 This command will remove the route.
Hi Jeremy. Have you noticed that ping from R1 to 192.168.3.1 is unreachable and from R3 to 192.168.1.1 is the same unreachable ? But from PC1 to PC2 and PC2 to PC1 is reachable. In my opinion this is weird and am not sure if this would work in real world. Any idea? BTW great course so far.
It's not necessary for the router to be able to ping every single destination on the route to the destination. For example, your computer can access youtube's servers to watch this video, but it probably can't access every single router on the path to the youtube server!
Hi Jeremy, your course is quite better than paid courses on udemy. I want to ask you, how many videos are you going to totally make? And when? I want to do new ccna as soon as possible and your videos are the best. Thanks
Thank you! I think it will be a maximum of 50 'days', but since I don't have a lot of time to make videos it will take a while to finish the course. If you want to get your CCNA soon, I recommend using another course too, until I finished my course.
Thanks for your hard work , one question is bothering me , we usually never use switch at home because router does has some ports so how layer 2 works the without switch how it identify the mac address of connected devices.
Actually, a home 'router' isn't just a router, it's a multipurpose network device which functions like a router + switch + firewall + wireless access point. So, those ports you connect to on your home router are actually Layer 2 switch ports.
Some notes on this lab in PT: When I did this lab, the first 3 pings failed, and only the fourth and final ping succeeded. When I tried pinging again, all pings were successful. I re-did the lab to "reset the state" so that I could view the first pings again in simulation mode. What happened was this: PC1 initiated an ICMP process which triggered an ARP request for R1's G0/1 MAC. The ARP was successful and then the ICMP echo request successfully reached R1. But then R1 needed to look up the MAC address for R2 in its ARP table, which it did not have. So R1 dropped the ICMP packet, and initiated an ARP request for R2, which was successful. Then the second ICMP echo request was initiated at PC1, and this time it was successfully forwarded to R2 from R1, but then R2 didn't have R3's MAC in its ARP table! So R2 dropped the second ping request, and initiated an ARP request for R3, which was again successful. Then PC1 initiated the third ping request, and it successfully reached R3 this time, but of course R3 didn't have PC2's MAC, so R3 dropped this third ping packet and initiated an ARP request for PC2. Finally, once all the routers knew eachother's MAC addresses, the fourth and final ping request succeeded.
I thought that would be the case. In the lesson there was no packet loss which I thought was weird. Thanks for sharing my man!
that is the same case for me here . I thought maybe I missed some configuration steps .
I imagine it would only be around 1 drop in a real network otherwise that would be extreme with hundreds or router hops
Thank you, I thought I was hallucinating for a while....
Thank you for confirming.. Same thing happened to me..
Whats crazy is I actually was able to comprehend what happened, and why in your explination.
Hell I guess that means I am actually learning. lol
I think days and labs 11 - 18 are absolutely crucial to passing the CCNA. This is my weak point and I think after doing each lecture and lab like 3x each, I'm finally able to get things to click and progress. Strangely all that eigrp stuff and AD comes way easier to me. Thanks Jeremy and good luck all :)
I do agree.. not from the perspective of someone with a. CCNA but as someone learning. It's so easy to forget when setting up something simple like each port of the router is a different interface an different IP but these labs give you that clarity to know yea I pinged that
One can not resist to become a networking expert by following these crystal-clear explained videos. Thank you very much.
I can't express my feeling when I successfully ping to the PC on this lab, you're people's teacher Jeremy. Truly appreciate your effort!!
I love your channel. I am really learning and following without difficulty the ccna path. Your lessons aren’t boring. The concepts are explained very well. Greetings from Italy !
Thanks, glad to hear it! Greetings from Japan :)
As a boy, Jeremy was haunted that the world might go without understanding routing and switching science.
Don't say like that ..he is doing a hell lot more than any of us combined ....for "FREE"
I actually find this very fascinating. I've always wanted to know how this happens. Other videos are not close to this level of clarity
Count Dracula - Muahahaha
absolutely brilliant series for CCNA. first time ever I am really committed to completing the series just because of the Jeremy's way of teaching. one of the good thig in this series is all the content is explained with practical labs. Highly recomended to start career in networking.
0:55 - "Repetition is very important to getting used to the CLI." Yes sir!
Awesome lesson TY Jeremy. I have used several paid classes and even one bootcamp (work paid for it) you are the only one that I can truly follow. (I also enjoy Certbros explanations).
I like that I get to lab next to you and check my work. This is the BEST method by far! MashAllah.
Thank you Dawud :)
You are a fantastic instructor, one of the very best. I just never realized how difficult and boring it was to be a Cisco engineer. Respect to those that get their CCNA, I had to use just 6 months to pass my Network+ exam which is nothing close to this level.
@Real HIFI Help, bro you are my spirit human. It took me two tries and 6 months to pass the net+ exam as well. The concepts just weren't sticking. I'm better now but whewwww it took me longer than usual to get here, but im here now. lol
I wish you were my teacher of networks on my institute. So good explanation!! I hope can pass the exam with your course. Thanks a lot
When I did the initial ping, it came back with 4 Time Outs, and I freaked out, checking all the routing tables, frantically trying to pin down the cause. After everything checked out, I nervously sent another ping, and -- voila! It must have been the ARP you mentioned!
I promise to send you at least $100 once I pass the exam. I would like to take exam before the end of the year.
Will book it in and reach out to you as soon as I pass!
Thank you for taking the time to make these detailed videos.
did you pass yet? and did jeremy get his $100 hahah
This was so informative and helpful! Of course, I had to pause the video a ton of times and double check my work against your CLI but it all matched up and once ARP got sorted, the ping came back with 0% loss! Who knew I could feel so satisified with a simple ping command?
This lab is great because I had this scenario as an interview question: "how many static routes are required for PC1 to be able to ping PC2?". Unfortunately I was not prepared for that question. I tried this out after the interview, and thought 6 routes were required (it works with 6 static routes as well). Today i tried this lab out on GNS3 with real Cisco images, and it works with the 4 static routes just as does in Packet Tracer. :-)
One?
Yep, it works with 6 static route too. Just curious, why it works with only 4 static route?
And At the end, When Jeremy tested the ping from PC1 to PC2, Unless I,m wrong, but I think he already tried the ping before because ping was supposed to fail (to resolve ARP) and especially when packet has to across multiple routers.
Other than that, Jeremy gives clear explanation and he always goes beyond. Still want to know why it works with only 4 static routes :)
I hope you're enjoying the course! If you want another great set of FREE packet tracer labs for the CCNA, check out Neil Anderson's lab guide here: www.flackbox.com/cisco-ccna-lab-guide#jm1
Thanks a lot ! Jeremy, thanks for you support
really enjoying the lab sessions as it clarifies doubts. please update on the series as we are eagerly waiting for more.
You are a saint sent from heaven. Thank you.
Tysm ❤️ for course..
Much appreciated Jeremy. You are the one and the only one. Waiting your CCNP course and CCIE as well.
I have a question " Which situation I shall choose between using exist interface or next hope?"
BEST ever am not saying this to praise Alfred but to thank him for not breaking the trust i had for him and keeping to his word.
Thank you :)
Thanks @JeremyITLab I am now able to configure IP routes.
I watch the lecture videos at least three time and coming on to these labs feels like a hot knife cutting butter. I configure them even before going though lab videos. Thanks Jeremy
I couldn't understand this, but after watching this I was able to understand it easily.thank you
Nice :)
Thank You!! This is the best video about "setting up a static Route" using PT, Clearly explained.
I feel so great with your labs Jeremy, it makes me feel than I'm actually learning by putting into practice all the theory I have seen and read! You are the best!
Thank you so much for all you do, you should be in the Hall of Fame of Networking.
Thanks Jose :)
hey Jeremy ,
I completed the lab first and then watched your explanation. I didn't know about "Description" command before. And I configured all the routes with next hop. 😀
This training is by far the best training to clear the concepts and learn hands on practice.
Jeremy,
Thank you for answering my question. Thank you for this video. I needed someone to walk me through it just one time and you did. You helped me find three things I was doing wrong. I don't have words to describe how awesome you are in every way. I wish you were my dad. Thank you.
Happy to help ;)
i love you Jeremy , i am soo grateful for you and your efforts .
Thank you, Hamza :)
Two additional things I did in the lab:
1. Configure routes to ALL target networks. (e.g. a route to 192.168.13.0/24 via 192.168.12.2 on R1) - on my first try all three pings failed. This however allowed me to ping all interfaces "in between" and thus help debugging (even tho in my case the issue was simply I didn't wait long enough for ARP)
2. If you configure a route with a next-hop IP where the corresponding interface is still in Protocol "down" state, the route won't show up in "show ip route". If you configure it with the Interface instead of the next-hop IP, it will show up.Confused me a good bit here on G2
not sure how relevant this is for the CCNA, but atleast for me it made it easier to visualize in my brain what I actually did and why.
AD. 1. I had to do the same. Not sure why, but that how I managed it to work.
These videos from Jeremy are really helpful. You made it easy.
Thanks Jeremy. One of the best teacher in UA-cam
Could I know how to get the lab exercises? Am I just supposed to get it from the link given or have to do something else. I tried but failed to download the labs.
Every aspect is micro-segmented and concise. incredibly awesome teaching STYLE!
I love the series so far. I am on day 13 and am looking forward to completing this course. Commenting this on every video for the algorithm.
Love this lesson, as others have stated, this is a VERY important one. My only critique would be it's pretty fast paced. Hard to pause in one window while working in the other at that pace. But still grateful to have it
If you don't know it yet, alt+tab shortcut should help you switching tabs easier and faster.
Feels so good when that ping is successful. Thanks for a great lab!
very good practice, step by step, thanks Jeremy very much.
Had hard time understanding Day 11. After doing this Lab, It's slowly starting to make sense. Still have to re-watch both videos a few more times.
You can also try googling for something like 'cisco static routes' to find some other explanations, that might help
Same This really helped me better understand everything though
So thanks for this course,i'm from iraq and my english medium but this course was very helpful for me💜🌷
Thank you! I'm glad you can understand the videos :)
@@JeremysITLab 💕
@@DownCity I'm also a non-native English speaker from France (you know frenchies are unfortunately very bad at English). I learned English most of the time by watching videos about courses in English and then by whatching other videos in English like yours. Of course I had previouly some basic knowledge from school in English. But I encourage all the people to learn English because it is a lovely language and it is also the international one nowadays. If you want to improve your English I give you some very good youtube channels I already worked with.
Speak English With Mr Duncan:
ua-cam.com/users/duncaninchinaplaylists
Anglo-Link: https:
//ua-cam.com/users/MinooAngloLink.
Have a nice day :)
In the simplest terms, IP Routing is the process of moving packets from its source to its destination across inter networks. To be able to route packets, a router must know at a minimum the following:
Destination address
Neighbor routers from which it can learn about remote networks
Possible routes to all remote networks
The best route to each remote network
Be able to maintain and verify routing information
Good summary!
you are the best , I cant thank u enough for your efforts
but deeply thank u ♥
Thank you :)
Just scheduled my CCNA for this Januarary. LET'S GOOOOOO!!!
Good luck!
thank you Jeremy.. I succesfully configure this lab.. My understanding improved
Awesome, good job!
For some reasons, on my packet tracer lab at this point 9:44. it said invalid input detected at g0/0. However if I put a space between g and 0/0 it works, like this g 0/0
Thank you Jeremy for this informative Course
Thank you very much, teacher, for the clear and understandable teaching method.
Hi Jeremy! thanks a lot for this amazing lab, I have question about configuring static route using the Gigabit Ethernet (video 9:44), we used g0/0, is the g0/0 belongs to R2 or R1? Thanks in advance and I appreciate your hard work with those videos.
It is referring to R1's G0/0 as its the exit-interface. ua-cam.com/video/YCv4-_sMvYE/v-deo.html
I got a problem connecting the interfaces of the routers to the end devices. I don't know but in this vid, you didn't have a problem like that. I search over the net and solved it by configuring the speed and duplex of the routers, that it must be the same with the PCs.
Thanks Jeremyyyyy!
Do you mean the switches? The routers aren't directly connected to the end devices in this lab
@@JeremysITLab Yes, I mean the switches. I read that the speed and duplex must be the same, so I only checked the switch for int stat and set the router with the same speed/duplex, and it worked!
I ran into some issues but was able to figure it out by reviewing the routing tables. I was literally pumping my arms in the air with joy when pings were successful lol. You are an amazing teacher, thank you.
how ? I did everything exactly the same but I couldn't ping :(
@@hzakaria5338 Might be a problem with packet tracer, I also did everything correctly but for some reason ping failed on PC1 but then I did it on PC3 and it went all well without changing anything. I'll retry the lab and report if the problem re-occurs.
@@DaddyDagoth I think yes, it has to do with the packet tracer. The ping worked after I switched to simulation mode and back again to real mode. 🤞
@@hzakaria5338 I re-did it and tested it out in simulation mode, the first ping after setting everything up properly will still fail because of the ARP requests from the routers trying to find the next hop ip address' router's MAC address and add it to the ARP table. In my case now that I redid it the first three ICMP requests failed and the 4th one went trough so it was a 75% failure and 1 went trough. The first time I did the lab all 4 failed but after pining again everthing went properly so I assume I configured everything well there too but the ARP requests made all 4 ping attempts to fail.
@@hzakaria5338 I looked into it further, arp requests will vary depending on how you set the static address (ip address mask next hop address or ip address mask interface) so I assume that is why my 2 labs varied in amount of packets recieved on first ping (100% loss during first lab and 75% loss on second lab). In my first attempt doing the lab I set one of the statics in R2 to interface and the other via next hop address, I also configured R1 to have R2 as it's default route/gateway of last resort and the same for R3 for the sake of excercising the command. In my second lab I did things as shown in Jeremy's video. All of these factors must have influenced the amount of ARP requests and thus the difference in packet loss % during first ping attempt.
Day 11 Lab 1 was awesome! Thank you Jeremy!
thank you you are the first one let me understand the IP address how it works , keep going till CCIE
A Perfect UA-cam tutorial
I followed the instructions for this lab, however the final steps were not same as showed in the lab, PC1 first failed to ping PC 2, after several attempts, it showed just 1 successful attempt, same was the case when PC2 tried to ping PC1. IS IT A PACKET TRACES ISSUE ?
This was a very challenging lab. It was great!
Nice, glad you liked it :)
A clear explanation and nice material presentation!
Thank you Alexey!
Very Interesting Jeremy are your videos sufficient in getting CCNA certified
Currently the course isn't finished, so no. When it's complete, yes, I will cover all of the topics! But I recommend using multiple resourecs anyway.
Best videos for CCNA Classes
Wow, thank you!
the ping for pc1 to pc4 dosen't work I've checked my errors but still same request timed out
same here everything checks out tho
Jeremy. Do you have any advice on how should we approach the study process for CCNA. How did you approach your CCNA?
I was a total beginner to IT and networking, so I just picked a course and followed it as the instructor said. I used Neil Anderson's course on Udemy by the way, check it out!
@@JeremysITLab Thanks for your reply.
It's very good that you pointed at the lacks of CPT.
Will cisco add to CPT the missing basic features that exists in a real device?
Sorry I'm not sure what CPT is...I don't want to watch my video again to see what I said, can you tell me the timestamp in the video? Haha
@@JeremysITLab CTP is Cisco Packet Tracer ;) Anyway everything is fine. What you are doing is great. You just said for instance that the description (using the "description" command on an interface) is not reporting in the "Name" column when typing the "switch# sh ip status" command. Also when changing manually the speed and/or the duplex values, it still appears as auto when typing the "switch# sh ip status" command. Anyway it is not so serious. Thank you so much for all :)
i greatly appreciate your detailed explanations. i can almost declare, i will be a networking expert by three months from now
update?
I try doing the labs with no video at first and try not to watch the video, unless I am truly stumped. Luckily I did found my problem without the assistance of the video. I did do something wrong at first, which when doing the "ip route" command, it showed "inconsistent address" or something like that. I was wondering why and then I did a "?". I realized that I needed the network destination address and I put the Address of PC3 the first time. I did an extra of implementing the "enable secret" and "service password-encryption" as well. I like this style of learning with the Anki Flashcards. It allows me to go at my own pace, unlike what I did in college, where it felt rushed.
Great vids, thx. With your next course maybe name them as episodes. Seeing as I'm a month in and only on day 11 hehe
Great job Jeremy, keep up the good work.
Maybe this is a Packet Tracer bug but after following instructions twice I still could not ping PC2. Changing R2s route to the 192.168.1.0 network from the interface to the IP fixed this. So for anyone else having trouble, undo the route then fix it:
no ip route 192.168.1.0 255.255.255.0 g0/0
ip route 192.168.1.0 255.255.255.0 192.168.12.1
Thanks Jeremy!
Thanks for your time and efforts.
3:48 After the configuration, shouldn't we use the WRITE command to save all the changes?
If you are finished with the configurations, it's a good idea to save the config.
Hi Jeremy, I cant express how much I appreciate you putting this course together for us in the the networking IT community. I just have a quick question that I'm not so sure about. Around 9:48 min into the video (configuring Static Routes Day 11 Lab video), when configuring the static route to 192.168.1.0 255.255.255.0 g0/0, you choose to use the exit interface instead of
the next hop ip address. I wanted to ask, if we didn't indicate the exit interface, what would be the next hop address be instead? Thanks
It would be the IP address of R1's G0/0 interface, 192.168.12.1, since that is the next-hop on the path to the destination.
@@JeremysITLab Thanks a million Jeremy. I'll try this option when I get home as I continue with my studies. Thanks again.
if you cant ping to PC2, then adding this hop of 192.168.12.1 works perfect. was having trouble here lol.
thanks guys
Thanks so much, Sir really helpful God Bless you and keep you well
Thank you so much!
Excellent I have learned a lot here rather in school , are there any other videos coming up?
Yes, new video every week!
Thank u so much. Your tutorials are helping me a lot!
I love these short Lab videos. Sir can you please tell how can I download Anky cards.
You can get the flashcards from the top line of the description:
Free CCNA 200-301 flashcards/Packet Tracer labs for the course: jeremysitlab.com/youtube-join/
Great video from a great teacher, you make things look simple, I'd like to know how to get the packet tracer lab files tho as I can't find them in resources..
good lesson tryied it.experienced it.very helpful.
Love your videos!
Thanks :)
9:47 Here i have one problem g0/0 invalid input detected at ^ marker and why?
restart fix :v
The end scared me a bit, I actually paused and worked oon a large portion of this myself...then when we went to ping at the end I got 3 time outs before I got a reply.
I did everything exactly the same as shown in the video, except at 10:32 I configured "R2(config)#ip route 192.168.3.0 255.255.255.0 g0/1", then if I ping from either PCs it will time out at every ping. Is there a reason exit-interface can't be configured at both ends of a router, or is it just some packet tracer quirks? It works fine if I set R2 to route 192.168.3.0 using next-hop ip instead of exit-interface.
Thanks so much for this great Course. God Bless you and keep you well
I had a question please Why you don't use this IP route in R1?
R1# ip route 192.168.13.0 255.255.255.0 192.168.12.2
yeah same question
Good question! The requirement is that PC1 can ping PC2, and R1 doesn't need to know the route to the 192.168.13.0/24 network for that. R1 just needs to know that to reach 192.168.3.0/24, it should send the packet to R2.
Jeremy's IT Lab
Thank you so much 🌹
@@JeremysITLab Does this also apply for bigger networks? We were taught to always include the serial's network when routing. When is it okay to not include a route to the serial's network and when should you include it?
For those who are having proplem with the packet canoot reach its destination.
I solved this problem by deleting R2 and set it up again.
I hope it work with you.
Thank u Jeremy, your videos are very useful
Thank you :)
Thanks Jeremy and good luck!
Really Thank you!! it was clear to understand.. Perfect job sir
Hi Jeremy, what kind of routers and switches should I choose if I will be using a packet tracer? Thank you. :)
For these practice labs I make, just download the lab file from the link in the description. For making your own labs, any kind will work. I usually use 2911 routers and 2960 switches in my labs.
Thank you Jeremy; I made a few silly errors but learned from them, and in the end, it was spot-on.
Well done! Errors are great learning opportunities :)
Very useful course for CCNA ....
Thank you! :)
I have no idea what I've done wrong but I cannot get a ping response from PC1 to PC. Following through the ICMP traffic, I can see it gets as far as PC2, then on the reply it is getting stuck at the G0/1. I've double and triple checked the interface settings on the PCs and routers and all the static routes. ARP doesn't seem to get past R1 either which is weird. Any ideas?
Edit: I was able to sort it by adding in additional default routes:
R1 (config) #ip route 0.0.0.0 0.0.0.0 192.168.12.2
R3 (config) #ip route 0.0.0.0 0.0.0.0 192.168.13.2
R2 (config) #ip route 192.168.3.0 255.255.255.0 192.168.13.3
R2 (config) #ip route 192.168.1.0 255.255.255.0 192.168.12.1
I'm getting ping responses now. I think Packet Tracer was having a moment.
Thank you for this amazing course. I've been practicing since day 1
I was able to configure all the addresses correctly first try and without guidance :D
Pure and Simple Thank you for your subject matter expertise, we really appreciate your exceptional CCNA skills
Observation with packet tracer. I did the entire lab and the pings weren't working. I double checked up and down the config. After about 40 minutes of checking my work and comparing I restarted the lab from a clean starting point. On this next time through - the first time I pinged it timed out again... Then after looking but making no changes to any device in the chain I use the up arrow from the dos prompt and do the same command again - and it worked. I literally made no changes to any device. I'm not sure if that's a packet tracer thing or something else... but pack your patience when doing labs on it.
Packet tracer can be tricky, and it's hard to know if you did something wrong or packet tracer is the problem!
I initially had an issue with my first ping from PC1-PC3 and figured it had something to do with configuring the interface g0/0 for R2 dest: 192.168.1.0 and I went back Into the router and specified the IP to use for the interface and it worked immediately afterwards. I was thinking Jesus if this isn't the issue then im going to have go a mission in order to figure out where I went wrong!
excellent teaching skills
WOOHOOOO that worked! Im so happy!
Sir , how do you zoom the router terminal you are using in the packet tracer labs ???
You can change the font size in the packet tracer options!
Hello Jeremy, so I made the configurations once, and it did not send any ping, I remaked them twice, with opening new lab, and now it says Pinging 192.168.3.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.3.1: bytes=32 time=58ms TTL=125
Ping statistics for 192.168.3.1:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 58ms, Average = 58ms
I did the same specifics twice
P.S The only differences is on 1:32 in your programme says Gateway, on my programme says Default Gateway, Idk if it is a difference, but just saying!
Looks fine to me, the ping worked!
Hello, thank you for making these informative videos. I have been recently getting into computer technology and came across your channel. There is so much information to learn about computers/internet etc. and it can be overwhelming for someone like me but the way you simplify it and reiterate points of the lesson along with providing flashcards and packet tracer labs has made it easier for me to keep pursuing my new passion. I really appreciate it. On a side note, I had one question, how do you delete a static route from the ip table?
Thanks Joshua, I'm glad the videos are helping!
Deleting a static route is the same as deleting any configuration, put 'no' in front of the command.
For example:
Router(config)# no ip route 10.0.0.0 255.255.255.0 192.168.1.2
This command will remove the route.
Hi Jeremy. Have you noticed that ping from R1 to 192.168.3.1 is unreachable and from R3 to 192.168.1.1 is the same unreachable ? But from PC1 to PC2 and PC2 to PC1 is reachable. In my opinion this is weird and am not sure if this would work in real world. Any idea?
BTW great course so far.
It's not necessary for the router to be able to ping every single destination on the route to the destination. For example, your computer can access youtube's servers to watch this video, but it probably can't access every single router on the path to the youtube server!
Hi Jeremy, your course is quite better than paid courses on udemy. I want to ask you, how many videos are you going to totally make? And when? I want to do new ccna as soon as possible and your videos are the best. Thanks
Thank you! I think it will be a maximum of 50 'days', but since I don't have a lot of time to make videos it will take a while to finish the course. If you want to get your CCNA soon, I recommend using another course too, until I finished my course.
Thanks for your hard work , one question is bothering me , we usually never use switch at home because router does has some ports so how layer 2 works the without switch how it identify the mac address of connected devices.
Actually, a home 'router' isn't just a router, it's a multipurpose network device which functions like a router + switch + firewall + wireless access point. So, those ports you connect to on your home router are actually Layer 2 switch ports.
Jeremy's IT Lab thx for reply
Thank You very much !
Thank you for this great information. Much appreciated
Thank you for your comment!