Hi Ricardo,
You should be able to use an offset-list in the outbound direction on the WAN interfaces to increase metric on R2. This way your MPLS VPN provider will see better EIGRP mettric through R1. What will happen then is provider's PE's will redistribute EIGRP routes into MP-BGP and insert a BGP cost community extended community attribute into your MPLS VPN routes. This value saves your EIGRP metric. When PE at the remote site makes a decision which route to choose, it will choose the one with lower BGP cost community, in your case, it's R1. It will then forward traffic to 192.168.10.0 and 192.168.20.0 through the next-hop of the PE router attached to R1. Here's the problem though. In order for this to work, your MPLS VPN provider should have configured different RD (route distringuisher) values for your VRF on PE1 (R1) and PE2 (R2). If they configured the same RD (which is quite common), then this solution won't work because their BGP route reflector will reflect only one of two 192.168.10.0/24 routes received from PE1 (R1) and PE2 (R2). Ask them.
The other solution is to run DMVPN (without protection) on top of MPLS. Yet another great advantage of using MPLS VPN with DMVPN. (The only distadvantage is 5% tunnel overhead for IMIX traffic). You can then natively route EIGRP between your CEs and use offset lists.
Finally, a simpler solution is to summarize outbound routes on R2. In your case you got 192.168.10.0/24 and 192.168.20.0/24 so it will be tough. If you could use, for example, 192.168.8.0/24 and 192.168.9.0/24, then you could summary these two EIGRP routes on R2 to 192.168.8.0/23. Your MPLS VPN provider will then prefer more specific routes through R1.
Good luck!
Regards,
Roman
