HP3000-L Archives

October 1997, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jeff Kell <[log in to unmask]>
Reply To:
Date:
Sat, 11 Oct 1997 00:24:15 -0500
Content-Type:
text/plain
Parts/Attachments:
[HP3000-L] (28 lines)
Alan Ambers writes:
> Terry -
> If you have transparent bridging turned on to pass the
> DTC traffic, I would expect that the local DTC traffic
> will stay off the WAN since the router should know
> what port each MAC address comes from.
>
> For instance, I have a remote 56k frame relay site that
> I am routing IP and have transparent bridging turned on
> for IPX (for right now, that will be turned off later).

This is a matter of scaling.  As I recall, Terry's original question
regarded a cisco router which *can* filter by protocol type in the IP
header.  Blind (transparent) bridging can cause all sorts of trouble
when you're looking at anything but small networks.  IPX, Appletalk,
broadcasts (ARPs, RIPs, SAPs) and a number of other "features", like
the newer versions of JetAdmin drivers and managers which secretly do
background pings/SNMP queries of every address on your network looking
for JetDirect devices.  That's fine for a class C network, but if you
have a class B address, or an "internal" A or B network, that is a
boatload of traffic.

Plain bridging *will* work for DTCs; but efficient?  As your bandwidth
demands increase, your decisions and implementation will catch up with
you.

Jeff Kell <[log in to unmask]>

ATOM RSS1 RSS2