ECTED]
Subject: Re: Neighbor distribute-list command w/ Extended ACL [7:47272]
Hello Charles,
Sorry to do this to you, but I still have one more e.g. that I'm not too
sure (I found this on CCO) :(
access-list 101 permit ip 131.108.0.0 0.0.0.0 255.255.255.0 0.0.0.0
In this line, I understand that
MAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> Hunt Lee
> Sent: Tuesday, June 25, 2002 4:58 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Neighbor distribute-list command w/ Extended ACL [7:47272]
>
>
> Hi Charles,
>
> Thanks so much for your explanation. I underst
Hunt,
Simply put, a distribute list simply has an ACL associated with it (in
your example it's an extended ACL).
Traffic inbound from the peered router (120.23.4.1) has extended ACL
applied to it.
You are probably familiar of defining ACL's and applying it on an
interface. In this example yo
0.0.255.255 255.255.0.0 0.0.255.255
denies the VLSM networks under the /16.
Charles
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Dain Deutschman
Sent: Sunday, June 23, 2002 9:05 PM
To: [EMAIL PROTECTED]
Subject: Re: Neighbor distribute-list command w
It's kind of wierd. The source portion of the access list defines the
network whose updates are permited/denied...no suprise...the wierd part is
that the destination portion specifies the subnet mask of that network. So,
in your example;
access-list 100 permit ip 192.108.0.0 0.0.0.0 255.255.0.0 0
5 matches
Mail list logo
