Hi guys, I have two Mikrotiks - one as primary GW and another one as main site router.
They have static routing between them and I’m facing to weird routing loop when I’m trying to access the private IP of the site router from the main GW’s network. The site router’s private network is routed correctly except for its own private IP.
$ ping 172.16.20.1
PING 172.16.20.1 (172.16.20.1) 56(84) bytes of data.
From 172.16.0.13 icmp_seq=1 Time to live exceeded
From 172.16.0.13 icmp_seq=2 Time to live exceeded
From 172.16.0.13 icmp_seq=3 Time to live exceeded
From where do you run the traceroute (it seems that from one of the Mikrotiks), and from where do you run the ping (the prompt rather suggests some linux machine than a Mikrotik one)?
Since you say that the WiFi AP and WiFi client are in bridge mode, there is no reason why anything should use the WiFi client’s IP (172.16.0.13) as a gateway. I can’t say how that is linked to the issue, but it is definitely incorrect.
So answer the above questions and show /ip route print from all four Mikrotik devices. Befoer posting, substitute any public IPs if you want to remain anonymous.
Well, that's the magic for me. I don't get why I see the IP of one member of the wireless bridge. These IPs are not even in the routing table.
FYI: wireless bridge are two Ubiquiti devices (AP and client) in the bridge mode.
What I want is to do ping from bridge interface from 172.16.0.1 -> 172.16.20.1 and vice versa.
Routing table from 172.16.0.13:
ip route show
172.16.0.0/24 dev br0 proto kernel scope link src 172.16.0.13
169.254.0.0/16 dev br0 proto kernel scope link src 169.254.246.227
default via 172.16.0.1 dev br0
Routing table from 172.16.0.10:
ip route show
172.16.0.0/24 dev br0 proto kernel scope link src 172.16.0.10
default via 172.16.0.1 dev br0
Please see the attachments and filenames.
FIXED!
I just found that 172.16.20.1 has the same MAC address as 172.16.0.13 has (wireless bridge client device) in the main GW ARP table. So I checked options there and found out that this Ubiquiti device has disabled the WDS transparent bridge mode. Basically, it repeated traffic coming through the bridge but replaced MAC to its own which interrupted routing.
Right after I enabled WDS transparent bridge mode on Ubiquiti client device routing started working as expected.