WEBVTT

0:00:08.000000 --> 0:00:13.060000
 So I've talked about in theory what an
 access list is that's an identification

0:00:13.060000 --> 0:00:15.460000
 or classification tool.

0:00:15.460000 --> 0:00:18.400000
 I've talked about it at a real high level
 that there's things called numbered

0:00:18.400000 --> 0:00:21.560000
 and named access lists, although we haven't
 really looked at how to configure

0:00:21.560000 --> 0:00:26.060000
 them yet. And I've talked about how at
 a high level there's a differences

0:00:26.060000 --> 0:00:29.000000
 between a standard and
 extended access list.

0:00:29.000000 --> 0:00:32.220000
 Now we're going to go into more details
 about standard access list, what

0:00:32.220000 --> 0:00:35.880000
 they can do, what they can't
 do, how to configure them.

0:00:35.880000 --> 0:00:39.280000
 And then just for demonstration purposes,
 I'm going to pair a standard

0:00:39.280000 --> 0:00:43.300000
 access list with a feature, a security
 feature called an access group

0:00:43.300000 --> 0:00:46.500000
 feature, so you can see how
 the two work together.

0:00:46.500000 --> 0:00:53.060000
 So a standard access list, probably the
 most basic and simple of the access

0:00:53.060000 --> 0:00:57.260000
 list you can configure identifies traffic
 simply based on the layer three

0:00:57.260000 --> 0:01:00.520000
 header. So if you have anything you
 want to match other than the layer

0:01:00.520000 --> 0:01:04.160000
 three header, this is
 not the tool for you.

0:01:04.160000 --> 0:01:08.820000
 Within the layer three header, the only
 thing it can match on is the source

0:01:08.820000 --> 0:01:10.960000
 IP address, and that's it.

0:01:10.960000 --> 0:01:13.540000
 So once again, if you want to match
 on anything other than this, like

0:01:13.540000 --> 0:01:17.160000
 the destination of where the packet's
 going, or something else in the

0:01:17.160000 --> 0:01:20.520000
 IP header, this is not
 the tool for you.

0:01:20.520000 --> 0:01:24.900000
 So when you're configuring a standard
 access list, if you're going to

0:01:24.900000 --> 0:01:29.160000
 be using a numbered access list, the
 number should be in the range from

0:01:29.160000 --> 0:01:31.140000
 one to ninety nine.

0:01:31.140000 --> 0:01:33.760000
 In other words, at the global configuration
 level, we're going to see

0:01:33.760000 --> 0:01:37.620000
 this in just a moment, you're going
 to type access dash list, and then

0:01:37.620000 --> 0:01:38.880000
 you're going to give it a number.

0:01:38.880000 --> 0:01:43.720000
 If the number you give it is in this
 range, iOS knows, okay, what follows

0:01:43.720000 --> 0:01:48.960000
 next is I can only, I should say this,
 when iOS sees a number in this

0:01:48.960000 --> 0:01:53.180000
 range, it says, okay, now after this,
 the only options I'm going to give

0:01:53.180000 --> 0:01:57.200000
 the user, the network admin who's configuring
 me, is the option to match

0:01:57.200000 --> 0:02:01.620000
 on the source IP address and a
 wildcard mask, and that's it.

0:02:01.620000 --> 0:02:07.060000
 Now there's also an extended range, what
 I should say in an extended range

0:02:07.060000 --> 0:02:11.920000
 of numbers, because for most people,
 because remember with access list,

0:02:11.920000 --> 0:02:15.980000
 for example, one, that is the name of
 the container, I could have multiple

0:02:15.980000 --> 0:02:20.900000
 lines of that, access list one, match
 on this, access list one, match

0:02:20.900000 --> 0:02:23.660000
 on that, access list one,
 match on something else.

0:02:23.660000 --> 0:02:27.980000
 So I could have dozens or even hundreds
 of access control entries all

0:02:27.980000 --> 0:02:35.600000
 numbered one. Now, for most companies,
 this range here is more than enough.

0:02:35.600000 --> 0:02:40.040000
 But sometimes when you're talking about
 internet service providers, their

0:02:40.040000 --> 0:02:45.040000
 access list can be huge, because they've
 got thousands of companies that

0:02:45.040000 --> 0:02:48.680000
 they're servicing, and they need to
 have different access lists for each

0:02:48.680000 --> 0:02:53.060000
 one, and so they might run out
 of them even from one to 99.

0:02:53.060000 --> 0:02:57.540000
 So there is an expanded range of standard
 ACLs, and you should probably

0:02:57.540000 --> 0:03:04.000000
 memorize this number, from 1,300, I'll
 write this down here, from 1,300

0:03:04.000000 --> 0:03:13.860000
 through 1,999. So same thing, if you're
 configuring your access list as

0:03:13.860000 --> 0:03:21.900000
 a numbered access list, 1,301,
 or access dash list 1,400.

0:03:21.900000 --> 0:03:26.080000
 Anything in this range, it's as if you
 were using the numbers 1 through

0:03:26.080000 --> 0:03:31.840000
 99. iOS still recognizes that what
 you want is a standard access list.

0:03:31.840000 --> 0:03:41.460000
 Standard access list should be applied
 closest to the destination.

0:03:41.460000 --> 0:03:42.740000
 What does that mean?

