Hi, We're having issues getting Client VPN traffic to route over our AWS Direct Connect connection. Our MX100 has static routes configured that point to our AWS subnets, to push traffic over a router that has been specifically configured for the direct connect. "Use VPN" has been enabled for the AWS subnets in Site-to-site VPN. AWS Security Groups allow access to for the VPN subnet. Packet trace looks as though it is working: --- Start Of Stream --- tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on client_vpn, link-type RAW (Raw IP), capture size 262144 bytes 23:55:31.124913 IP 192.168.13.4 > 10.60.14.12: ICMP echo request, id 1, seq 63, length 40 23:55:36.125236 IP 192.168.13.4 > 10.60.14.12: ICMP echo request, id 1, seq 64, length 40 23:55:41.125291 IP 192.168.13.4 > 10.60.14.12: ICMP echo request, id 1, seq 65, length 40 23:55:46.135298 IP 192.168.13.4 > 10.60.14.12: ICMP echo request, id 1, seq 66, length 40 --- End Of Stream --- Although having issues accessing the resource from the workstation: Pinging 10.60.14.12 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Anyone have any ideas? Thanks. Kind Regards, mmeck
... View more
