From: Bill Dellamar (wdellamar@xxxxxxxxx)
Date: Sun Nov 05 2000 - 18:21:19 GMT-3
Cliff,
I believe the answer is this:
Promiscous is listen only - meaning that it will
accept connections from unconfigured remote-peers, but
not inititate connections to unconfigured
remote-peers, except to those that are explictity
defined in a remote-peer statement.
Whereas, peer-on-demand-defaults also has the ability
to initiate connections to unconfigured remote-peers.
--- Clifton Stewart <cliftonlstewart@home.com> wrote:
> Bill,
>
> I will set this up in the lab tonight but according
> to "Configuring
> Cisco Routers for Bridging, DLSw+ and Desktop
> Protocols" the border-peer
> method should limit explorer packet traffic. I will
> need to run some
> debugs to confirm this. Talk to you later.
>
> -Cliff
>
> P.S. Being dragged to Target with the family ;}
>
> Bill Dellamar wrote:
>
> > Cliff,
> > I pulled this from the cd docs. Notice how E1
> forms a
> > direct peer from W1. Therefore, connection
> requests
> > can be from anybody, not just the border peer.
> What
> > if it's a explorer issue. What if it only
> except's
> > explorer packets or responds to explorer packets
> from
> > the border peer.???
> > any thoughts?
> >
> > After configuring border peers and peer groups,
> the
> > same fully meshed connectivity is possible without
> the
> > overhead. In the "after" network, two peer groups
> are
> > defined (West Group and East Group). Within each
> > group, one or more peers is configured as border
> > peers. Every peer within the West Group
> establishes a
> > peer connection with the west border peer (WBP).
> Every
> > peer within the East Group establishes a peer
> > connection with east border peer (EBP). The border
> > peers establish a peer connection with each other.
> > When a peer in the West Group wants to find a
> > resource, it sends a single explorer to its border
> > peer. The border peer forwards this explorer to
> every
> > peer in its group and to every other border peer.
> The
> > EBP, after receiving this explorer, forwards it to
> > every peer in its group. When the resource is
> found
> > (in this case at E1), a positive reply flows back
> to
> > the origin (W1) via the two border peers. At this
> > point, W1 establishes a direct peer connection to
> E1.
> > Peer connections that are established via border
> peers
> > without the benefit of preconfiguration are called
> > peer-on-demand connections. The rules for
> establishing
> > on-demand peers are defined in the dlsw
> > peer-on-demand-defaults tcp commands in each
> router.
> >
> > --- Clifton Stewart <cliftonlstewart@home.com>
> wrote:
> > > Hi Bill,
> > >
> > > What if the requirement was to ONLY accept
> > > connections from a
> > > border-peer?
> > >
> > > -Cliff
> > >
> > > Bill Dellamar wrote:
> > >
> > > > Could someone explain the difference between
> > > > promiscous and peer-on-demand-defaults.
> > > >
> > > > Promiscous - will accept connections without
> > > defining
> > > > remote-peers.
> > > >
> > > > Peer-on-demand-defaults - is a non-configured
> > > > remote-peer that was connected because of an
> LLC2
> > > > session established through a border peer
> DLSw+
> > > > network.
> > > >
> > > > Aren't these the same thing? Or won't
> promiscous
> > > > accept a connection from a border peer?
> > > >
> > > > Any input would be appreciated.
> > > > Thanks,
> > > > Bill
> > > >
> > > >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:42 GMT-3