[Resolved] unable to ping Ligowave AP connected to Mikrotik RB951

Hello, I have Ligowave Propeller 2 which is set to AP bridge. One wireless client is connected to this Propeller (another Propeller in station mode, i.e.P2P link).
If I plug Propeller AP to Mikrotik bridged port then I cannot ping my Propeller anymore. However, if no wireless clients are connected to Propeller AP then I CAN ping it from Mikrotik. I.e. I lose wired connectivity once a single wireless client gets connected to the Propeller AP. At the same time if I plug my laptop to the Propeller AP then I can ping it regardless of whether wireless clients are connected or not.

I tried opening a ticket with Ligowave but they say the problem is with Mikrotik. Since I can ping Propeller if I plug it into my laptop.

I also did packet capture on the propeller-facing interface. During sniffing I also did ARP ping. I’m attaching pcap file.
What puzzles me is that I can see ARP and IP packets from the far end of P2P wireless link (192.168.77.79), I also see SSDP packet from the near end Propeller (192.168.77.16) but I don’t see any ARP requests or replies form the Mikrotik side. Obivously, I aslo cannot ping 192.168.77.79 regardless of the presense of ARP packets. It seems like Mikrotik just doesn’t answer ARP on that port. However, it’s explicity said to answer ARP. See screenshots as well.

Finally, what I also noticed is that I occasionally loose access to my Mikrotik bridge IP for a period of 10-30 seconds if Propeller-facing Ethernet port is ON.

[admin@MikroTik] > interface bridge export verbose
# jun/28/2016 20:23:54 by RouterOS 6.35.4
# software id = 4TQY-JEWB
#
/interface bridge
add admin-mac=00:00:00:00:00:00 ageing-time=5m arp=enabled auto-mac=yes \
    disabled=no forward-delay=15s max-message-age=20s mtu=1500 name=bridge1 \
    priority=0x8000 protocol-mode=rstp transmit-hold-count=6
/interface bridge port
add auto-isolate=no bridge=bridge1 disabled=no edge=auto external-fdb=auto \
    horizon=none interface=ether3 path-cost=10 point-to-point=auto priority=\
    0x80
add auto-isolate=no bridge=bridge1 disabled=no edge=auto external-fdb=auto \
    horizon=none interface=ether4 path-cost=10 point-to-point=auto priority=\
    0x80
add auto-isolate=no bridge=bridge1 disabled=no edge=auto external-fdb=auto \
    horizon=none interface=ether5 path-cost=10 point-to-point=auto priority=\
    0x80
add auto-isolate=no bridge=bridge1 disabled=no edge=auto external-fdb=auto \
    horizon=none interface=wlan1 path-cost=10 point-to-point=auto priority=0x80
add auto-isolate=no bridge=bridge1 disabled=no edge=auto external-fdb=auto \
    horizon=none interface=ether1 path-cost=10 point-to-point=auto priority=\
    0x80
add auto-isolate=no bridge=bridge1 disabled=no edge=auto external-fdb=auto \
    horizon=none interface=ether2 path-cost=10 point-to-point=auto priority=\
    0x80
/interface bridge settings
set allow-fast-path=yes use-ip-firewall=no use-ip-firewall-for-pppoe=no \
    use-ip-firewall-for-vlan=no



[admin@MikroTik] > interface ethernet print detail

2 XS ;;; propeller
      name="ether3" default-name="ether3" mtu=1500 l2mtu=1598 
      mac-address=D4:CA:6D:27:0D:08 orig-mac-address=D4:CA:6D:27:0D:08 
      arp=enabled auto-negotiation=yes 
      advertise=10M-half,10M-full,100M-half,100M-full,1000M-half,1000M-full 
      full-duplex=yes tx-flow-control=off rx-flow-control=off speed=100Mbps 
      master-port=none bandwidth=unlimited/unlimited switch=switch1

2016-06-28 19_51_35-admin@192.168.77.88 (MikroTik) - WinBox v6.35.4 on RB751G-2HnD (mipsbe).png

Any Mikrotik support here?

In the meanwhile I did a fresh packet capture. During packet capture I did ARP ping which failed. Refer to the screenshot.
However, packet capture clearly says that Propeller sends back ARP replies to Mikrotik. For some strange reason Mikrotik doesn’t want to accept this ARP reply and install in the ARP table
2016-06-29 12_43_14-admin@192.168.77.88 (MikroTik) - WinBox v6.35.4 on RB751G-2HnD (mipsbe).png
2016-06-29 13_10_30-admin@192.168.77.88 (MikroTik) - WinBox v6.35.4 on RB751G-2HnD (mipsbe).png
2016-06-29 13_09_45-test3.pcap.png

OK, seems like this was a one-person show =)

I found the root cause of the problem. Fortunately for the Mikrotik community - it wasn’t been a Mikrotik issue. The real issue is that Ligowave Propeller doesn’t work properly with STP.
RSTP was enabled on the Mikrotik bridge. Everything started to work instantly once I disabled STP on Mikrotik. So be aware folks, Ligowave doesn’t say publicly that their devices are incompatible with STP.

And I must tell you Mikrotik rocks! Not least beacuse of the great troubleshooting funcitonality.