Solved! Go to solution.
Well done.
>Is the router advertising the client VPN subnet into AWS?
I should have been more explicit. It meant the BGP peering here.
The MX100 is on premise.
Does the Direct Connect router (on premise) have a route for the client VPN subnet pointing to the MX?
Is the router advertising the client VPN subnet into AWS?
When you are connected via Client VPN can you ping the LAN interface of the local Direct Connect router?
The MX100 is on premise - Yes it is.
Does the Direct Connect router (on premise) have a route for the client VPN subnet pointing to the MX?
Not initially, although added a route to the direct connect router to point the Client VPN range to the MX
Is the router advertising the client VPN subnet into AWS? No, a route wasn't propagated, although added one manually to point to the direct connect virtual gateway.
When you are connected via Client VPN can you ping the LAN interface of the local Direct Connect router? I couldn't initially - but after adding the route to point to the MX I can now.
So is it working now?
Well done.
>Is the router advertising the client VPN subnet into AWS?
I should have been more explicit. It meant the BGP peering here.