0:03:42.740000 --> 0:03:45.180000
 We'll take a look at that
 in just a moment.

0:03:45.180000 --> 0:03:48.460000
 And there's no method to check the destination
 address or port numbers,

0:03:48.460000 --> 0:03:52.580000
 because all the standard access list
 checks is a source IP address.

0:03:52.580000 --> 0:03:56.240000
 That's it. Now, a lot of times,
 that's all you need to check.

0:03:56.240000 --> 0:03:59.080000
 You know, based on the feature that you're
 using, maybe you say, you know

0:03:59.080000 --> 0:04:01.720000
 what, all I care about is where
 this packet's coming from.

0:04:01.720000 --> 0:04:05.180000
 I could care less about where it's going
 to or anything else like that.

0:04:05.180000 --> 0:04:10.240000
 So here's how you would configure
 a standard access list.

0:04:10.240000 --> 0:04:12.320000
 So notice a few very important
 things here.

0:04:12.320000 --> 0:04:17.500000
 Number one, where are we doing it
 at the global configuration level?

0:04:17.500000 --> 0:04:19.760000
 So that's very important.

0:04:19.760000 --> 0:04:24.920000
 Number two, so we say
 access dash list.

0:04:24.920000 --> 0:04:27.920000
 We provide a number that's
 in the standard range.

0:04:27.920000 --> 0:04:30.760000
 And then you have to
 say permit or deny.

0:04:30.760000 --> 0:04:35.160000
 Now remember, permit or deny, we don't
 know what that's going to do.

0:04:35.160000 --> 0:04:38.060000
 If we're talking about an encryption
 feature that's using this, that means

0:04:38.060000 --> 0:04:41.540000
 permit the packet to be encrypted
 or deny it to be encrypted.

0:04:41.540000 --> 0:04:45.200000
 If we're using the access group feature,
 which is what I'm I'm going to

0:04:45.200000 --> 0:04:48.700000
 be using for my demonstrations, permit
 means allow the packet through

0:04:48.700000 --> 0:04:52.300000
 deny means kill the packet
 deny it block it.

0:04:52.300000 --> 0:04:59.280000
 And then we specify some 32 bit number
 as our source address and then

0:04:59.280000 --> 0:05:00.980000
 a wildcard mask.

0:05:00.980000 --> 0:05:09.400000
 Now to verify what we've configured,
 we can do show IP access list.

0:05:09.400000 --> 0:05:11.080000
 And they'll show us
 our access list.

0:05:11.080000 --> 0:05:14.720000
 Now that's not going to show you what
 feature or features because you'd

0:05:14.720000 --> 0:05:18.140000
 have more than one that are using this
 access list for identification

0:05:18.140000 --> 0:05:21.280000
 purposes. But it will show you the
 access list that you've configured

0:05:21.280000 --> 0:05:23.640000
 or you can do show run.

0:05:23.640000 --> 0:05:27.880000
 And you can use the pipe
 symbol on your keyboard.

0:05:27.880000 --> 0:05:32.840000
 And then I and C that's short for include
 access dash list, or you can

0:05:32.840000 --> 0:05:34.860000
 just look at show run.

0:05:34.860000 --> 0:05:38.180000
 Now in order to actually use an access
 list for something, because if

0:05:38.180000 --> 0:05:40.720000
 you just configure this access list
 and sitting at global configuration

0:05:40.720000 --> 0:05:43.740000
 level, it's not doing anything.

0:05:43.740000 --> 0:05:44.800000
 Here's an example.

0:05:44.800000 --> 0:05:48.300000
 Remember back when we were talking
 about switching and I said, if you

0:05:48.300000 --> 0:05:52.420000
 want to create a VLAN and have some
 hosts on your switch use that VLAN,

0:05:52.420000 --> 0:05:54.240000
 I said it was a two step process.

0:05:54.240000 --> 0:05:58.980000
 I said the global configuration level,
 you typed VLAN five or VLAN 100.

0:05:58.980000 --> 0:06:03.300000
 And then you had to go to the interface
 and say switch port access VLAN

0:06:03.300000 --> 0:06:06.140000
 five or switch port
 access VLAN 100.

0:06:06.140000 --> 0:06:11.580000
 Well, on a switch, if I just configured
 VLAN five and nothing else, that's

0:06:11.580000 --> 0:06:15.000000
 a broadcast domain that isn't really
 being used for anything.

0:06:15.000000 --> 0:06:15.960000
 Same thing here.

0:06:15.960000 --> 0:06:19.000000
 If I configure my access list, I don't
 have a feature that's referencing

0:06:19.000000 --> 0:06:22.080000
 it. It's just taking up space
 in my running config.

0:06:22.080000 --> 0:06:24.120000
 It's not doing anything.

0:06:24.120000 --> 0:06:29.240000
 So one of the first features that you
 learn in the CCNA level that uses

0:06:29.240000 --> 0:06:34.260000
 access lists is something called
 the IP access group feature.

0:06:34.260000 --> 0:06:37.960000
 Now this is an interface
 level feature.

0:06:37.960000 --> 0:06:41.680000
 It's a security feature and it's like
 it says you're a primitive firewall.

0:06:41.680000 --> 0:06:45.900000
 Basically, it's using the access list
 to determine if a packet matches

