From: Rick Burts (burts@xxxxxxxxxxxxxx)
Date: Fri Jul 21 2000 - 21:19:32 GMT-3
uninteresting packets certainly do not reset the idle timer. EIGRP hello
will not keep the line up in this configuration.
Rick
On Sat, 22 Jul 2000, Walid Fahme wrote:
> Thanks Rick. I think you have a point. The Hello packets should establish
> neighbor relation once the link comes up again. But don't you think the
> hello packets will keep the link up ? Or uninteresting packets will not
> clear the idle timer ??????
>
> Ciao,
> Walid.
>
>
> Look more carefully at his example. His access list did not discard
> Hello packets, it merely made them uninteresting. If the link is
> down, Hello will not bring it up. If the link is up, hello will be
> exchanged and neighbor relationship will form and routes will be
> advertised.
>
> Rick
>
> On Fri, 21 Jul 2000, Bill Dicks wrote:
>
> > If you filter the Hellos, then how will the two routers become neighbors
> > unless the line is already up? If they don't become neighbors, how will
> > routing occur and routes be exchanged?
> >
> > I see you have the floating static, so if your link to the WAN goes down,
> > this will be the only route. BUT, since you are filtering eigrp, you will
> > never become neighbors with the other router on the other side of the ISDN
> > link and no routes will be exchanged. If you're going to use a floating
> > static, use 0.0.0.0 so that all traffic goes that way (assuming of course
> > that you have a normal 0.0.0.0 route when the WAN link is up). But without
> > Hellos, no neighbor and no routes.
> >
> > Bill
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> > Wojtek Iwanczyk
> > Sent: Friday, July 21, 2000 1:08 PM
> > To: aub95@emirates.net.ae; ccielab@groupstudy.com
> > Subject: Re: EIGRP over ISDN
> >
> > Here is a sample config of DDR using EIGRP ... Filter eigrp "helo s" with
> > the dialer list referencing an extended ip access list ...
> >
> >
> > interface Dialer0
> > description ISDN Dial-up to NY-PRI-BRI-Router
> > ip unnumbered Loopback0
> > no ip directed-broadcast
> > ip nat outside
> > encapsulation ppp
> > bandwidth 2
> > delay 6000
> > dialer remote-name Router1
> > dialer idle-timeout 90
> > dialer string xxxxxxxxxxxxxx
> > dialer string xxxxxxxxxxxxxx
> > dialer pool 1
> > dialer-group 1
> > pulse-time 0
> > ppp authentication chap callin
> > ppp chap hostname xxxxx
> > ppp chap password xxxxx
> >
> > router eigrp 1
> > network 172.31.0.0
> > no auto-summary
> >
> > ip route 172.31.0.0 255.255.0.0 Dialer0 240
> >
> >
> > access-list 160 deny udp any any eq snmp
> > access-list 160 deny eigrp any any
> > access-list 160 permit ip any any
> >
> > dialer-list 1 protocol ip list 160
> >
> > Wojtek Iwanczyk
> > Sr Support Engineer
> > Exenet Technologies
> > 15 E 26th Street
> > New York, NY 10010
> > (212) 684 7300
> > wiwanczyk@exenet.com
> >
> >
> > >>> Walid Fahme <aub95@emirates.net.ae> 07/21/00 01:14PM >>>
> > Question:
> >
> > To limit Distance Vector Protocol updates on a dialup link (ISDN) we
> > have several options (Snapshot, Watch-Group)
> >
> > To limit Link State OSPF updates ==> "ip ospf demand"
> >
> > What about EIGRP, any solution ???
> >
> > (Also, is there anything for IS-IS, NLSP and others ????)
> >
> > Appreciate your comments.
> >
> > Walid Fahme.
> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:56 GMT-3