Router blocking traffic of Shark Ion Robot

RouterOS General
1

RB941-2nD
Firmware 6.45.3

I have a shark ION robot Vaccum that connects fine to cell phone hotspot and also will connect fine to Cisco Linksys E1000

I have reset mikrotik router, changed wifi settings a million ways and no change.
The robots shows up on the wireless registration tab and is assigned an ip of 192.168.1.229 which i can ping for about 90 seconds
then i get error on shark ion app and the device drops from the wifi.

I have changed my DNS to 8.8.8.8 and confirmed that ports are open

I ran tool sniffer for the IP 192.168.1.229

Hoping someone can help guide me to a solution?
shark.pcap.zip (3.99 KB)

2

It is often useful to search the forum before creating a new topic. See http://forum.mikrotik.com/t/router-blocking-traffic-of-shark-ion-robot/117097/1

3

Thanks for your response.
Guess I should have added the note…
Searched form and found previously mentioned issue with the same device. However, changing the dns servers to 8.8.8.8 and/or adding the following rules did not provide the same result for my setup.

/ip firewall nat
add action=masquerade chain=srcnat out-interface=ether1
add action=dst-nat chain=dstnat dst-address-type=local dst-port=53
per-connection-classifier=src-port:2/1 protocol=udp src-address=
192.168.1.229 to-addresses=1.1.1.1
add action=dst-nat chain=dstnat dst-address-type=local dst-port=53
per-connection-classifier=src-port:2/0 protocol=udp src-address=
192.168.1.229 to-addresses=8.8.8.8

4

Your capture shows that the DNS responses do not contain the Authoritative Nameservers and Additional Records sections, i.e. so far the same issue which turned out to cause the trouble in the topic linked above can still be the explanation of yours. Now the question is why the DNS responses don’t contain these sections. So as the first step, please sniff also at ether1 (/tool sniffer set file-name=dns.pcap, then /tool sniffer quick port=53, i.e. without restriction to particular interfaces). Your dst-nat rules seem fine to me but let’s see whether the responses from 8.8.8.8 and/or 1.1.1.1 do contain those sections. If they do, something must have gone wrong with the DNS redirection and the DNS continues to be cached (and the responses’ contents filtered) by your Tik; if they don’t, the rest of your network (including the ISP) is responsible for that, and we’ll have to identify the differences between where it doesn’t work (Mikrotik and its uplink) and where it does (Linksys E1000 and its uplink).