0:06:45.900000 --> 0:06:49.240000
 a permit statement, allow
 the packet through.

0:06:49.240000 --> 0:06:57.420000
 If any statement, filter
 it, drop it.

0:06:57.420000 --> 0:06:59.440000
 An IP access group is directional.


0:06:59.440000 --> 0:07:02.420000
 So when you apply it to an interface,
 you have to specify, am I looking

0:07:02.420000 --> 0:07:07.000000
 at traffic coming in that's coming
 in off the cable or am I looking at

0:07:07.000000 --> 0:07:10.380000
 traffic that's going out that I'm
 about to put onto the cable?

0:07:10.380000 --> 0:07:12.860000
 You have to specify
 directionality.

0:07:12.860000 --> 0:07:14.700000
 And then it references
 an access list.

0:07:14.700000 --> 0:07:18.200000
 Either it could be a named access list
 or a numbered access list for the

0:07:18.200000 --> 0:07:21.620000
 identification or classification
 purposes.

0:07:21.620000 --> 0:07:25.120000
 And so here's an example of
 how you would apply it.

0:07:25.120000 --> 0:07:30.760000
 So notice that we are at the interface
 level and you would say IP access

0:07:30.760000 --> 0:07:35.060000
 dash group and then you reference your
 access list like IP access dash

0:07:35.060000 --> 0:07:40.000000
 group one or access dash group two
 and then you specify your direction

0:07:40.000000 --> 0:07:45.800000
 in or out. Now one thing that's important
 about the IP access dash group

0:07:45.800000 --> 0:07:51.240000
 feature is you can only have it
 in one direction per protocol.

0:07:51.240000 --> 0:07:52.660000
 What do I mean by that?

0:07:52.660000 --> 0:07:58.360000
 Well, for example, I could say IP, let's
 put a little hash symbols here,

0:07:58.360000 --> 0:08:16.360000
 IP access dash group four.

0:08:16.360000 --> 0:08:22.440000
 Let me get rid of some of this
 stuff group eight out.

0:08:22.440000 --> 0:08:27.640000
 So right now, if a packet comes, we
 don't know what this interface is,

0:08:27.640000 --> 0:08:29.020000
 let's just put something here.

0:08:29.020000 --> 0:08:34.500000
 Let's say it's fast ethernet
 zero slash zero.

0:08:34.500000 --> 0:08:41.380000
 Okay, so if a packet comes in fast
 ethernet zero slash zero, I'm going

0:08:41.380000 --> 0:08:44.620000
 to stop and I'm going to inspect that
 packet against my standard access

0:08:44.620000 --> 0:08:47.220000
 list number four.

0:08:47.220000 --> 0:08:50.760000
 If there's a line in access list four
 and access control entry that says

0:08:50.760000 --> 0:08:53.080000
 deny, I'm going to
 drop the packet.

0:08:53.080000 --> 0:08:56.660000
 If there's a line in my standard access
 list that says permit that matches

0:08:56.660000 --> 0:08:58.500000
 this packet, I'm going
 to fold it through.

0:08:58.500000 --> 0:09:00.840000
 I'm going to let it
 into my device.

0:09:00.840000 --> 0:09:05.260000
 Now, if there's a packet that came in
 some other interface, fast ethernet

0:09:05.260000 --> 0:09:08.640000
 one one or a serial interface and my
 router has decided needs to route

0:09:08.640000 --> 0:09:12.040000
 it out fast ethernet zero zero.

0:09:12.040000 --> 0:09:16.300000
 Well, then it's going to look at access
 list eight to make that decision.

0:09:16.300000 --> 0:09:23.500000
 Now, let's say I come back later
 and I say IP access dash group.

0:09:23.500000 --> 0:09:28.300000
 Let's say seven in.

0:09:28.300000 --> 0:09:35.120000
 Then guess what, it's going to delete
 this line, because I can only have

0:09:35.120000 --> 0:09:38.260000
 one inbound and one outbound.

0:09:38.260000 --> 0:09:42.280000
 So whatever the most recent one is
 that you typed in, it will override

0:09:42.280000 --> 0:09:46.020000
 what the previous one
 was that said inbound.

0:09:46.020000 --> 0:09:49.320000
 So let's play around with
 this a little bit.

0:09:49.320000 --> 0:09:55.820000
 So we're going to use this topology
 and I'm going to build this up from

0:09:55.820000 --> 0:09:59.080000
 the CCNA racks we
 have here at INE.

0:09:59.080000 --> 0:10:02.300000
 So if you're using our rack rental tokens,
 you could create this on your

0:10:02.300000 --> 0:10:07.360000
 own. And I thought about having this
 pre-built in advance, but then I

0:10:07.360000 --> 0:10:09.980000
 thought I could use this as a good
 learning tool for you guys.

0:10:09.980000 --> 0:10:17.080000
 So when I'm creating a topology from
 nothing, step number one is you have

0:10:17.080000 --> 0:10:20.500000
 to know what do I have to work with,
 what physical equipment do I have,

0:10:20.500000 --> 0:10:24.700000
 how is it physically cabled up, and I know
 that my physical topology supports

0:10:24.700000 --> 0:10:28.560000
 this. And how do I know that?

0:10:28.560000 --> 0:10:34.660000
 Well, because if you rent time on our
 CCNA CCNP racks, this is what the

