This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Cannot get traffic to pass over IPSEC AWS VPN when connecting to XG via SSL VPN

I have successfully connected the AWS instance to the XG and am able to ping between local LAN and AWS no problem. Connecting in to the XG via SSL VPN to access resources on AWS fails. I've checked and rechecked and went through the logs, but cannot find the problem.

 

I've made sure the AWS subnet was added into the rule on the XG, and I've checked the VPN connection on AWS and added the VPN subnet as well. 

 

Any help would be greatly appreciated.



This thread was automatically locked due to age.
Parents
  • Hey  

    Are you able to determine how far your traffic makes it along? At which point does it fail? (Traceroute, TCPdump, Log Viewer, Packet Capture)

    I was going to advise a couple things, but you mentioned you have performed some of them already.

    • AWS subnet/Remote SSL VPN subnet included in the firewall rule, SSL VPN policy, IPsec connection
    • Ensure that Ping is enabled in your XG's Local Service ACLs
    • Have you tried to pass other types of traffic? (RDP, SSH, FTP)

    Regards,

    Flo

  • Hi,

    Thanks for the reply!

     

    I have tried TraceRoute and such, and it doesn't go past the VPN IP address. I have also checked and made sure ICMP is enabled. RDP, which will be the main use, times out as well. 

     

    -Cory

Reply Children