Set the router id
/routing ospf instance set 0 router-id=x.x.x.x
Then add the network
/routing ospf network add network=192.168.8.16/28
That should be enough to get the adjacency.
One thing to bear in mind with Mikrotik is that it doesn’t (to my knowledge) compute link cost automatically. By default, an interface has cost 10 unless you manually create the interface (/routing ospf interfaces add ?) and set the cost manually. If you’re not setting costs proportional to bandwidth, then you’re basically getting the same type of routing decisions that RIP would make (least hops).
As for the Cisco commands you gave, I have a few things to say about what I’ve come to understand is best practice. It’s your network, and you know what your needs are, etc - so if you disagree, feel free to take the forthcoming information with a grain of salt:
Redistribute connected is probably a bad habit to get into.
It’s better to use passive-interface default and then include your interfaces in OSPF. (external routes don’t aggregate the same way that native routes do, and external routes can lead to routing loops, just to name a couple of reasons). This way, interfaces are “inside” ospf like it expects them to be, but it won’t try to form adjacencies. If you DO need an adjancency to form on an interface, then specify no passive-interface FaX/X.
I’m actually a fan of the newer “ospfv3” style syntax that Cisco now supports in OSPFv2.
Instead of defining network statements to activate ospf interfaces, (e.g. network 192.168.0.0 0.0.255.255 area 0) you can just explicitly activate ospf in the interfaces themselves:
interface fa0/1
ip ospf 101 area 0
!
With “passive-interface default” configured in your global ospf settings, all this will do is create the network as an internal network native to OSPF. It won’t send hello packets or form adjacencies on that interface.
Another good habit to get into - filter your redistributed routes by default.
Create a route map (e.g tagged101) that matches some specific tag, I use the same tag as the ospf process ID, so router ospf 101 would look for tag 101. Then instead of just redistribute static subnets, specify “redistribute static subnets route-map tagged101” This gives you finer-grained control over which routes get injected into ospf.
If you create a static route that you want to be injected into OSPF, then use the form “ip route x.x.x.x m.m.m.m y.y.y.y tag 101” You can just leave off the tag 101 if you want to test some route and not make it “global” in your network while you test, or if there’s some local behavior that you want but not to affect your entire routing table.
So originating interface networks as native to OSPF and giving yourself the ability to specify which static routes get injected into ospf, you have full control of your routing table now, and if you split into areas, you will get a lot fewer LSAs bouncing around whenever there is a topology change. (External LSAs go chugging right on through to the backbone regardless)
This is all coming from a reformed redistributor. 
