cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
245
Views
0
Helpful
1
Replies

icmp port unreachable question

ColForbin
Level 1
Level 1

I was just testing something and noticed an odd debug.

I have three routers testing something, all just plain vanilla configs, and adding a static route to a loopback address and I'm able to ping and traceroute to it, and I thought it was just fine...i happened to debug ip icmp and every 10 seconds I'm getting  a destination port unreachable...I'm not sending any icmp, that i'm aware, that causes this message to pop on the console the moment i enter the route:

R3  192.168.2.1---------192.168.2.2 R2 192.168.13.2---------192.168.13.1 R1 Loop 1.1.1.1

R1 ip route 192.168.2.0 255.255.255.0 192.168.13.2

R2 ip route 1.1.1.1 255.255.255.255 192.168.13.1

R2 pings/traceroute 1.1.1.1 no issue, R3 cannot till the static is added

R3 ip route 1.1.1.1 255.255.255.255 192.168.2.2

Immediately this is logged to the console of R3:

dst 192.168.2.1 port unreachable from 192.168.13.1

And on the console of R1:

dst 1.1.1.1 port unreachable sent to 192.168.2.1

every 10 seconds.....

But 1.1.1.1 is pingable from R3.  Probably would have gone unnoticed just by happenstance was running a deb ip icmp

Something dumb i'm not seeing right? 

1 Accepted Solution

Accepted Solutions

ColForbin
Level 1
Level 1

nevermind lol, it was something stupid.  R3 was not in fact wr erased, and there was a tunnel config just lingering using those ip's

View solution in original post

1 Reply 1

ColForbin
Level 1
Level 1

nevermind lol, it was something stupid.  R3 was not in fact wr erased, and there was a tunnel config just lingering using those ip's