0:10:34.660000 --> 0:10:35.960000
 land topology looks like.

0:10:35.960000 --> 0:10:38.520000
 This is every possible
 land connection.

0:10:38.520000 --> 0:10:43.760000
 And so you can see from this, I can derive
 all kinds of certain topologies.

0:10:43.760000 --> 0:10:48.780000
 So for example, I want to use my
 connection from R1 to switch one.

0:10:48.780000 --> 0:10:49.960000
 So that's right here.

0:10:49.960000 --> 0:10:51.540000
 I'm going to be using
 this connection.

0:10:51.540000 --> 0:10:53.100000
 This connection, I'm
 not going to use it.

0:10:53.100000 --> 0:10:54.520000
 So I'm just going to shut it down.


0:10:54.520000 --> 0:10:57.620000
 And so that is not even
 part of my topology.

0:10:57.620000 --> 0:11:01.460000
 I'm going to use this connection from
 R2 to switch one, which is right

0:11:01.460000 --> 0:11:05.880000
 here. Once again, even though R2 has
 a connection to switch two, I'm not

0:11:05.880000 --> 0:11:06.480000
 going to use it.

0:11:06.480000 --> 0:11:07.960000
 I'm going to shut it
 down, disable it.

0:11:07.960000 --> 0:11:10.620000
 So it's not even part
 of my diagram.

0:11:10.620000 --> 0:11:13.260000
 I'm going to use this connection
 from switch one to switch two.

0:11:13.260000 --> 0:11:17.620000
 I only need one connection for this
 lab I'm creating, zero slash 10.

0:11:17.620000 --> 0:11:20.300000
 So I'm going to use this
 one link right here.

0:11:20.300000 --> 0:11:22.240000
 I'm going to shut the
 other ones down.

0:11:22.240000 --> 0:11:28.600000
 So what I usually do is in this lab,
 I will disable interfaces that I

0:11:28.600000 --> 0:11:32.440000
 don't use, because I don't
 want them to distract me.

0:11:32.440000 --> 0:11:34.420000
 I don't want my traffic
 to go off in directions.

0:11:34.420000 --> 0:11:36.260000
 I don't can't foresee.

0:11:36.260000 --> 0:11:37.520000
 I can't predict.

0:11:37.520000 --> 0:11:42.100000
 And then I will only enable with the
 no shut command, those interfaces

0:11:42.100000 --> 0:11:44.860000
 are actually part of my topology.

0:11:44.860000 --> 0:11:47.980000
 So these numbers here in brown are
 the actual interfaces I'm going to

0:11:47.980000 --> 0:11:54.140000
 be using, like zero slash one,
 zero slash two, zero slash 10.

0:11:54.140000 --> 0:11:58.300000
 And anything that's not shown here,
 that's on this diagram is not being

0:11:58.300000 --> 0:12:03.180000
 used. For example, 13, 14,
 15, switch three entirely.

0:12:03.180000 --> 0:12:04.240000
 I'm not even using them.

0:12:04.240000 --> 0:12:07.360000
 So all these connections of
 switch three are disabled.

0:12:07.360000 --> 0:12:08.600000
 I'm not using it.

0:12:08.600000 --> 0:12:12.020000
 Now, once I've figured out from my
 physical topology, what interfaces

0:12:12.020000 --> 0:12:17.260000
 I want up and actually active and what
 interfaces are not relevant, then

0:12:17.260000 --> 0:12:20.520000
 the next thing is to figure
 out my IP addressing.

0:12:20.520000 --> 0:12:22.700000
 And so I just came up with
 some very easy addresses.

0:12:22.700000 --> 0:12:26.340000
 I sort of based it off of the interface
 off of the device names.

0:12:26.340000 --> 0:12:29.280000
 I figured, okay, router one connecting
 a switch one let's just have a

0:12:29.280000 --> 0:12:33.280000
 bunch of ones in the subnet switch one
 connecting a router to let's have

0:12:33.280000 --> 0:12:35.000000
 a combination of ones and twos.

0:12:35.000000 --> 0:12:37.600000
 So that's sort of how I came up with
 these subnets here that I'm going

0:12:37.600000 --> 0:12:47.640000
 to use. And then from my host bits,
 once again, I tried to make it MB

0:12:47.640000 --> 0:12:49.540000
 dot 22 for everything.

0:12:49.540000 --> 0:12:53.140000
 So that way my IP subnetting
 scheme is make sense to me.

0:12:53.140000 --> 0:12:56.560000
 And when I see these subnets in my various
 routing tables, I'll sort of

0:12:56.560000 --> 0:13:00.760000
 be able to visualize where they
 belong in my topology diagram.

0:13:00.760000 --> 0:13:05.640000
 Then what I do is once I have all this
 mapped out, this is a great exercise

0:13:05.640000 --> 0:13:11.080000
 for you in order to test your skills and
 your knowledge about have I memorized

0:13:11.080000 --> 0:13:14.640000
 the commands? Do I actually know
 the commands really well?

0:13:14.640000 --> 0:13:15.920000
 This is what I do.

0:13:15.920000 --> 0:13:20.900000
 I bring up a text editor
 like notepad.

0:13:20.900000 --> 0:13:24.460000
 Let me go to it.

