WEBVTT

0:00:02.920000 --> 0:00:09.160000
 Hello and welcome to this video titled
 dynamic ARP inspection demonstration.

0:00:09.160000 --> 0:00:10.740000
 And that's what I'm
 going to be doing.

0:00:10.740000 --> 0:00:14.360000
 I'm going to be giving you a live demonstration
 of how dynamic ARP inspection

0:00:14.360000 --> 0:00:16.820000
 works in a lab environment.

0:00:16.820000 --> 0:00:19.800000
 So let's just go right into that.

0:00:19.800000 --> 0:00:23.260000
 So here is our topology
 for this demonstration.

0:00:23.260000 --> 0:00:26.280000
 I have two DHCP clients.

0:00:26.280000 --> 0:00:29.700000
 In this particular case, I have
 routers fulfilling those roles.

0:00:29.700000 --> 0:00:35.140000
 Each router is configured for IP address
 DHCP on their various interfaces.

0:00:35.140000 --> 0:00:38.460000
 So client R1 and client R3.

0:00:38.460000 --> 0:00:41.600000
 I also have a default gateway that
 they're going to be using, which is

0:00:41.600000 --> 0:00:45.280000
 router 2. He has a static
 IP address configured.

0:00:45.280000 --> 0:00:50.100000
 And then we have DHCP snooping
 currently running on switch 2.

0:00:50.100000 --> 0:00:53.060000
 So if we look in switch 2 right here,
 we can see in the DHCP snooping

0:00:53.060000 --> 0:00:59.980000
 binding table, we have been allocated
 to those various different clients.

0:00:59.980000 --> 0:01:06.020000
 So without dynamic ARP inspection turned
 on, I can go for example to one

0:01:06.020000 --> 0:01:07.840000
 of those clients.

0:01:07.840000 --> 0:01:10.680000
 And I should be able to
 ping as default gateway.

0:01:10.680000 --> 0:01:15.960000
 Yep. And I should be able to go to the
 other client and ping the default

0:01:15.960000 --> 0:01:28.360000
 gateway. Great. All right.

0:01:28.360000 --> 0:01:31.520000
 IP ARP inspection VLAN 123.

0:01:31.520000 --> 0:01:34.980000
 So all the devices are in
 VLAN 123 in this case.

0:01:34.980000 --> 0:01:36.840000
 Now let's just leave it
 there for the moment.

0:01:36.840000 --> 0:01:44.160000
 Now because these two clients are already
 in the DHCP snooping binding

0:01:44.160000 --> 0:01:46.880000
 database, they should be
 able to ping each other.

0:01:46.880000 --> 0:01:50.400000
 In other words, they should be able
 to ARP for each other because they

0:01:50.400000 --> 0:01:54.440000
 will be coming in on untrusted interfaces,
 but they can be validated by

0:01:54.440000 --> 0:01:57.300000
 switch 2. Let's check that out.

0:01:57.300000 --> 0:02:05.160000
 So for example, let's go to the first
 client, show IP interface brief.

0:02:05.160000 --> 0:02:09.700000
 This guy is 1113, so we know
 the other guy must be 1114.

0:02:09.700000 --> 0:02:12.040000
 So let's ping 1114.

0:02:12.040000 --> 0:02:20.100000
 And we can. And look, show IP ARP,
 we can see the ARP was successful.

0:02:20.100000 --> 0:02:23.280000
 We did successfully ARP for 1114.

0:02:23.280000 --> 0:02:25.560000
 Now I'm going to clear out the
 ARP in just a moment here.

0:02:25.560000 --> 0:02:30.020000
 Clear IP ARP. Let's get rid of the
 ARP for the default gateway.

0:02:30.020000 --> 0:02:41.700000
 OK. So he currently has an ARP entry
 for himself, which never ages out.

0:02:41.700000 --> 0:02:45.040000
 And he has an ARP entry
 for the other PC.

0:02:45.040000 --> 0:02:48.200000
 But let's see if he's able to ARP
 for his default gateway now.

0:02:48.200000 --> 0:02:53.640000
 Debug IP ARP. Actually,
 it's just debug ARP.

0:02:53.640000 --> 0:03:04.180000
 PING 1111. OK. So he's sending an ARP
 request source of 1113, destination

