Tue Feb 07, 2023 8:37 pm
Yes, that's what I try to do for the past few day.
Host_A----------------------------192.168.31.0/24--------------------ether27[CRS-518]ether28---------------------172.16.31.0/24------------------------Host_B
192.168.31.3/24 192.168.31.1/24 172.16.31.1/24 172.16.31.4/24
I can ping from host_a to ether27 and ping from host_b to ether28, but host_a cannot even ping ether28, 172.16.31.1, on CRS-518. I think that's because the nexthop is not properly. Here's what I see on the CRS-518.
[admin@CRS_354_ROS] > /ip/address/print where interface="ether37"
Columns: ADDRESS, NETWORK, INTERFACE
# ADDRESS NETWORK INTERFACE
1 192.168.31.1/24 192.168.31.0 ether37
[admin@CRS_354_ROS] > /ip/address/print where interface="ether38"
Columns: ADDRESS, NETWORK, INTERFACE
# ADDRESS NETWORK INTERFACE
2 172.16.31.1/24 172.16.31.0 ether38
[admin@CRS_354_ROS] >
[admin@CRS_354_ROS] > /ip/arp/print
Flags: D, P - PUBLISHED; C - COMPLETE
Columns: ADDRESS, MAC-ADDRESS, INTERFACE
# ADDRESS MAC-ADDRESS INTERFACE
0 DC 192.168.88.2 54:EE:75:4C:10:2C bridge
1 DC 192.168.31.100 EC:30:91:5A:6A:C1 bridge
2 DC 192.168.31.3 00:1E:06:39:E2:9B bridge <----- arp for host_a
3 DC 172.16.31.4 00:1E:06:39:E7:C8 bridge <----- arp for host_b
[admin@CRS_354_ROS] >
[admin@CRS_354_ROS] > /ip/route/print
Flags: D - DYNAMIC; A - ACTIVE; c, y - COPY
Columns: DST-ADDRESS, GATEWAY, DISTANCE
DST-ADDRESS GATEWAY DISTANCE
DAc 172.16.31.0/24 bridge 0 <----- nexthop points to bridge, not outgoing interface ether38
DAc 192.168.31.0/24 bridge 0 <------ same situation as in interface ether37
DAc 192.168.88.0/24 bridge 0
[admin@CRS_354_ROS] >
So, the question is what Mikrotik CLI configuration is needed to make the route pointing to outgoing interface. In other product, which is really trivia and it's create automatically, especially for a router. But of course, I'm comparing apple to orange in terms of vendor/platform at the moment.