Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 27 subscribers
  • Views 3532 views
  • Users 0 members are here
Options
Suggested
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

v18 - cannot ping to XG from route based VPN

Wimar Aswan

Hi,

I'm trying out the XG v18 route based VPN. So far I've got it replacing the policy based VPN to Azure and between sites. What I've noticed is that since switching the VPN from policy to route, I'm unable to ping the XG from the other side of the tunnel. I can ping other devices so I know the tunnel is working, I just can't ping the XG's local IP from the remote tunnel. Pinging the XG's WAN IP works, however that would be cause of the local ACL exception. All XG are on SFOS 18.0.0 GA-Build354.

 

Thank you.

WA



This thread was automatically locked due to age.
Parents Reply
  • 0 in reply to LuCar Toni

    The IP of PortA on one of the XG. If I do a route lookup in XG2 for XG1's PortA IP address, it returns saying it is located in PortB instead of the VTI interface. If I create a static route for XG1's local subnet, route lookup in XG2 will return with the VTI interface. However ping still doesn't work.

    I've tried the following route precedence:

    SD-WAN policy route, VPN route, Static route. (initial value as I upgraded to v18)

    Static route, SD-WAN policy route, VPN route.

    Both system generated traffic and reply packet routing have been enabled. 

Children