|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Re: test Nets being routed?
Ack! You don't have a permit statement in there. The last line should read something like: access-list 181 permit ip any any Also, I'd input the list before applying it to the apropriate interfaces. The slower ciscos seem to appreciate it more when it's done that way, though my 7206 just screams through it. Lord knows the kind of stress doing something like that could cause without a permit statement, especially if your offsite. Regards, Joe Shaw - [email protected] NetAdmin - Insync Internet Services Fortune for today: "You're not drunk if you can lie on the floor without holding on." -- Dean Martin On Tue, 23 Dec 1997, Randy Bush wrote: > > Am I the only one seeing the 192.168.0.0 test net going somewhere? RFC 1918 > > mandates 192.168.0.0/255.255.0.0 [192.168/16] for private networks (testing), > > right? Inc.net seems to have some problems... > > While they should not be announcing, you should not be listening. Try this > and call back in the morning if it does not work. > > access-list 181 deny ip host 0.0.0.0 any > access-list 181 deny ip 10.0.0.0 0.255.255.255 255.0.0.0 0.255.255.255 > access-list 181 deny ip 127.0.0.0 0.255.255.255 255.0.0.0 0.255.255.255 > access-list 181 deny ip 128.0.0.0 0.0.255.255 255.255.0.0 0.0.255.255 > access-list 181 deny ip 172.16.0.0 0.15.255.255 255.240.0.0 0.15.255.255 > access-list 181 deny ip 191.255.0.0 0.0.255.255 255.255.0.0 0.0.255.255 > access-list 181 deny ip 192.0.2.0 0.0.0.255 255.255.255.0 0.0.0.255 > access-list 181 deny ip 192.168.0.0 0.0.255.255 255.255.0.0 0.0.255.255 > access-list 181 deny ip 192.0.0.0 0.0.0.255 255.255.255.0 0.0.0.255 > access-list 181 deny ip 223.255.255.0 0.0.0.255 255.255.255.0 0.0.0.255 > > randy >
|