🚀 go-pugleaf

We're in the process of improving campus connectivity by tossing an
AGS+ into the middle of things.  Problem right now is that several of
the departmental ethers which we are starring together use Appletalk.
Each department's Appletalk is its own problem, but they don't want
(yet) to talk to each other.  Since our previous topology and bridges
let us block it differently, and since the departments were autonomous
as far as Appletalk is concerned (the centre officially doesn't support
it), we have not centrally assigned Appletalk zones, and I'd bet they
are all using whatever is the default-as-shipped.

I'm aware that we could block it through all interfaces of the AGS+ by
using 'Administrative Filtering by Protocol Type', but somewhere in the
manual is a line suggesting that there is a performance hit on this,
'proportional to the number of entries in the type code access list'.
Cisco don't say what the constant of proportionality is, though.  If an
entry cost, say .001% of throughput, who cares?  If it costs 50% per
entry, ouch.

It looks, though, like it might be possible to win by telling the AGS+
to route Appletalk, and then setting 'no appletalk address' on all the
interfaces.  This sounds more elegant, and also would be more flexible
if we do need to handle inter-departmental Appletalk later.  Anyone
have any comments on this possibility?

-- 
Paul Smee, Computing Service, University of Bristol, Bristol BS8 1UD, UK
 P.Smee@bristol.ac.uk - ..!uunet!uknet!bsmail!p.smee - Tel +44 272 303132