0:03:04.180000 --> 0:03:07.940000
 of 1111. But he doesn't
 know the MAC address.

0:03:07.940000 --> 0:03:11.620000
 And notice, we never
 got a reply back.

0:03:11.620000 --> 0:03:16.140000
 Now, did that ARP request make
 its way to the router?

0:03:16.140000 --> 0:03:22.220000
 Let's find out. Let's go
 over here to that router.

0:03:22.220000 --> 0:03:25.580000
 Let's send our debugging output
 to the logging buffer.

0:03:25.580000 --> 0:03:28.700000
 So logging buffer debug.

0:03:28.700000 --> 0:03:36.020000
 Debug ARP. Clear that log.

0:03:36.020000 --> 0:03:39.280000
 And let's try it again
 from the same client.

0:03:39.280000 --> 0:03:40.860000
 Try pinging the default gateway.

0:03:40.860000 --> 0:03:43.040000
 So he's ARPing for him right now.

0:03:43.040000 --> 0:03:47.420000
 OK. So are those ARPs making
 it over there to router 2?

0:03:47.420000 --> 0:03:56.020000
 Yes. See that? Received request from
 1113, sending reply from 111.

0:03:56.020000 --> 0:03:58.780000
 So why is the reply
 not getting there?

0:03:58.780000 --> 0:04:02.160000
 Well, if we go back to the switch where
 we just turned on dynamic ARP

0:04:02.160000 --> 0:04:05.600000
 inspection, our syslog message
 just tell you why.

0:04:05.600000 --> 0:04:10.020000
 Dynamic ARP inspection,
 DHCP snooping, deny.

0:04:10.020000 --> 0:04:18.360000
 Invalid ARP response
 on FastEthernet 0.10.

0:04:18.360000 --> 0:04:22.180000
 Which is leading to 1111.

0:04:22.180000 --> 0:04:24.720000
 It was unable to validate that.

0:04:24.720000 --> 0:04:27.280000
 It was unable to validate
 that packet.

0:04:27.280000 --> 0:04:31.980000
 So now in this particular case, the
 easiest thing to do would be to make

0:04:31.980000 --> 0:04:34.980000
 FastEthernet 0.10 a
 trusted interface.

0:04:34.980000 --> 0:04:44.180000
 Let's do that. Interface FastEthernet
 0.10, IP ARP inspection trust.

0:04:44.180000 --> 0:04:48.960000
 Now the client's ARP should be able
 to get there and more importantly,

0:04:48.960000 --> 0:04:53.900000
 the ARP response should be
 able to make its way back.

0:04:53.900000 --> 0:05:03.100000
 There we go. Received reply from 1111
 and now our ARPs are perfectly fine.

0:05:03.100000 --> 0:05:07.900000
 Alternatively, because FastEthernet
 0.10 in this case does lead upstream

0:05:07.900000 --> 0:05:13.320000
 to another switch, making it a trusted
 interface on switch 2 is potentially

0:05:13.320000 --> 0:05:18.620000
 problematic because ARP attacks could now
 come from switch 1 going downstream

0:05:18.620000 --> 0:05:23.160000
 to switch 2. And if that interface is
 trusted, we have no way of validating

0:05:23.160000 --> 0:05:29.340000
 them. So now let's go back to switch
 2, go back to that same interface,

0:05:29.340000 --> 0:05:32.300000
 remove that command.

0:05:32.300000 --> 0:05:37.940000
 OK. Now let's create
 an ARP access list.

0:05:37.940000 --> 0:05:40.460000
 Now for an ARP access list, we're going
 to need two pieces of information

0:05:40.460000 --> 0:05:41.300000
 from the router.

0:05:41.300000 --> 0:05:45.180000
 We've already got one piece,
 which is his IP address.

0:05:45.180000 --> 0:05:47.780000
 We need his MAC address as well.

0:05:47.780000 --> 0:05:56.640000
 All right. So let's go ahead and
 capture that in a text file.

0:05:56.640000 --> 0:06:04.480000
 So his MAC address is this.

0:06:04.480000 --> 0:06:09.240000
 All right. So we'll
 just keep that.

