|
0:00:13
|
Now, filtering in EIGRP...
|
|
0:00:16
|
is gonna be similar to what we
|
|
0:00:19
|
where we could use standard
|
|
0:00:23
|
to match on what particular routes
|
|
0:00:27
|
or what we want to advertise out.
|
|
0:00:30
|
Where the extended access list is
|
|
0:00:34
|
but the source of the route.
|
|
0:00:37
|
Where again, the source of the
|
|
0:00:40
|
when we look at the Show IP Route
|
|
0:00:48
|
So here, we're looking at the
|
|
0:00:51
|
It says it is received from
|
|
0:00:57
|
which we see are related to
|
|
0:01:02
|
of the neighbors that we're
|
|
0:01:05
|
We'll see later in OSPF, the route source
|
|
0:01:13
|
So, if you're doing route source-based
|
|
0:01:18
|
whether it is the actual
|
|
0:01:22
|
or whether it is the ABR
|
|
0:01:25
|
that is generating the Type-3 LSA,
|
|
0:01:31
|
But in the case of EIGRP, we can see
|
|
0:01:36
|
So, whatever shows up here in the
|
|
0:01:40
|
that's gonna be the route source.
|
|
0:01:44
|
So, we could potentially say here,
|
|
0:01:50
|
loopback interface,
|
|
0:01:52
|
but I wanna only accept it from
|
|
0:01:55
|
So, I don't want it to come from this neighbor.
|
|
0:01:58
|
So on router 4, we could create
|
|
0:02:05
|
If we Show Access List.
|
|
0:02:08
|
Access List 100...
|
|
0:02:11
|
is going to deny the route source of
|
|
0:02:26
|
Then, we will Permit Anything Else.
|
|
0:02:31
|
Then, under the EIGRP process,
|
|
0:02:36
|
or Distribute List 100 In.
|
|
0:02:41
|
Or we could apply this to a particular link.
|
|
0:02:44
|
In this case where we're
|
|
0:02:47
|
it's going to apply to all interfaces.
|
|
0:02:50
|
Then, if we were to look at the result of this,
|
|
0:02:53
|
we should see...
|
|
0:02:56
|
once the routers recalculate the topology,
|
|
0:03:00
|
we now are only learning
|
|
0:03:04
|
from the point-to-point link
|
|
0:03:07
|
We're no longer learning it over the frame-relay,
|
|
0:03:10
|
because when we look at the access list,
|
|
0:03:13
|
we're filtering out that particular route.
|
|
0:03:16
|
So, when it is coming from this
|
|
0:03:24
|
Again, the limitation of this just like in RIP
|
|
0:03:27
|
is that both the extended
|
|
0:03:30
|
they can match on the route, but they cannot
|
|
0:03:36
|
So, any case where we're doing summarization,
|
|
0:03:40
|
or subnetting, or we're trying to
|
|
0:03:44
|
two routes that have the same address
|
|
0:03:49
|
standard or extended access list would not
|
|
0:03:53
|
So, the ideal implementation for route
|
|
0:03:58
|
because the syntax is specifically
|
|
0:04:03
|
where with an access list, whether
|
|
0:04:07
|
mainly, those are meant for
|
|
0:04:11
|
So, if we want to filter out FTP traffic,
|
|
0:04:14
|
or we wanna filter out UDP
|
|
0:04:19
|
Whereas the prefix list is mainly
|
|
0:04:22
|
Now, similar to RIP, we could
|
|
0:04:28
|
and the distance for filtering,
|
|
0:04:32
|
where the offset list could be used to increase
|
|
0:04:39
|
Syntax is gonna be very similar
|
|
0:04:42
|
in the access list what particular
|
|
0:04:46
|
what's the metric value that we will offset it
|
|
0:04:53
|
Only main difference between RIP is that the maximum
|
|
0:05:01
|
So, if we look at simply the question
|
|
0:05:06
|
if router 4...
|
|
0:05:08
|
were to say Offset List 0 for all network in,
|
|
0:05:16
|
then, this maximum value...
|
|
0:05:21
|
So, what is this? 2.1 billion.
|
|
0:05:25
|
If we offset a network to this value,
|
|
0:05:28
|
the metric becomes infinite, and then,
|
|
0:05:33
|
Then likewise, we could say "in an interface, out
|
|
0:05:38
|
An additional route filtering
|
|
0:05:42
|
that the other protocols do not
|
|
0:05:45
|
are filtering with a route map
|
|
0:05:51
|
Now, we know that when we are
|
|
0:05:54
|
like from RIP to OSPF,
|
|
0:05:58
|
we can control what particular
|
|
0:06:02
|
by filtering them through a route map.
|
|
0:06:05
|
However, with normal IGP implementations,
|
|
0:06:11
|
or to the process itself.
|
|
0:06:15
|
Filtering with route maps most of
|
|
0:06:18
|
or it's applied on a per-neighbor basis
|
|
0:06:21
|
to control what prefixes we want to
|
|
0:06:25
|
and also if we want to modify
|
|
0:06:30
|
But with EIGRP, we can use
|
|
0:06:35
|
or a filter based on
|
|
0:06:38
|
So, let's say in our case...
|
|
0:06:41
|
on switch 1,
|
|
0:06:44
|
we're gonna create another loopback
|
|
0:06:51
|
When I do this, I'm gonna
|
|
0:06:53
|
So, I'll set the tag to be 7.
|
|
0:06:58
|
Then, on router 6, I'll say,
|
|
0:07:03
|
I'm not going to accept any
|
|
0:07:07
|
So first, on switch 1, let's
|
|
0:07:11
|
We'll say, "Loopback 7
|
|
0:07:19
|
Under the EIGRP process, we'll
|
|
0:07:24
|
and we'll send it to the
|
|
0:07:30
|
Where Route Map Set
|
|
0:07:35
|
So, whatever metric value we want.
|
|
0:07:38
|
And set the tag to be 7.
|
|
0:07:43
|
So now, if we were to go to
|
|
0:07:47
|
and look in the routing table,
|
|
0:07:53
|
we see that the prefixes,
|
|
0:07:56
|
and it has a tag of number 7.
|
|
0:08:02
|
Now, on router 6, we can create
|
|
0:08:08
|
that will say Deny...
|
|
0:08:11
|
Sequence 10.
|
|
0:08:13
|
Any routes that match
|
|
0:08:18
|
Then, we will Permit Anything Else.
|
|
0:08:24
|
Now, we'll see, the key difference
|
|
0:08:28
|
in IGP versus BGP, or versus
|
|
0:08:34
|
is that under the EIGRP process,
|
|
0:08:37
|
we will say, Distribute List Route Map.
|
|
0:08:42
|
The Route Map is the tag filter.
|
|
0:08:47
|
And this is going to apply in on...
|
|
0:08:53
|
Fast Ethernet 0/0.67. Fa 0/0.67.
|
|
0:09:02
|
So now, if we look at the
|
|
0:09:09
|
we'll see that once we
|
|
0:09:12
|
this route is not gonna be
|
|
0:09:19
|
Where we could see now, it's changed
|
|
0:09:25
|
So, even though the metric is higher on
|
|
0:09:33
|
versus 2800,
|
|
0:09:35
|
since we're filtering the tag value on this link,
|
|
0:09:39
|
then, this route cannot be installed
|
|
0:09:44
|
Now, this feature can also be
|
|
0:09:48
|
If you simply look for EIGRP
|
|
0:09:55
|
you'll see some examples
|
|
0:10:01
|
It says, "How to configure...
|
|
0:10:04
|
EIGRP suppport for route map filtering."
|
|
0:10:09
|
And let's look at the
|
|
0:10:13
|
where they're saying match
|
|
0:10:17
|
So, not only can we
|
|
0:10:22
|
but we can say, what's
|
|
0:10:25
|
So, if it came from BGP.
|
|
0:10:27
|
And if the metric is
|
|
0:10:33
|
So, 500 plus or minus a hundred.
|
|
0:10:35
|
Now, for outbound filtering in EIGRP,
|
|
0:10:38
|
it's essentially the same thing
|
|
0:10:41
|
We could use the access
|
|
0:10:43
|
we could offset a route so that it
|
|
0:10:49
|
As we talked about before, if we set
|
|
0:10:54
|
it's not only going to be a route filter,
|
|
0:10:57
|
but it would also be an adjacency filter.
|
|
0:11:00
|
So, we cannot establish adjacencies
|
|
0:11:05
|
Then, likewise, the route map that we just
|
|
0:11:10
|
either based on the metric value
|