arp-ping not working on RouterOS v7

RouterOS RouterOS beta
1

Hello,

I am currently using RouterOS v6.49.2, and started testing RouterOS v7.1, but I am currently facing a problem with arp-ping.
I tested on CHR, hAPac2 and RB4011iGS+, and with the default setup (no custom configuration at all), so the problem is easy to reproduce.

I am using a laptop connected to eth2 (by default in “bridge”). He gets automatically an IP address from dhcp : during my tests it was 192.168.88.254, and router have the 192.168.88.1, by default.

Trying to ping the laptop from the router :
With 6.49.2 :

  • ping to 192.168.88.254 is OK
  • ping (with arp-ping=yes and interface=bridge) to 192.168.88.254 is OK

With 7.1 :

  • ping to 192.168.88.254 is OK
  • ping (with arp-ping=yes and interface=bridge) to 192.168.88.254 is NOT working (status: ping failed)

Has anyone else experienced this problem ?

Best regards,
MCA

2

I just encountered the same with 7.1.1 on hAP ac2: http://forum.mikrotik.com/t/v7-1-1-is-released/154314/421

3

Hi!

Same issue here.

Running RouterOS 7.1.1 on RB5009UG+S+.

4

Same here, RoSV7.3beta37 and RB4011

5

Same on hEX S with 7.2.1

[demo@MikroTik] > /system/routerboard/print
       routerboard: yes
        board-name: hEX S
             model: RB760iGS
     serial-number: 
     firmware-type: mt7621L
  factory-firmware: 6.46.4
  current-firmware: 6.47.10
  upgrade-firmware: 7.2.1
[demo@MikroTik] > /tool/ping arp-ping=no interface=vlan241 192.168.241.1
  SEQ HOST                                     SIZE TTL TIME       STATUS                                                                                                                                               
    0 192.168.241.1                              56  64 895us     
    1 192.168.241.1                              56  64 739us     
    2 192.168.241.1                              56  64 652us     
    3 192.168.241.1                              56  64 579us     
    4 192.168.241.1                              56  64 720us     
    5 192.168.241.1                              56  64 698us     
    6 192.168.241.1                              56  64 708us     
    7 192.168.241.1                              56  64 709us     
    8 192.168.241.1                              56  64 665us     
    sent=9 received=9 packet-loss=0% min-rtt=579us avg-rtt=707us max-rtt=895us 

[demo@MikroTik] > /tool/ping arp-ping=yes interface=vlan241 192.168.241.1
  SEQ HOST                                     SIZE TTL TIME       STATUS                                                                                                                                               
    0                                                              ping failed                                                                                                                                          
    1                                                              ping failed                                                                                                                                          
    2                                                              ping failed                                                                                                                                          
    3                                                              ping failed                                                                                                                                          
    4                                                              ping failed                                                                                                                                          
    5                                                              ping failed                                                                                                                                          
    6                                                              ping failed                                                                                                                                          
    sent=7 received=0 packet-loss=100% 

[demo@MikroTik] >
6

Same issue in RB3011UiAS with 7.1.5

[nothing@MikroTik] > /system/routerboard/print
       routerboard: yes
             model: RB3011UiAS
          revision: r2
     serial-number: *********
     firmware-type: ipq8060
  factory-firmware: 6.47.10
  current-firmware: 6.47.10
  upgrade-firmware: 7.1.5

[nothing@MikroTik] > ping arp-ping=no interface=130 10.1.30.167
  SEQ HOST                                     SIZE TTL TIME       STATUS        
    0 10.1.30.167                                56 255 443us     
    1 10.1.30.167                                56 255 370us     
    2 10.1.30.167                                56 255 327us     
    3 10.1.30.167                                56 255 347us     
    4 10.1.30.167                                56 255 330us     
    sent=5 received=5 packet-loss=0% min-rtt=327us avg-rtt=363us max-rtt=443us 

[nothing@MikroTik] > ping arp-ping=yes interface=130 10.1.30.167
  SEQ HOST                                     SIZE TTL TIME       STATUS        
    0                                                              ping failed   
    1                                                              ping failed   
    2                                                              ping failed   
    3                                                              ping failed   
    4                                                              ping failed   
    sent=5 received=0 packet-loss=100% 

[nothing@MikroTik] >
7

I just upgraded to 7.2.3 stable and the same thing happens.

8

I’m not really sure if it’s related, but yesterday I upgraded hEX S from v6.49.6 to v7.2.3 and I was no longer able to connect to IPsec resources from the Road-Warrior VPN. Using IKEv2 with RSA authentication, I can connect to resources on the local network, but not to resources behind other IPsec tunnels. Downgrading back to v6.49.6, the problem disappears.

At the same time with an almost identical configuration on RB5009 and v7.2.3, I don’t experience this problem.

9

We’re having the same arp ping issues, running version 7.2.3.

10

I am not using IPsec on my hEX S, but it seems unlikely to me that arp-ping is involved at all with IPsec.

What seems more likely to me is some change in IPsec between v6.49.6 (6x) and v7.2.3 (7x). Since the RB5009 never supported any version of v6, the upgrade wouldn’t have made the v6 to v7 jump with many changes, and probably more upgrade problems than going from any v7 to another v7 version.

11

I can also confirm that ARPING is not working with RoS 7.2.3

I tested on 3 boards,

CCR1036-8G-2S+
CCR1072-1G-8S+
CCR2116-12G-4S+ ( this one is ROS7 v native , it can’t be downgraded to v6 )

do definitely it’s a BUG.

12

Log a support ticket. Just make sure you provide a supout file otherwise they will stall your ticket by asking you for supout even if your bug report explains that it is easy to reproduce the issue on any device with default config…(I know this because it’s exactly what just happened to me with another issue report)

13

Thank you for this info!

I’ve filed a bug report, as per your instructions, and Mikrotik acknowledged the issue:
“We have managed to reproduce the issue locally in our labs and look forward to fixing it on upcoming RouterOS versions, unfortunately, I cannot provide an ETA now.”

I guess that, when the problem will be solved, it will pop in the RouterOS changelog.

14

Hello,

Same issue here, version 7.2.3 (stable).

15

Any update on this?
Causing me serious issues with bonding slaves monitoring…

16

I am having this issue as well, verified on 3 hEX’s and 2 2004’s with varying configs, one on the default and one with no config. I put in a support ticket with a supout file attached.

17

So, apparently this is almost a year old issue, still present on my rb4011 7.5 (stable) and chr 7.6rc1 (testing). would providing supout expedite the fix?

18

I think they are already aware of the issue. I put in a support request and attached a supout file and got this response:

Hello, this will be fixed in upcoming releases of ROS, thanks!

I am hoping the fix comes with ROS 7.6

19

I think they are not doing anything to solve it..
Arping is a great tool for solving network problems. I don’t understand Mikrotik’s laziness in this matter.

I also opened a case and got a similar response from Mikrotik on 06/05/2022 (Support case SUP-81289):

We have managed to reproduce the issue locally in our labs and look forward to fixing it on upcoming RouterOS versions, unfortunately, I cannot provide an ETA now.

20

I forgot… I just upgraded to RouterOS 7.6 and the problem persists.