CCNA1 Packet Tracer 9.1.3 - Identifying MAC and IP Addresses

hello this is barrett from the c4 cyber club here at cypress college uh in this video we are going to cover the packet tracer lab 9.1.3 identifying mac and ip addresses so you can see in the first part we're going to gather pdu information for local area network communication so looking at the lab here essentially everything over here on this switch so this will be the the local network communication and then we're going to gather information for remote network communication so we'll be you know potentially going from one of these pcs whoops over to here through the router for remote network connection um [Music] so as you can see in the background all these devices are already configured they're ready to go but we're based basically going to be looking at viewing pdus and looking at ethernet frames ip headers as we ping these different systems so this lab it's it's essentially a lot of information gathering there's no configuration that needs to be done but as you can see here we're going to start off by pinging this device the dot 2 host from the dot 5 host we're going to check out the pdu of that by running in simulation mode so for the mo for most part in in the course you've been running in real time mode but simulation mode will allow us to look at the packets and the frames as they move across the network now important is this e section here so as we do this you want to record the pdu information you gathered into a spreadsheet so below is an example because we are going to be paying a few different times so you can see here we're going to ping [Music] this is all in the local and then down here in part 2 this is where we will start pinging to our remote network and we're going to have more more ip addresses to put down in a spreadsheet so if you see behind me here and i'll probably keep this document file outside of the screen for now but i would definitely recommend that you have this open as well to to refer to so now what i did is i created a google google sheet so i just logged into my google docs created a new spreadsheet so the way that i'm laying it out is very similar to what you saw on here so we have um at which device and this is going to make sense in a moment when we look at the pdus every pdu will tell you which device it's at you'll actually see a little envelope at each device as well and then within the pdu we'll find the destination mac the source mac the source ip address and the destination ip address well maybe not always because keep in mind on a switch that is a layer 2 device so you do not see layer 3 network layer ip address there and then coming down this would be the next set of pings that we do so we're pinging here from here pinging to this device from this device so you can see i kind of already got this started but then i stopped because i figured well i might as well document the process of also creating this as well for you so it's um it's definitely a different lab than what we've been doing it just requires a little bit of organization at the beginning and but once you have this table set up you should be good to go and it's fairly straightforward from there all right so the very first thing that we do want to do is we're going to ping this dot 2 host from the dot 5 host so when we click on the 172.16.31.5 we want to go to desktop and command prompt so remember this is where we do pings from so first let's let's look at how we've usually been running packet tracer in real time mode so if you ping 172.16.31 oops 31.2 you see okay those those four pings went through pings 4 by default so that's normal right so now let's switch to simulation mode and you notice a simulation panel opens up here and this is where we're going to see step by step how this data moves through the network okay so if we press up in the command prompt again it's going to bring that last ping command back press enter and now you see the command prompts hanging it's it's waiting because we need to now we can um forward these events as we wish so i'm actually just going to minimize this and you see an envelope here so this is the pdu so when we click on this let's let's break down what's happening here because you'd be looking at a lot of these um also real quick i wanted to mention because it will likely happen to me still but if you hover this over your packet tracer there's a very good chance you may accidentally drop it into here right so all you all you do to get it out is just click and drag it out so because you'll see how it's it becomes more handy if you open a little bit bigger so you can look at this information a little bit easier okay so once again we're looking at the pdu now we see that it's at this device it's at the dot five host which makes sense that's where we originated the ping from the source is that and then the destination of course is the dot 2 that we're pinging now here's where the osi layer model comes in handy you see we have seven layer options um but only three are available which makes sense um we're pinging from an ip address so we have the layer 3 network layer which deals with logical addressing in ips layer 2 the data link layer which deals with physical addressing mac addresses and then layer zero the actual port um that we're coming out of the the and also the the physical layer okay so now very important we move over to outbound pdu details and so this is where you see everything that module 7 i believe covers and we see up here the ethernet frame fields so this is on the data link layer we have the preamble sfd destination mac address source mac address type the data which remember can be anywhere from 64 to 1518 bytes and the frame check sequence so this is where it's doing error detection right remember and then down here we have the ip header so this is this is happening on layer 3 network layer and the most important fields here that you'll be looking at are source ip and destination ip so a reminder destination mac address source mac address because you see in the spreadsheet that's what we're going to be logging here and then of course the source ip and the destination ip okay good so now you know where you need to be looking and then again you'll also be logging the at device which will always be located either at the top here or right here because as this moves through the network this this will change okay so actually looking at this very first one you can see that it corresponds to what i've already logged here so we're at the dot five host the destination mac a zero zero c eight five cc 1da7 the source mac address is right here the source ip and then the destination ip is right here okay so now we can close this one so once you get that logged you're good to go and then we can come to the play controls and forward this to its next stop which is at the switch so when we open this up very first thing you can log down it's at device switch one now if you go to outbound and and notice that there is no layer 3 here and so this is actually why we we say um the source ip destination ip is actually n a because there is no ip at a a essentially a switch is a layer 2 device so we're mainly just looking at the destination mac address here which is right here and the source mac address which is right here all right now let's play controls again let's move to the next section and now we are at the hub and we can see here this is only working with layer one which makes sense remember from lectures a hub is a dumb device it's a layer one physical layer device it just sends everything out so we can actually probably imagine it's going to send this to both of these systems because they're both connected to the hub even though we do know that the destination is supposed to be here the hub does not know this it because it's a dumb device it does not know where this is supposed to go but it's just going to flood out of all of its ports so in this case we have n a on all these sections here okay and as we guessed it sent out to both and we notice this x the blinking x on the dot three host so i just noted in in my chart that that frame was dropped because it the dot three host received and said hey this is not for me so i'm just going to drop it so we can take a look at this pdu and now we see okay we're back we have up to layer three take a look at the outbound details and then go ahead and lock those as well so we have the destination mac right there the source mac address right here the source ip and then the destination ip so we notice that that these have swapped now because uh once it reached the destination all right so essentially the lab let me pull this back over it right so it asks for repeat this process until the pdu reaches its destination so at this point we can probably just switch this back to real time so now that we've switched back to real time mode we will ping the dot 2 host from the dot 3 host so the very first thing we want to do actually just to make sure that we don't get too much cluttered pdu information in the simulation mode when we open the command prompt we want to ping 172.16.31.2 so this is from the dot 3 host we're pinging the dot 2 host and this is just making sure it's doing all the like arp requests and stuff that we've been learning about because you don't want to be looking at too much information in the pdus for this a particular lab so now that we've done that now we can switch the simulation and actually i shouldn't have closed that we stay back in the 0.3 device and we're just going to ping again okay so now we have the simulation mode enabled so now we can take a look at this information so i'm going to move this back over here and we're going to start inputting this into our chart all right so we're at device 1.3 double check this the destination mac address okay add that down uh zero zero six zero for the source add that down the source ip address makes sense it's at that device and this is where we sent it to the dot 2. okay so let's go ahead and forward this all right we are now at the hub once again this is a dumb device a layer one device only so all of these are going to be not applicable okay so let's move that along all right we see it's splitting up because the hub remember it sends out of all of its ports and here we are getting a dropped packet so we can actually say switch one dropped oops i'm going to copy that i'm gonna make sure all these are centered there we go now down here we could say okay it is at device 31.2 this is our destination taking a look at the outbound all right so you can actually um copy from here and then we can paste it in here no maybe not no didn't want to do that for me okay okay what sorry for the confusion too i was using colons up here just just so there's no confusion you can also use the periods that is okay okay dot two eight four nine okay so that is the destination here we have the source mac address yep see i knew it would happen so if that happens you could just click and drag it right back out it's the the tricky thing with this lab is just getting it formatted properly okay here we go zero zero zero c dot 85 one d cc.1da seven okay and now we see the source ip so now that we're at the destination this this flips this swaps right all right so that should be it for this one because we have reached the destination so we can let's swap back to real time mode now we are pinging the dot4 host from the dot 5. so i'm just going to copy this so i get my coloring and i'm just going to alter this so we're going to ping the dot 4 host from the dot 5 host okay and then i'm going to go ahead and copy this line as well so feel free to follow my lead on the layout i think it'll it'll definitely come in handy once we get to the questions all right so now we want to click on the dot 5 go to command prompt remember stay in real time mode with this first ping so ping 172.16 all right so now that that has gone through let's go ahead and turn simulation mode back on and remember you could just press the up arrow to bring that ping command back okay so now we're now we're in business here to minimize that so we know that we are at device 172.16.31.5 i'm going to go ahead and open this up outbound pdu details okay destination mac we have it right here so that's zero zero zero c c f zero b b c eighty now the source let me move this over here i can see there we go zero zero d0 d3 11 c788 and now down here in the ip header we have the ip address the source ip and then the destination ip all rights we're good with this pdu let's go ahead and forward it along goes to the switch all right so remember the switch um is only a layer 2 device no layer 3 so the source ip and destination ip will be not applicable we are at switch one device now let's take a look at the pdu and whoops there we go again and we notice it's it's the same it's exactly the same so i'm actually going to copy and paste that down there okay great moving along and now we have reached our destination 172.16.31.4 all right the destination mac address zero zero d0 dot b311.c788 and the source zero zero zero c c f zero b b bc80 and then down here in the ip header source ip172.16.31.4 because we're at the destination now so we have a swap all right so i th pretty sure that completes the local network let's take a look let me bring the lab over okay so we did this um so it says return real-time mode we'll go ahead and do that yeah so now we're in part two gathering pdu information for the remote network communication and so the first thing we're going to do so we're going to ping from the dot 5 host all the way over to this laptop all right so let's go ahead and do this first ping in real-time mode 10 about 10.10.2 probably taking a second because it needs to do an arp request likely why we saw that request timed out it was it was waiting um until it got that arp request back and now we see that all those tables have likely been updated and so now we will have a much cleaner communication once we switch the simulation mode here all right so let's go ahead and run that again now that we swapped the simulation and we can minimize this as we travel along with this pdu all right so let's let's get our chart updated here so we are pinging 10.10.10.2 from actually this from is exactly the same so i'm going to bring that down here set my color okay and i'm gonna pull this row down here all right so we are at device dot five host and let's take a look at this pdu all right outbound details destination mac address zero zero d0 ba 8e 7418 these are all showing up bold aren't they there we go and the source right down here remember uh zero zero d zero d three eleven oop didn't have my caps lock on d311 c788 and the source ip of course this is where we're sending it from and the destination ip is 10.10.10.2 all right now we move on to the switch so we are at switch one as we can probably gather the source and destination i should say the destination that comes first the destination and source are exactly the same again and not applicable on ip because that is a layer 2 device all right let's keep moving alright so now we reach the router so type out router for at device okay destination mac 0 0 6 0 dot 2 f 8 4 4 a b 6 the source is over here gosh zero zero d zero five eight eight c two four zero one and i p all right so we can close this one let's go ahead and move it along so now it comes to switch zero open this pdu once again no layer three so no ip needs to be logged and we're taking a look at the destination mac zero zero six zero two f eight four four a b six zero zero d zero 588c so it's exactly as it was up above and then n a and a now we go to the wireless access point and this is you know very similar to a hub so this is a layer 1 device so we are actually going to say n a not applicable on all fields so access points and a copy that okay and now we see that it it broadcasts that to all devices on the network on the the access point and the dot three of course drops it because it's not intended for it so we we could log that i'm not sure if the questions actually get into anything that's dropped but it can't hurt to log it okay and now we're at device 10.10.10.2 take a look at this okay so you notice that the pdu fields are a bit different because we're looking at a wireless connection coming from this this laptop the address 3 is going to be your destination mac and the address 2 is going to be your source mac and you can actually kind of figure this out by looking at the router so you know that the destination has to be the source of the router so this is the router's mac address here so of course um address three here this is the destination this is where it needs to send back to and then we determined that this is the source mac address as well because this was the destination from the router so we can actually copy from here and these get swapped so i know that one's probably a little tricky um but yeah with that this is and this is why it's important to take this a step at a time think about um the way that these pdus travel and determining all the different mac addresses for all these different devices so now finally all we have to do log is the ip i wish there was a way to lock it so it cannot drop in there maybe there is okay so 10.10.10.2 on the source ip 172.16.31.5 for the destination because it is getting ready to send back to that destination but at this point for the lab we're going to stop now that we've reached the destination all right let's see do we have any more on the remote i think that is it okay cool so let me go ahead and change this to real time so an answer of this one here what device has the destination mac that is shown and i believe that's referring to once it reaches the destination so what device has this destination mac well remember we were just talking about it that is the router so this is is going to be sending back to the router because it needs to communicate back to this device okay so now let's go ahead and take a look at these reflection questions now that we've gathered all of this information so number one were there different types of cables or media used to connect devices so we could think about that by looking at the packet tracer topology i see mostly copper connections here but all obviously wireless down from the the access point here so we're looking at copper and wireless um you could potentially look at let's say if we look at the router now i see that there the router has fiber capability but if we let's see if we hover over here it's actually using the fast ethernet zero zero so it's actually using copper here so say there is fiber possibility but it's we're looking like we're only seeing copper and wireless so did the cables change the handling of the pdu in any way no no no change did the hub lose any information that it received we didn't notice that remember we we logged when things were dropped so here we see the hub received and it's sent to the dot three host but it dropped the packet um because it wasn't the correct recipient but that is not the same thing as lost right the hub still sent the packet as it's meant to do so the answer to this would be no it didn't lose any information um when what does the hub do with mac address and ip addresses this is kind of a trick question because remember hubs are dumb devices and they they don't operate at layer two layer three levels so the answer to that is pretty much nothing right uh what did i'm sorry did the wireless access point do anything with the information given to it so yes remember when we were looking down here once the access point forwarded to this laptop remember we were looking at the fields and they were it didn't specifically say source ip or i'm sorry source mac or destination mac and we kind of had to do some thinking to figure out which was which and we made it made sense that okay it's sent from the router so this would be the destination and then the source would be where the router was sending to so the router's destination so essentially it was repackaged in those wireless 802.11 standard frames because it's working through a wireless adapter here okay was any mac or ip address lost during the wire transfer no we don't recall seeing any any loss uh what was the highest osi layer that the hub and access point used so remember keep saying this hub and and the access point they're dumb devices and they are only layer 1 devices so layer 1 is the highest layer that they have access to okay so did the hub or access point ever replicate a pdu that was rejected with a red x yes we did see that we did see replication okay when examining the pdu details which mac address appeared first the source or the destination so i remember i remember pointing this out at one point the destination mac will always appear first and so leading into question 10 why would the mac address appear in this order well especially if you're using something like cut through forwarding where it looks for the destination mac address first and then just forwards it along so that's that's a good way that's a way to have faster forwarding keep in mind it's not always the the best solution but in general even if you're doing store and forward it looking at the destination mac address first allows it to move more quickly to its destination all right and was there a pattern to the mac addresses in the simulation so if we look at our charts not necessarily i would essentially the answer to this is no there's no specific pattern happening did the switches ever replicate a pdu that was rejected with an x no the switches did not replicate any of the pdus with the x every time that the pdu was sent between the 10 network and the 172 network there was a point where the mac address suddenly changed so where did this occur so we're talking about the remote the remote connection test so we're looking down here so when did the mac address suddenly change so you can see here we're working with the same mac addresses and then it was at the router right so we see the source mac address is now the router besides that we're just dealing we've just been dealing with the sender and the receiving mac addresses but now because it reaches the router the frames get updated with the router's mac address and because the router has its mac table updated it knows the mac address of 10.10.10.2 so that's where we see the destination mac is now this so to answer this question where did that occur that occurred at the router and so which device uses mac addresses that start with zero zero d0ba let's pull that up here okay so this is the destination mac coming from the sending device so this must also be the router because it knows okay in order for me to get to here i need to send to the router so it sends it through the switch to the router so that is the device here the router and what devices did the other mac addresses belong to i mentioned it up above pretty much the only other mac addresses that we are looking at through here is the sending device like 172.16.31.5 and the receiving device 10.10.10.1.2 sorry so yeah sender and receiver did the sending and receiving ipv4 addresses change fields in any of the pdus ah no we did not notice any changed fields when you follow the reply to a ping sometimes called a pong do you see the sending and receiving ipv4 addresses switch so yeah absolutely and [Music] this is kind of related to this next question so i guess this would be yes and then what is the pattern to the ipv4 addressing used in the simulation and so we could see here how the ip addresses get swapped so once it once it reaches the destination down here the source and the destination ips swap okay so why do different ip networks need to be assigned to different ports of a router well essentially you know the function of a router is to interconnect different ip networks so you need to have different ports to connect two different networks right and then finally if this simulation was configured with ipv6 instead of ipv4 what would be different essentially nothing except for instead of these ipv4 addresses we would have ipv6 addresses so that you know the mac addressing would be the same the communication would be the same you would just have ipv6 instead of ipv4 so that concludes this lab the packet tracer 9.1.3 identifying mac and ip addresses [Music] so just a reminder i would make sure you save your sheets you may need to potentially turn this in for the assignment as well and also make sure that you filled these out while we while we went over them so okay great thanks a lot for watching

Channel: Cypress College Cyber Club C4

Views: 5,026

Keywords: ccna1, cisco, packet tracer, packet tracer 9.1.3, cisco networking, mac address, ip address, cypress college, c4cyberclub

Id: 1gS1NrZxTB4

Length: 44min 11sec (2651 seconds)

Published: Sat Oct 24 2020