MikroTik

Posted: **Fri Sep 15, 2017 3:22 pm**

On one of our routers we have a strange issue were the mikrotik can't ping anything at all, but is able to successfully traceroute to them.

- The router is running the latest 6.38.7 bugfix and has no firewalling enabled on it at all.
- All it does is perform BGP / OSPF and nothing else is configured on it.
- This is occuring on all interfaces.
- Devices on the network however can ping the Mikrotik and get a successful response.
- Another mikrotik device with the same / similar config works.
- This affecting directly connected links / peers and traffic outside the network.
- Any other device and outside of our network can ping this device and gets successful responses.

For example:

The one interface on the router has the IP xxx.xxx.216.241/28 and can't ping xxx.xxx.216.250:

[admin@rt1] > ping xxx.xxx.216.250
  SEQ HOST                                     SIZE TTL TIME  STATUS                                                                          
    0 xxx.xxx.216.250                                         timeout                                                                         
    1 xxx.xxx.216.250                                         timeout                                                                         
    2 xxx.xxx.216.250                                         timeout                                                                         
    sent=3 received=0 packet-loss=100%

However can traceroute to it:

[admin@rt1] > /tool traceroute xxx.xxx.216.250
 # ADDRESS                          LOSS SENT    LAST     AVG    BEST   WORST STD-DEV STATUS                                                  
 1 xxx.xxx.216.250                    0%    7   0.1ms     0.1     0.1     0.2       0

This is also occuring when trying to ping things outside our network:

[admin@rt1] > ping 8.8.8.8      
  SEQ HOST                                     SIZE TTL TIME  STATUS                   
    0 8.8.8.8                                                 timeout                  
    1 8.8.8.8                                                 timeout                  
    2 8.8.8.8                                                 timeout                  
    3 8.8.8.8                                                 timeout                  
    4 8.8.8.8                                                 timeout                  
    5 8.8.8.8                                                 timeout                  
    sent=6 received=0 packet-loss=100%

Has anyone come across this or have any ideas?

Posted: **Sat Sep 16, 2017 10:07 pm**

Our ccr1072 6.38.7 same issue.
it works good for 25 days. now it can't send any ping all of ip's. But traceroute is working fine.
We send this to the mikrotik Ticket#2017091622000659

Posted: **Sun Sep 17, 2017 7:56 pm**

The only difference between Ping and Trace (besides the TTL in the ICMP Type 8 outbound packet) is the return packet for the in-between hops. The return packet will be an ICMP type 11 for in between hops for a trace and an ICMP type 0 for the final hop. A ping will always have an ICMP type 0 as the return packet. Check to see if there are any firewalls that may be blocking ICMP type 0 but not 11 perhaps?

Posted: **Sun Sep 17, 2017 10:12 pm**

The only difference between Ping and Trace (besides the TTL in the ICMP Type 8 outbound packet) is the return packet for the in-between hops. The return packet will be an ICMP type 11 for in between hops for a trace and an ICMP type 0 for the final hop. A ping will always have an ICMP type 0 as the return packet. Check to see if there are any firewalls that may be blocking ICMP type 0 but not 11 perhaps?

we restart the router and ping comes back. it is software error.

Posted: **Tue Sep 19, 2017 7:07 am**

The only difference between Ping and Trace (besides the TTL in the ICMP Type 8 outbound packet) is the return packet for the in-between hops. The return packet will be an ICMP type 11 for in between hops for a trace and an ICMP type 0 for the final hop. A ping will always have an ICMP type 0 as the return packet. Check to see if there are any firewalls that may be blocking ICMP type 0 but not 11 perhaps?
we restart the router and ping comes back. it is software error.

@Meeker - There is no firewall configured, the router is using fastpath.

@sakirozkan - I left our router over the weekend and by Monday it could ping again. This is definately a software bug.

Posted: **Tue Sep 19, 2017 5:01 pm**

The only difference between Ping and Trace (besides the TTL in the ICMP Type 8 outbound packet) is the return packet for the in-between hops. The return packet will be an ICMP type 11 for in between hops for a trace and an ICMP type 0 for the final hop. A ping will always have an ICMP type 0 as the return packet. Check to see if there are any firewalls that may be blocking ICMP type 0 but not 11 perhaps?
we restart the router and ping comes back. it is software error.

@Meeker - There is no firewall configured, the router is using fastpath.

@sakirozkan - I left our router over the weekend and by Monday it could ping again. This is definately a software bug.

After 2 days pings come back itself. Software bug.

Posted: **Wed Sep 20, 2017 10:07 am**

the same problem here, still remains after reboot.

Posted: **Wed Sep 20, 2017 9:07 pm**

Mikrotik says
*) ping - fixed ping getting stuck (after several thousands of ping attempts);

is fixed with this.but when update ccr1072 it gives watchdog error and reboot

viewtopic.php?f=7&t=78462

MikroTik

Unable to ping from mikrotik

Unable to ping from mikrotik

Re: Unable to ping from mikrotik

Re: Unable to ping from mikrotik

Re: Unable to ping from mikrotik

Re: Unable to ping from mikrotik

Re: Unable to ping from mikrotik

Re: Unable to ping from mikrotik

Re: Unable to ping from mikrotik