RE: Filtering/Poisoning ISIS injected 0.0.0.0/0 default route

From: Ian Henderson (ianh@chime.net.au)
Date: Mon May 30 2005 - 11:30:50 GMT-3

On Mon, 30 May 2005, ccie2be wrote:

> BTW, I don't see anything wrong with how Kwok used the distance command.
> Shouldn't that have worked?
>
> Router isis
> Distance 255 0.0.0.0 255.255.255.255 1
>
> Access-list 1 deny 0.0.0.0 0.0.0.0

'access-list 1 permit 0.0.0.0 0.0.0.0' is what you're after here. This
shows up as 'access-list 1 permit any' in the running config.

Rack1R3#show run | inc access-list 1
access-list 1 permit any
Rack1R3#show ip route 0.0.0.0
% Network not in table
Rack1R3#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Rack1R3(config)#no access-list 1
Rack1R3(config)#access-list 1 deny 0.0.0.0 0.0.0.0
Rack1R3(config)#
Rack1R3#show
6d05h: %SYS-5-CONFIG_I: Configured from console by console
Rack1R3#show ip route 0.0.0.0
Routing entry for 0.0.0.0/0, supernet
  Known via "isis", distance 115, metric 10, candidate default path, type
level-2
  Redistributing via isis
  Last update from 149.1.127.4 on FastEthernet0/0, 00:00:00 ago
  Routing Descriptor Blocks:
  * 149.1.127.4, from 149.1.254.4, via FastEthernet0/0
      Route metric is 10, traffic share count is 1

Rack1R3# 

--
Ian Henderson CCNA, CCNP
Senior Network Engineer

iiNet Limited
Chime Communications Pty Ltd

This archive was generated by hypermail 2.1.4 : Fri Jun 03 2005 - 10:12:03 GMT-3