From: adrian smith (adrian36@xxxxxxxxxxx)
Date: Sat May 20 2000 - 16:08:11 GMT-3
   
do you need to configure appletalk on R2?  if so, how about a tunnel between
R1 and R3.  i wonder if you could bridge across R2 as another altenative.
>From: "Gerard Robinson" <gerardrobinson@dial.pipex.com>
>Reply-To: "Gerard Robinson" <gerardrobinson@dial.pipex.com>
>To: <ccielab@groupstudy.com>
>Subject: Re: Appletalk filters
>Date: Sat, 20 May 2000 14:36:50 +0100
>
>
>     Does it really matter if users on R3 LAN can see the cable-range and
>zone on the R1-R2 WAN, if there are no Appletalk nodes on the WAN link
>which must be the case then what's the issue? just use a GZL filter on R3
>to block R2e0 zone or a cable-range filter to block R2e0 and then the zone
>won't appear anyway. Of course you could block R1-R2 cable-range from R3
>and then use a static route on R3 to get to R2.
>
>         BTW the question strikes me a being a typical CCIE lab question,
>can you confirm?
>   ----- Original Message -----
>   From: Earl Aboytes
>   To: ccielab@groupstudy.com
>   Sent: Saturday, May 20, 2000 10:51 AM
>   Subject: Appletalk filters
>
>
>   I have the following appletalk configuration
>
>
>
>   -----(e0)R1(s0)--------(s0)R2(e0)
>
>                                 |
>
>                                (s0)R3(t3/0)
>
>   I am being asked to put a filter on r3 such that it only sees routes and
>zones from r1.  Can anyone clarify what they are asking me here?  I dont
>think that it is a zip reply filter because I am being asked to put the
>filter directly on R3.  Its not a get zone list filter because they are not
>asking about end users.  I dont think a cable range filter would work
>because R1 and R2 share a cable range.  Can somebody help me?
>
>
>
>   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>   Earl Aboytes
>
>   Senior Technical Conultant
>
>   GTE Managed Solutions
>
>   805-381-8817
>
>   earl.aboytes@telops.gte.com
>
>   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:30 GMT-3