0:13:24.460000 --> 0:13:29.000000
 And I will write out my configuration
 in the text editor from beginning

0:13:29.000000 --> 0:13:33.160000
 to end. Okay, I know I need to go into
 enable mode first, then config

0:13:33.160000 --> 0:13:35.420000
 T, I'll type in a host name.

0:13:35.420000 --> 0:13:40.600000
 So this is all the configuration that
 router one should need for this

0:13:40.600000 --> 0:13:43.860000
 topology. And then
 I'll scroll down.

0:13:43.860000 --> 0:13:47.360000
 And I'll make a configuration for
 the next device router two.

0:13:47.360000 --> 0:13:48.720000
 And then the next device.

0:13:48.720000 --> 0:13:53.880000
 So I'll write in text all the configuration
 I think I need for each device.

0:13:53.880000 --> 0:13:56.140000
 And then I'll copy
 and paste it in.

0:13:56.140000 --> 0:14:00.180000
 If I was right, if I didn't mess up
 any of my commands, I won't get any

0:14:00.180000 --> 0:14:02.420000
 error messages, and I'll be done.

0:14:02.420000 --> 0:14:06.400000
 If I get any error messages, then I'll
 know, oh, okay, I misspelled something

0:14:06.400000 --> 0:14:08.420000
 or I forgot a keyword.

0:14:08.420000 --> 0:14:13.100000
 And this is a great way for you to
 practice your knowledge of your iOS

0:14:13.100000 --> 0:14:14.740000
 command. So let's just
 go ahead and do it.

0:14:14.740000 --> 0:14:16.600000
 I haven't actually implemented
 any of this yet.

0:14:16.600000 --> 0:14:17.980000
 Hopefully all of it's right.

0:14:17.980000 --> 0:14:20.720000
 So let's go into router
 one and put this in.

0:14:20.720000 --> 0:14:29.100000
 Okay, I'll just right
 click and paste it in.

0:14:29.100000 --> 0:14:30.560000
 And everything looks good.

0:14:30.560000 --> 0:14:32.280000
 There were no error messages.

0:14:32.280000 --> 0:14:34.800000
 All right, save my configuration.

0:14:34.800000 --> 0:14:38.860000
 And let's repeat it
 now with router two.

0:14:38.860000 --> 0:14:49.940000
 Copy, paste. And we're
 done with him.

0:14:49.940000 --> 0:15:01.820000
 Now let's go to router three.

0:15:01.820000 --> 0:15:05.160000
 Okay, this guy clearly
 has a debug running.

0:15:05.160000 --> 0:15:10.320000
 Show debug. Otherwise, I would not
 have seen that I don't think.

0:15:10.320000 --> 0:15:13.040000
 Let's see. Yep, there's
 a debug running.

0:15:13.040000 --> 0:15:14.460000
 So how do I turn off all debug?

0:15:14.460000 --> 0:15:24.880000
 If I don't want to see
 a bunch of show debug.

0:15:24.880000 --> 0:15:26.640000
 Do you have anything
 running in you?

0:15:26.640000 --> 0:15:31.500000
 Nope, that's good.

0:15:31.500000 --> 0:15:40.620000
 Okay, and then my switches.

0:15:40.620000 --> 0:15:45.100000
 Now my switches, I'm configuring them
 a little bit differently than what

0:15:45.100000 --> 0:15:46.840000
 we've been dealing
 with in the videos.

0:15:46.840000 --> 0:15:52.800000
 In the videos, all of my physical interfaces
 were all always configured

0:15:52.800000 --> 0:15:58.960000
 as layer two switching ports as either
 switch port mode access or switch

0:15:58.960000 --> 0:16:04.000000
 port mode trunk or switch port
 mode dynamic something.

0:16:04.000000 --> 0:16:05.640000
 And you could certainly do that.

0:16:05.640000 --> 0:16:09.740000
 I could have elected to have three different
 VLANs because these are three

0:16:09.740000 --> 0:16:11.620000
 different broadcast domains.

0:16:11.620000 --> 0:16:14.940000
 And then I would have made these
 switch port mode access.

0:16:14.940000 --> 0:16:18.260000
 And then I would have needed to create
 a layer three switched virtual

0:16:18.260000 --> 0:16:23.620000
 interface like interface VLAN one interface
 VLAN two interface VLAN whatever.

0:16:23.620000 --> 0:16:26.020000
 But there's an alternative
 approach.

0:16:26.020000 --> 0:16:28.060000
 That's one way you could do it.

0:16:28.060000 --> 0:16:31.100000
 But on these switches, because these
 switches are multi layer switches

0:16:31.100000 --> 0:16:35.800000
 mean they can be routing, I can actually
 elect to convert their ports

0:16:35.800000 --> 0:16:41.300000
 from a layer two switching port like
 access or trunk into what's called

0:16:41.300000 --> 0:16:44.700000
 a routed port, which means it's
 like a port on a router.

0:16:44.700000 --> 0:16:49.020000
 You can slap an IP address on it
 and it's a layer three interface.

0:16:49.020000 --> 0:16:54.220000
 And you simply do that on switches by
 using the no switch port command.

0:16:54.220000 --> 0:16:58.160000
 When you type no switch port, then it
 allows you to put in an IP address

0:16:58.160000 --> 0:17:00.520000
 as if it was a port on a router.

