Wilson,
I had some time to look at the lab this evening. The problem is two fold. You are redistributing statics on R3, but the only static that you have is the default route. This isn't treated as a true static, so you would need "default-information originate" on R3 in order to send it to R1 and pass it to the routers on the right.
The issue with that is that the way that you're wanting to do this, at least I'm assuming by the routes on R2 and R3, is that R4 and R5 will need to send their unknown routes to their respective upstream router. R4 would send anything it didn't know about to R3, but R3's default route is sent back to R4, and the same thing happens on the other side with R5 sending to R2 as a default route, but R2's static default route is pointing back to R5. This may be a little confusing.
In order to ping from R4 to R5, all of the routers in between will need to know about the routes on these routers. Let's use 192.168.10.0/24 on R4. R5 doesn't know about it, so when you try to ping it, it sends to R2. R2 doesn't know about it because it's not advertised, so it sends the traffic back to R5 which isn't what you want.
So, in order to fix it, you need to have all networks between all hosts advertised and known. For example, on R3, you can advertise for the three networks - 192.168.10.0/24 192.168.20.0/24 192.168.30.0/24 - and R1 and R2 will now know about them. When R5 sends traffic to 192.168.10.2 (R4), R2 can direct the traffic to R1 and then R3 and finally to R4. What happens if R4 receives a packet from 172.17.228.2? It will drop it if R2 isn't advertising for that network since it holds those subnets. R3 needs to know how to get back to R2's subnets in order for R4 to return the traffic since R4 is using R3 as it's default gateway. So you would also need to advertise the subnets from R2 into ospf so R3 knows how to get to them.
HTH,
John
*** Please rate all useful posts ***
HTH,
John
*** Please rate all useful posts ***
