Hi, same issue here. But i have to add that it happens only on windows machines, that try to access via ssh or sftp 192.168.100.0 network, added by simple static route rule. I have no connection issues with generic 192.168.0.0 network, made by mikrotik itself. Only switching off the "drop inval...

192.168.0.50 is mikrotik. Finally i managed to get things working, and as expected the problem was not on mikrotik side - i used vagrant vm box to check subnet, and it used vagrant default gateway, which was virtualbox's NATed interface (so traffic from supposedly 172.16.17.0 network was originating...

Thanks for you reply. I've checked everything: i have disabled filter rules, no NAT rules, no routing rules, but still the only thing i get while i try to ping 172.16.17.10 from 192.168.0.69 -> From 192.168.0.50: icmp_seq=40 Redirect Host(New nexthop: 192.168.0.50) 192.168.0.50 is gateway. And yes, ...

I do have filter rules and i did what you suggest to no result - the behaviour didn't change.

Hello. I have one physical interface eth0-local, on which i run dhcp server, network 192.168.0.0/24 Now i want to setup 172.16.17.0/24 on the same interface. Here is what i do: i add second address on the same interface - 172.16.17.1/24, network 172.16.17.0, with this address comes a dynamic route t...

Ohhh... It seems i misunderstood those big textboxes in /tool netwatch winbox window - i thought they should contain the script itself... Thank you.

Hello, i have some problemas with netwatch script (it doesn't woark, actually): /ip route set [find comment="ISP1"] distance=1; /ip route set [find comment="ISP2"] disabled=yes; :delay 5; /ip firewall connection remove [find dst-address=95.213.163.196]; I have ROS 6.32.3 and am i...