Perhaps there is a Router God, that can see configurations over long distances??
haha nice jok, you are all right
but i think at end i will solve it by putting new wifi router behind mikrotik and disable wifi from ISP
thank you all for patience and understanding
You could have posted your configuration to make sure people are able to overlook possible errors in your configuration. But it looks like the problem can be cleared if we dig a little bit deeper.
You are connected to the network 192.168.0.0/24 via wifi. If you try to reach some host in 192.168.1.0/24 your computer (or whatever device) will send packets to the standard-gateway since you should have only one route on that client (0.0.0.0/0 via gateway - means every packet gets send to your ISPs device). The ISP-device does not know about the subnet 192.168.1.0/24. If its configured properly it wont route the traffic anywhere but just drop the packets. If its misconfigured it may sends the packet to the ISPs next hop (who hopefully will throw it away).
In this case you have 2 options:
-> You could either tell the ISP device that Network 192.168.1.0/24 is reachable via the mikrotiks ip (192.168.0.12), sometimes called "static routes" or something like that. Its possible that ISPs device is not giving you the option to setup static routes.
-> You could go with destination-nat rules. In this case you would setup a dst-nat rule with dst-address set to mikrotiks eth1 ip (192.168.0.12), matching a destination port (you chose this one) and natting it to to-address and to-port of your choice (in the network behind your mikrotik router, to-address and to-port must match with your dvr or whatever device you are trying to forward). Now you need to connect to mikrotiks eth1 ip from your wifi-client (use the port you chose in dst-nat rule). If you do not have any firewall-filter rules setup this will work right away. If you have set them you need to setup the accept-rule as well.