0:17:00.520000 --> 0:17:04.540000
 And for me, this was easier because
 I didn't have to create VLANs.

0:17:04.540000 --> 0:17:11.560000
 I don't have to use the interface.


0:17:11.560000 --> 0:17:15.880000
 So let's go ahead and put that on there
 for a notice I'm using the interface

0:17:15.880000 --> 0:17:19.260000
 range command to shut down
 all of my interfaces first.

0:17:19.260000 --> 0:17:22.980000
 And then I selectively go into each
 interface say no switch port at an

0:17:22.980000 --> 0:17:26.440000
 IP address and then bring
 the interface up.

0:17:26.440000 --> 0:17:34.620000
 So my configurations for my switches
 are a little bit larger.

0:17:34.620000 --> 0:17:44.340000
 Ah, okay something wasn't right.

0:17:44.340000 --> 0:17:49.040000
 So right there I can tell it did
 not like the no auto summary.

0:17:49.040000 --> 0:17:50.360000
 Ah, okay so look at this.

0:17:50.360000 --> 0:17:52.160000
 So this is a great test.

0:17:52.160000 --> 0:18:00.660000
 So as you're doing this, if you see the
 so at first it looks like it didn't

0:18:00.660000 --> 0:18:04.800000
 like no auto summary but I think wait
 a second that's a valid command.

0:18:04.800000 --> 0:18:06.180000
 Why didn't it like that?

0:18:06.180000 --> 0:18:09.220000
 But look, we're at the global
 configuration level.

0:18:09.220000 --> 0:18:11.500000
 This is a rip command.

0:18:11.500000 --> 0:18:16.560000
 And then if I go up a little bit
 more, ah, IP routing not enabled.

0:18:16.560000 --> 0:18:22.940000
 So I forgot in my configuration, I should
 probably put in IP routing up

0:18:22.940000 --> 0:18:24.600000
 here towards the top.

0:18:24.600000 --> 0:18:29.800000
 And I should do that in switch two as
 well because he will need IP routing.

0:18:29.800000 --> 0:18:31.460000
 Actually that is switch two.

0:18:31.460000 --> 0:18:34.540000
 Let's do it up here
 and switch one.

0:18:34.540000 --> 0:18:36.840000
 Alright let's try copying.

0:18:36.840000 --> 0:18:40.420000
 I don't have to copy and paste the whole
 thing because a lot of the interfaces

0:18:40.420000 --> 0:18:44.740000
 already worked. So actually what I'll
 do is I'll just put IP routing right

0:18:44.740000 --> 0:18:51.340000
 here. And I'll take
 it out up here.

0:18:51.340000 --> 0:18:56.140000
 Okay because I previously did exit
 if I did copy and paste this whole

0:18:56.140000 --> 0:18:59.980000
 thing in again because I typed exit
 here at the interface level, I would

0:18:59.980000 --> 0:19:03.640000
 be back to global configuration level
 again and this command would work.

0:19:03.640000 --> 0:19:06.660000
 So this is all I'm going to
 copy and paste for now.

0:19:06.660000 --> 0:19:15.700000
 There we go. And now let's go into
 switch two and finish that off.

0:19:15.700000 --> 0:19:18.900000
 I know I could have started like I said
 with all this stuff pre-configured

0:19:18.900000 --> 0:19:21.500000
 and for those of you who are watching
 the video saying I wish you would

0:19:21.500000 --> 0:19:25.440000
 have done that, I'm sorry but I figured
 for those of you who might actually

0:19:25.440000 --> 0:19:30.700000
 be trying to build labs from scratch,
 this could be a useful example of

0:19:30.700000 --> 0:19:36.060000
 a way of doing that and practicing your
 memorization of iOS commands at

0:19:36.060000 --> 0:19:45.960000
 the same time. Okay so if everything's
 working correctly, router one now

0:19:45.960000 --> 0:19:53.320000
 should have a connected network and
 he should have one, two, three, four

0:19:53.320000 --> 0:19:57.580000
 routes that he learned via RIP,
 four rip routes, four subnets.

0:19:57.580000 --> 0:20:07.780000
 Let's find out. Show IP route.

0:20:07.780000 --> 0:20:11.560000
 There they are. They are
 all four rip routes.

0:20:11.560000 --> 0:20:14.920000
 So right now router one should be able
 all the way down to two dot four

0:20:14.920000 --> 0:20:17.540000
 dot two dot four.

0:20:17.540000 --> 0:20:24.240000
 And he can. Okay so now have
 end-to-end connectivity.

0:20:24.240000 --> 0:20:27.300000
 Let's practice my access list.

0:20:27.300000 --> 0:20:31.480000
 So we know that with a standard access
 list, all it can match on is the

0:20:31.480000 --> 0:20:35.840000
 source. So let's first of
 all write my objective.

0:20:35.840000 --> 0:20:38.380000
 So if you're creating a lab for yourself,
 you're building a lab from scratch,

0:20:38.380000 --> 0:20:41.880000
 you need to have a clearly defined idea
 of what is my objective of this

0:20:41.880000 --> 0:20:45.480000
 lab, what am I trying to test
 and how am I going to test it.

0:20:45.480000 --> 0:21:02.900000
 So objective, test, standard ACL feature
 and IP access dash group feature

