You may want to know if RIP indeed does trigger the dialing. So, to answer your 2nd question, use the command "debug dialer packets" to give you a rundown if RIP is considered an interesting traffic. If RIP is triggering your ISDN, you'll see a debug output similar to the following:
07:34:30: BR0/0 DDR: ip (s=192.168.0.1, d=255.255.255.255), 52 bytes, outgoing interesting (ip PERMIT) OR 07:35:49: BR0/0 DDR: ip (s=192.168.0.1, d=224.0.0.9), 52 bytes, outgoing interesting (ip PERMIT) The first output is shown that RIPv1 is considered interesting and is responsible for bringing up the ISDN line. The second output is a simillar condition using RIPv2. Now, to block RIP, you will have to "instruct" the router that RIP should not be treated as an interesting traffic. The way to do that is to put an access-list that denies RIP and permit all others on the dialer-list of the dialing router... Like so: access-list 101 deny udp any any eq rip access-list 101 permit ip any any dialer-list 1 protocol ip list 101 Doing a "debug dialer packets again would yield the following: 07:41:40: BR0/0 DDR: ip (s=192.168.0.1, d=255.255.255.255), 72 bytes, outgoing uninteresting (list 101) OR for RIPv2 07:43:22: BR0/0 DDR: ip (s=192.168.0.1, d=224.0.0.9), 52 bytes, outgoing uninteresting (list 101) Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=65490&t=65482 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