0:06:09.240000 --> 0:06:11.100000
 We'll put that down here.

0:06:11.100000 --> 0:06:14.780000
 Now let's go back to our switch.

0:06:14.780000 --> 0:06:18.400000
 And we'll configure
 an ARP access list.

0:06:18.400000 --> 0:06:25.840000
 IP ARP actually is just
 ARP access dash list.

0:06:25.840000 --> 0:06:28.840000
 We'll just call it gateway.

0:06:28.840000 --> 0:06:39.000000
 And then we'll say permit
 IP host 1111 MAC host.

0:06:39.000000 --> 0:06:42.920000
 And then we'll paste
 this back in there.

0:06:42.920000 --> 0:06:50.240000
 All right. So there is
 our ARP access list.

0:06:50.240000 --> 0:06:54.740000
 Now lastly, we need to tell dynamic
 ARP inspection to reference that ARP

0:06:54.740000 --> 0:07:03.700000
 access list. So IP ARP inspection
 filter gateway.

0:07:03.700000 --> 0:07:06.840000
 We want to apply it
 on VLANs 1, 2, 3.

0:07:06.840000 --> 0:07:11.260000
 Now if we use the static command, that
 would say don't even look at the

0:07:11.260000 --> 0:07:13.140000
 DHCP snooping binding database.

0:07:13.140000 --> 0:07:16.820000
 But we do. We want him to use both
 the DHCP snooping binding database

0:07:16.820000 --> 0:07:19.640000
 and this ARP access list.

0:07:19.640000 --> 0:07:22.440000
 So we will not put the keyword
 of static in there.

0:07:22.440000 --> 0:07:30.100000
 So now if we take a look, if we do
 show run interface fast ethernet 0

0:07:30.100000 --> 0:07:36.560000
 slash 10, notice that it's trusted
 upstream for DHCP snooping.

0:07:36.560000 --> 0:07:41.540000
 But there's no mention of it being trusted
 upstream for dynamic ARP inspection.

0:07:41.540000 --> 0:07:44.960000
 So what we just did right there is we
 checked this interface right here

0:07:44.960000 --> 0:07:47.520000
 that leads to the router.

0:07:47.520000 --> 0:07:54.000000
 So right now for dynamic ARP inspection,
 it is untrusted, which normally

0:07:54.000000 --> 0:08:01.540000
 would mean that when this guy sends an
 ARP reply, that it would be dropped.

0:08:01.540000 --> 0:08:08.620000
 But because we configured the ARP access
 list, it will not be dropped.

0:08:08.620000 --> 0:08:11.260000
 Let's take a look at that.

0:08:11.260000 --> 0:08:19.040000
 So here is dynamic ARP inspection, and
 we're telling it to reference the

0:08:19.040000 --> 0:08:22.420000
 access list called gateway.

0:08:22.420000 --> 0:08:25.800000
 And that access list is going to be
 weighed out the bottom beneath all

0:08:25.800000 --> 0:08:27.660000
 of our physical interfaces.

0:08:27.660000 --> 0:08:33.900000
 There it is. Permitting that specific
 host and MAC address.

0:08:33.900000 --> 0:08:37.800000
 So if we configured that correctly,
 now when I go to my client again,

0:08:37.800000 --> 0:08:46.240000
 I do clear IP ARP
 1111, show IP ARP.

0:08:46.240000 --> 0:08:52.940000
 Notice that the moment I did clear
 IP ARP, now this is a router.

0:08:52.940000 --> 0:08:55.440000
 So a regular host
 would not do this.

0:08:55.440000 --> 0:09:01.160000
 But the moment I did this, the router
 on its own sent an ARP saying, hey,

0:09:01.160000 --> 0:09:02.720000
 1111, I lost your MAC address.

0:09:02.720000 --> 0:09:04.760000
 Can you please tell
 me what it is again?

0:09:04.760000 --> 0:09:11.580000
 And sure enough, we receive an
 ARP reply from that router.

0:09:11.580000 --> 0:09:14.200000
 And so once again,
 we can ping him.

0:09:14.200000 --> 0:09:21.260000
 So that concludes this live demonstration
 of dynamic ARP inspection.

0:09:21.260000 --> 0:09:21.960000
 Thank you for watching.

