From: Janto Cin (jantocin@datacomm.co.id)
Date: Fri Dec 13 2002 - 00:21:19 GMT-3
How about NTP?
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Coleman, Jason
Sent: Thursday, December 12, 2002 10:16 PM
To: 'Tran Tien Phong'; ccielab@groupstudy.com
Subject: RE: Why does broadcast still trigger the call?
What routing protocol are you running on this router?
Without the benefit of your entire config, I would guess that this is
likely
the source of you problem.
It is normally common practice to deny all routing protocol traffic as
interesting, and any traffic that you may use to monitor the router as
well.
On my ISDN configs, I always deny the routing protocol and SNMP.
Also, as a point of interest, given your dialer-list 1 protocol IP
permit
statement, CDP will never bring up or keep up the link since it is a
layer 2
protocol.
Jason Coleman - CCNP, CCDP
Customer Engineer
Network Management Center - Austin
(ph) 512-340-3134
(email) colemaj@netsolve.com
-----Original Message-----
From: Tran Tien Phong [mailto:PhongTT2@FPT.COM.VN]
Sent: Wednesday, December 11, 2002 10:51 PM
To: ccielab@groupstudy.com
Subject: Why does broadcast still trigger the call?
Hi guys,
When configuring DDR between 2 sites, I noticed that the broadcast still
triggered the call. The "show dialer" displayed: Dial reason: source:
x.x.x.x, destination: 255.255.255.255.
The interesting traffic was defined: dialer-group 1, dialer-list 1
protocol
ip permit
Also, I used the command "no ip directed-broadcast" and "no cdp enable"
at
both sides and no routing protocols running between two sides.
Anyone can tell me why broadcast packet still trigger the call and how
to
prevent this?
Thanks
Tran Tien Phong
.
.
.
This archive was generated by hypermail 2.1.4 : Fri Jan 17 2003 - 17:21:44 GMT-3