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

AWS IPSec VPN lacking a route

On our XG330 v2 18.5.1 MR-1 Following the various guides, I have set up a VPN to AWS using their (supplied by a third party whose VPC it is) generic config file.

The VPN is active and connected but the local host has no route to the remote subnet. 

  • Looking on the CLI, route -n does not have a route to the remote subnet
  • system ipsec_route show is empty

Does this also need a static route from our internal subnet to the remote subnet?  If so what gateway/interface to use?

Thanks in advance

Jon



This thread was automatically locked due to age.
Parents
  • Which VPN do you use?
    SSL S2S?
    IPSec - standard-mode
    IPSec - Interface - route based VPN?
    Can you show us your configuration ?

    a trace route test does not pass the tunnel?


    Dirk

    Systema Gesellschaft für angewandte Datentechnik mbH  // Sophos Platinum Partner
    Sophos Solution Partner since 2003
    If a post solves your question, click the 'Verify Answer' link at this post.

Reply
  • Which VPN do you use?
    SSL S2S?
    IPSec - standard-mode
    IPSec - Interface - route based VPN?
    Can you show us your configuration ?

    a trace route test does not pass the tunnel?


    Dirk

    Systema Gesellschaft für angewandte Datentechnik mbH  // Sophos Platinum Partner
    Sophos Solution Partner since 2003
    If a post solves your question, click the 'Verify Answer' link at this post.

Children
No Data