I have a similar problem and I hope Chupaka can help.
I have "WAN" and "LAN" IPs assigned to me by my ISP.
My WAN schema is a /30 (aa.bb.59.104 / 30), which gives me a single IP on my Mikrotik's "Public" interface (aa.bb.59.106) to talk to my ISP's Cisco router (which is assigned aa.bb.59.105).
I then have a /29 network (which gives me 6 usable public IPs but is a
slightly different IP schema than the /30, - aa.bb.
58.161 thru aa.bb.
58.166) that is properly passed/routed through the Cisco to my Mikrotik, which I can then use for devices behind the Mikrotik on my "Private" interface.
I can successfully assign aa.bb.58.xx addresses to interfaces on my Mikrotik (which I don't want to do), but I mistakenly gave someone aa.bb.58.161 / 29 as the network range they could use for devices when I should have given them aa.bb.58.160 / 29. So, assuming .161 was the network, they assigned aa.bb.58.162 to a device with a gateway of aa.bb.58.161.
While this eats up two of my public IPs (aa.bb.58.161 and 162), I think I can rectify it by establishing the proper routes in the Mikrotik. Basically, I want to setup routes that allow the device who's IP is aa.bb.58.162 to be able to access (and be accessed by) the Internet, but I can't figure out the proper routes.
Please help! Please send either specific terminal commands or the proper GUI settings so I can get this working!
I would prefer not to use bridging, 1:1 NAT, "fake IPs" or anything else "exotic" if it can be helped. I believe a simple route can do the trick.