topic Re: No Route Warnings in Network Security

No Route Warnings

bfrericks — Mon, 11 Mar 2019 10:14:05 GMT

In our syslog we are getting a ton of the following messages: No route to 63.168.xxx.xxx from 70.209.211.170. Now 63.168.xxx.xxx is a static nat on our outside interface and the 70. address is some IP unaffiliated with us. Unles I'm reading the message wrong, why would we be getting a message saying no route to 63.168.xxx.xxx when that is on my interface and is it the 70 address sending an ICMP message to us stating such?

Re: No Route Warnings

joshua.walton — Tue, 15 May 2007 00:32:10 GMT

Please post your config.

Thanks!

Re: No Route Warnings

bfrericks — Tue, 15 May 2007 11:41:48 GMT

Any particular part? you're after?

Re: No Route Warnings

vitripat — Wed, 16 May 2007 13:22:42 GMT

Can you provide output from "show static" and "show route"? If using 7.x commands would be "sh run static" & "sh run route".

Thanks,

Vibhor.

Re: No Route Warnings

bfrericks — Wed, 16 May 2007 13:46:53 GMT

It was over 4000 characters so it made me add as an attacment but here are the results of the show commands.

Re: No Route Warnings

acomiskey — Wed, 16 May 2007 19:10:43 GMT

I receive these "no route to" messages as well. Doesn't seem to effect anything.

No route to 75.x.x.x from 208.x.x.x

208.x.x.x = my asa outside interface

75.x.x.x = a public ip of a remote access vpn client

Could 70.209.211.170 also have been a vpn client in your case? I think if that were the case we would be onto something here.