From: John Underhill (stepnwlf@magma.ca)
Date: Thu Nov 27 2003 - 14:01:41 GMT-3
They both will work, the difference being the control mechanism added with
the acl. As far as keeping the dialer up, is the dialer side set as the STP
root? On global or interface, assign a higher priority, ex. bridge-group 1
priority 100.. Are the peers passive, promiscuous, on demand, or active? Set
a low keepalive number on local peer statements, and extend the timeout on
remote peer statements so that the session doesn't timeout while the circuit
initializes, and a keepalive value that is lower then the dialer idle time
should keep the circuit up..
dlsw local-peer peer-id 10.1.1.1 keepalive 10
dlsw remote-peer 0 tcp timeout 500
int dia0
dialer idle-time 90
----- Original Message -----
From: "Bob Sinclair" <bsin@cox.net>
To: "William Chen" <kwchen@netvigator.com>; <ccielab@groupstudy.com>
Sent: Thursday, November 27, 2003 10:51 AM
Subject: Re: Transparent Bridging over DDR
> William,
>
> Good question! Seems either should work. If you post your configs
perhaps
> someone can spot the issue you are having.
>
>
> -Bob Sinclair
> CCIE #10427, CISSP, MCSE
> bsinclair@netmasterclass.net
>
>
> ----- Original Message -----
> From: "William Chen" <kwchen@netvigator.com>
> To: "Bob Sinclair" <bsin@cox.net>; <ccielab@groupstudy.com>
> Sent: Thursday, November 27, 2003 10:41 AM
> Subject: Re: Transparent Bridging over DDR
>
>
> > Hi Bob,
> >
> > What is the different between "dialer-list 1 protocol bridge permit"
> > with "dialer-list 1 protocol bridge list 201 AND access-list 201 permit
> > 0x0000 0xFFFF".
> >
> > -- William Chen
> >
> > ----- Original Message -----
> > From: "Bob Sinclair" <bsin@cox.net>
> > To: "William Chen" <kwchen@netvigator.com>; <ccielab@groupstudy.com>
> > Sent: Thursday, November 27, 2003 10:34 PM
> > Subject: Re: Transparent Bridging over DDR
> >
> >
> > > William,
> > >
> > > There are some good example configs on CCO regarding bridging over
ISDN.
> > > Here is the relevant portion from one of them: Apparently you need to
> > > permit all protocol types:
> > >
> > >
> > > interface BRI0
> > > description ISDN TO ROUTER2
> > > encapsulation ppp
> > > dialer map bridge name ROUTER2 speed 56 5773756
> > > dialer-group 1
> > > bridge-group 1
> > > isdn spid1 0177104130 7710413
> > > ppp authentication chap
> > > !
> > > dialer-list 1 list 101
> > > !
> > > bridge 1 protocol ieee
> > > !
> > > ! Permit all bridged packets
> > > access-list 201 permit 0x0000 0xFFFF
> > > !
> > > dialer-list 1 LIST 201
> > >
> > >
> > >
> > > -Bob Sinclair
> > > CCIE #10427, CISSP, MCSE
> > > bsinclair@netmasterclass.net
> > >
> > >
> > > ----- Original Message -----
> > > From: "William Chen" <kwchen@netvigator.com>
> > > To: <ccielab@groupstudy.com>
> > > Sent: Thursday, November 27, 2003 4:27 AM
> > > Subject: Transparent Bridging over DDR
> > >
> > >
> > > > Dear Group,
> > > >
> > > > I try to understand the running transparent briding over DDR. If
I
> > want
> > > to make the spanning tree BPDU as the interesting packet to keep the
> dial
> > > interface up, what should I do?
> > > >
> > > > I found that just by the command "dialer-list 1 protocol bridge
> permit"
> > > will not preventing the line from idle. What is the transparent bridge
> > > packets includes actually?
> > > >
> > > > Best Regards,
> > > > William Chen
> > > >
> > > >
> _______________________________________________________________________
> > > > Please help support GroupStudy by purchasing your study materials
> from:
> > > > http://shop.groupstudy.com
> > > >
> > > > Subscription information may be found at:
> > > > http://www.groupstudy.com/list/CCIELab.html
> > >
> > >
This archive was generated by hypermail 2.1.4 : Fri Dec 12 2003 - 12:29:18 GMT-3