0:21:02.900000 --> 0:21:04.180000
 and directionality.

0:21:04.180000 --> 0:21:08.360000
 Okay so how am I going to do it.

0:21:08.360000 --> 0:21:20.780000
 So my objective here is prevent IP packets
 sourced from R1 from pinging

0:21:20.780000 --> 0:21:29.900000
 R4. So my idea here is that I want R1
 to be able to ping everything but

0:21:29.900000 --> 0:21:31.620000
 R4. Now here's a problem.

0:21:31.620000 --> 0:21:36.140000
 I shouldn't say a problem but my challenge
 is that a standard access list,

0:21:36.140000 --> 0:21:38.200000
 I can't specify the direction.

0:21:38.200000 --> 0:21:41.000000
 I mean I can't specify
 the destination.

0:21:41.000000 --> 0:21:45.020000
 All I can specify in a standard
 access list is the source.

0:21:45.020000 --> 0:21:48.420000
 So that being the case.

0:21:48.420000 --> 0:21:57.140000
 Let's see here my access list should look
 something like this ACL configuration.

0:21:57.140000 --> 0:22:00.940000
 Access dash list and I'll just choose
 the number one because it's a standard

0:22:00.940000 --> 0:22:05.800000
 access list. Deny
 and I'll say host.

0:22:05.800000 --> 0:22:08.440000
 Actually let's do it
 with a wildcard mask.

0:22:08.440000 --> 0:22:13.860000
 1.1.1.1 and then what would the wildcard
 mask be to match all 32 bits

0:22:13.860000 --> 0:22:22.380000
 of that host. 000.0.0.0 or I could have
 said access dash list 1.deny host

0:22:22.380000 --> 0:22:26.760000
 1.1.1.1.1. That also
 would have worked.

0:22:26.760000 --> 0:22:30.200000
 And I need to put in a permit statement
 because if I don't that invisible

0:22:30.200000 --> 0:22:33.840000
 deny anything will
 kill everything.

0:22:33.840000 --> 0:22:38.700000
 So access dash list 1 permit any.

0:22:38.700000 --> 0:22:45.700000
 Okay now where now I have to use the
 access dash group command which will

0:22:45.700000 --> 0:22:54.340000
 be on some interface and I'll say IP
 access dash group 1 and then I'll

0:22:54.340000 --> 0:22:58.420000
 have to supply some sort of
 direction either in or out.

0:22:58.420000 --> 0:23:02.300000
 Now this is where we get
 back to that one slide.

0:23:02.300000 --> 0:23:09.920000
 If I go back this bullet point right
 here where it should access list

0:23:09.920000 --> 0:23:14.980000
 or standard access list should be applied
 nearest to the destination.

0:23:14.980000 --> 0:23:18.300000
 Here's where that is
 going to make sense.

0:23:18.300000 --> 0:23:28.240000
 If I took this IP access group and
 I put it let's say right here well

0:23:28.240000 --> 0:23:33.000000
 if I put it in the outbound
 direction would that work?

0:23:33.000000 --> 0:23:36.840000
 That'd be saying match packets
 going out this way.

0:23:36.840000 --> 0:23:40.240000
 Well is there ever any going to be
 any packet going out this way with

0:23:40.240000 --> 0:23:42.920000
 a source address that
 matches 1.1.1.1.1?

0:23:42.920000 --> 0:23:49.020000
 No destination yes but source
 address going this direction?

0:23:49.020000 --> 0:23:50.980000
 No that wouldn't make sense.

0:23:50.980000 --> 0:23:56.520000
 Okay what if I did it inbound
 on this interface?

0:23:56.520000 --> 0:24:02.660000
 Okay well that means a packet coming
 in that is a source address of 1

0:24:02.660000 --> 0:24:08.140000
.1.1.1.1 it'll be matched and it'll
 be dropped because the access group

0:24:08.140000 --> 0:24:14.560000
 feature says drop it but they'll
 drop everything from router 1.

0:24:14.560000 --> 0:24:18.520000
 My objective was not to drop router
 1 going everywhere my objective was

0:24:18.520000 --> 0:24:22.640000
 only if router 1 is trying to get to
 this guy down here should I drop

0:24:22.640000 --> 0:24:27.960000
 it and that's why a standard access
 list should be applied as close to

0:24:27.960000 --> 0:24:32.660000
 the destination as possible since you
 can't specify the destination well

0:24:32.660000 --> 0:24:39.860000
 you might think oh okay well then why
 don't I put it right here inbound?

0:24:39.860000 --> 0:24:43.100000
 Well here's the problem with that.


0:24:43.100000 --> 0:24:50.560000
 If you put it here router 4 he will actually
 look up that packet and process

0:24:50.560000 --> 0:24:55.660000
 it before he even looks
 at the access list.

0:24:55.660000 --> 0:25:00.140000
 So let's just imagine for a moment that
 the destination was not a router

0:25:00.140000 --> 0:25:04.760000
 but imagine this was a server right
 here that didn't support access list

0:25:04.760000 --> 0:25:08.120000
 because it's not a Cisco device it's
 a Windows server or a Linux server

0:25:08.120000 --> 0:25:13.320000
 well then in that case the closest we
 could get to the destination would

0:25:13.320000 --> 0:25:18.440000
 be right here on this and I would say
 doing it in the outbound direction

