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

Sophos Firewall v18 AWS site-to-site VPN connected but no traffic PING SSH

Well, I have followed this step-by-step, exactly:

https://community.sophos.com/sophos-xg-firewall/f/recommended-reads/125560/sophos-xg-firewall-v18-to-aws-vpn-gateway-ipsec-connection

....and while the VPN shows "UP" in both AWS and my Sophos VPN section, I cannot PING or SSH to my test EC2 instance. In the bottom screenshot you'll see I have PING and SSH allowed from anywhere (0.0.0.0/0). I've been at it for hours, first because I mistakenly followed the v17. Even with the v17 how-to, my VPN said it was up in AWS and Sophos VPN section. Then I found v18 and thought for sure I would have success. No such luck.

At one point I got stuck at the part where I couldn't find my "xfrm" interface until I realize that little vertical blue line meant I could expand my WAN interface, thanks to THIS ARTICLE. Again, I thought for sure I would have success. No such luck again, and now I'm at a loss. 

The only difference I've noticed between my setup and the setup in the link above, is in Step 9 and Step 10, I have "xfrm1" not "xfrm2".

Anyone know where I should start with troubleshooting?



This thread was automatically locked due to age.
  • Still the same Disappointed -- I had to change the "Local ID type" from IP address back to the default "Select local ID" option because otherwise it was forcing me to enter an IP address in the "Local ID" field. Going to watch a few episodes of Ozark... my head hurts.

  • Hello,

    Did you create a new Ec2 instance this time?

    Regards,

  • No. I've only been deleting/recreating the VPN stuff, and attaching it to my existing test VPC (on a 10.10.0.0/16) network, which then has a 10.10.1.0/24 subnet in it with my test EC2 instance at 10.10.1.93. I'm guessing one shouldn't have to completely delete/recreate an EC2 instance... instead, just make sure your newly created Virtual Private Gateway is attached to the existing test VPC and the correct routing and firewall rules are in place. In any case, I just created a new EC2 instance (10.10.1.13) and cannot PING or SSH to that either. My VPC and Security Group was created using the "Set the AWS side" section of the Sophos v17 AWS VPN tutorial -- because the Sophos v18 AWS VPN tutorial completely leaves all of the VPC creation stuff out.

  • I suppose I am ready to pay for support to find out why my setup isn't working after following the how-to's verbatim. Would I just go to www.sophos.com/.../support.aspx and click the CHAT WITH US link and go from there, or does anyone know if there's a different avenue to get support for evaluations? I just went through the setup for I think the 5th or 6th time, and while the tunnel says "UP" on the Sophos and AWS, I'm still unable to pass any traffic, so I'm white-flag'n it and will just pay to find out what I'm missing Disappointed

  • Hello,

    I could send you screenshots of my configuration via PM, if you would like then you can compare them with yours. I don't believe the issue is with the XG but rather on the AWS side since we can see the pings leaving the tunnel, (I would double-check this again with all the changes), Sophos would only troubleshoot the XG side, so I would be checking with AWS for them to double confirm your configuration for the VPC.

    I forgot to ask what type of Ec2 are you deploying?

    Do let me know if you want me to share my configuration. 

    Support for evaluations is only provided by the community.

    Regards

  • Hi , if you don't mind I would greatly appreciate the screenshots. My trial is about to end on the Sophos and we're trying to get the production firewall in place by the end of the week, and I've been stuck on this one thing for weeks Sweat

  • Hello there,

    I have send you a PM with the configuration.

    Regards,