If you are trying to ping se2/0 on router1, that will fail, because router0 has to be configured to do routing, and r1 needs a route back to pc0.
However, if you are pinging se2/0 on r0, this depends on how the code is written. In the past, that worked. Because when the packet arrive to the router, the mac header(L2) is stripped off, and packet is puched up to L3 to be handled. There the router discover that this is my own interface, so the ping is answered. If this is still working on newer routers, i don't now.