0:25:18.440000 --> 0:25:24.400000
 so if I go to switch to and I go to
 interface fast ethernet 0 slash 4

0:25:24.400000 --> 0:25:29.400000
 and I apply this command I put this
 access list on it on switch 2 and

0:25:29.400000 --> 0:25:32.880000
 then I put this command in the outbound
 direction let's see how that logic

0:25:32.880000 --> 0:25:38.100000
 is going to work so as r1 is pinging
 r4 no one's going to be looking at

0:25:38.100000 --> 0:25:41.580000
 his packets going to go all the way
 through switch 1 so he can ping r2

0:25:41.580000 --> 0:25:45.760000
 if he wants to he can ping any of the
 IP addresses on switch 1 if he wants

0:25:45.760000 --> 0:25:49.800000
 to because there's no access list here
 goes all the way down to switch

0:25:49.800000 --> 0:25:59.040000
 2 if r1 is trying to ping this dot 22
 or this dot 22 no problem but then

0:25:59.040000 --> 0:26:05.660000
 when it's routed out this interface
 if I have IP access dash group 1 out

0:26:05.660000 --> 0:26:11.180000
 he'll say hold on a second partner
 I got to look at that packet and so

0:26:11.180000 --> 0:26:16.680000
 if that packet matches 1 1 1 1 as a
 source he'll say I'm going to drop

0:26:16.680000 --> 0:26:23.680000
 it and so that will prevent router 1
 from pinging router 4 let's go ahead

0:26:23.680000 --> 0:26:31.880000
 and configure that on switch 2 just
 like it says access dash list and

0:26:31.880000 --> 0:26:36.620000
 I could pick any number in the standard
 range I'll just pick 1 people

0:26:36.620000 --> 0:26:44.300000
 usually start with the lowest number
 and I'll say deny host 1 1 1 1 or

0:26:44.300000 --> 0:26:50.740000
 an alternative to that would be 1 1
 1 1 and then a wildcard mask of all

0:26:50.740000 --> 0:26:58.640000
 zeros and then access dash list 1 permit
 I could put anything here it

0:26:58.640000 --> 0:27:03.900000
 doesn't really matter because that wildcard
 mask says I could have used

0:27:03.900000 --> 0:27:13.660000
 the word any let's see what happens actually
 here show run include access

0:27:13.660000 --> 0:27:21.880000
 dash list so look what it did my access
 list of 000 it actually took out

0:27:21.880000 --> 0:27:26.200000
 the wildcard mask I could have typed
 it in as host but it displays it

0:27:26.200000 --> 0:27:31.040000
 as this and this right here it said look
 that 32 bit number is meaningless

0:27:31.040000 --> 0:27:34.700000
 because you said any of the bits could
 match it it really doesn't matter

0:27:34.700000 --> 0:27:39.340000
 so that's the same thing as saying permit
 any and now I just need to apply

0:27:39.340000 --> 0:27:45.380000
 it so now on switch 2 I will go to interface
 fast ethernet 0 slash 4 and

0:27:45.380000 --> 0:27:51.580000
 I will insert my IP access dash group
 1 out command because I'm monitoring

0:27:51.580000 --> 0:27:58.760000
 packets going out onto the wire interface
 fast ethernet 0 slash 4 IP access

0:27:58.760000 --> 0:28:07.420000
 dash group 1 out all right so let's
 test it from router 1 I should be

0:28:07.420000 --> 0:28:11.100000
 able to ping router 2 because there's
 no access list on switch 1 so from

0:28:11.100000 --> 0:28:20.120000
 router 1 let's see if I can ping 1
 2 1 2 1 2 and I can from router 1 I

0:28:20.120000 --> 0:28:24.480000
 should be able to ping this address
 on switch 2 because it's coming in

0:28:24.480000 --> 0:28:29.520000
 this interface there's no inbound access
 list here there's no access group

0:28:29.520000 --> 0:28:32.280000
 supplied to either one of these interfaces
 so you should be able to ping

0:28:32.280000 --> 0:28:41.460000
 in and they get a reply back so from router
 1 let's ping 2.3.2.22 no problem

0:28:41.460000 --> 0:28:55.180000
 I should even be able to ping this
 if a packet tries to go out on this

0:28:55.180000 --> 0:29:00.220000
 wire with a source address of 1 1 1 1
 now the access group feature should

0:29:00.220000 --> 0:29:04.700000
 match that and it should be filtered
 or denied so I should not be able

0:29:04.700000 --> 0:29:14.680000
 to ping 2 4 2 and I cannot these use
 the reason I'm getting these use

0:29:14.680000 --> 0:29:25.940000
 here right here that is a result of receiving
 what's called ICMP unreachable

0:29:25.940000 --> 0:29:33.700000
 messages so I sent an ICMP echo request
 to 2424 it was blocked by the

0:29:33.700000 --> 0:29:37.560000
 switch who has the access list and the
 access group security feature and

0:29:37.560000 --> 0:29:42.080000
 the switch responded to me saying that
 is unreachable you can't get there

0:29:42.080000 --> 0:29:47.800000
 and that's what that is so that concludes
 this video on standard access

0:29:47.800000 --> 0:29:51.980000
 lists and pairing them up with the security
 feature known as the IP access

