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