A good first step would be to black hole route the /27 on RB1.
/ip route add dst=95.95.144.192/27 type=blackhole
This way, whenever port scan / IP scan traffic comes to unused addresses from your /27 it won’t cause ping-pong traffic between your router and the ISP router until TTL expires. (may those bastards rot in hell)
Then, make sure that the netmap rules you posted are actually EARLIER in the chain than the default masquerade rule.
Thanks ZeroByte for blackhole advise.
The masquerade is the last row on NAT setting.
My IPs are:
95.95.26.192/28
and
95.95.144.192/27 on static route in 95.95.26.206
The netmap on the first subnet, the IPs do not have problems:
/ip firewall nat
add chain=srcnat action=netmap to-addresses=95.95.26.194 src-address=10.10.10.200
add chain=dstnat action=netmap to-addresses=10.10.10.200 dst-address=95.95.26.194
95.95.26.194 has 95.95.26.194 some as internet ip both incoming and outgoing traffic.
But with subnet 95.95.144.192/27 the forward works well incoming, I can reach the device through internet but when I check my internet IP that is always 95.95.26.206.
The statis routes 95.95.144.192/27 on static route in 95.95.26.206 is made on Cisco ISP where I can not access, is it possible that the problem is on the CISCO router?