AWS VPN PING ISSUE

Start with "diag debug flow" and see what it shows. You can also  run a diag sniffer packet <interface> "icmp" and  see what other icmp-message might come down the tunnel

hi,

I have a similar problem,  when performing the sniffer and sending a ping to aws I get an echo request no replay and if I send the ping from AWS I just get replay.

regards,

Armando Gómez

Hi,

please let me know only unable to ping ? is there any other ports you are able to telnet from source end?

Hello,

I agree with @sandralynn 's answer.

However, these are also the best steps you can try.

Confirm your routing configurations

Verify the Amazon VPC subnet route table configuration

1. Open the Amazon VPC console.
2. From the navigation pane, choose Route Tables.
3. Select the routing table used by your source Amazon Elastic Compute Cloud (Amazon EC2) instance.
4. Choose the Routes tab.
5. Verify that there is a route with Destination set to the on-premises network.
6. Verify that there is a Target with the value of Transit Gateway ID.

AWS DevOps Course you can look to find other easy ways.

Thanks

Hello All,

The problem, unfortunately, seems to go much deeper than I feared, there is an issue where traffic originating from the external interface of the firewall cannot it seems make it to the Gateway, although traffic from the inside zone can, I am talking it through with TAC as well as the upstream provider as this did work previously.

Thank you for your reply though and you are, of course, right that I should check there for the logs and make sure the traffic is allowed.

cyber security course

Hello Everyone,

You have to go to the security group of the EC2 instance you created. Then go to inbound rules and click Edit. Then add a Custom ICMP rule with Protocol as Echo Request. For source, add Anywhere so that you can ping from any machine you want.

I enjoyed this site. It was very easy to use and functional. The buttons are easy to find. I think this is a very good site and will continue to use it. For Python developers who concentrate on research and development using various machine learning and deep learning techniques, the Deep Learning with Tensorflow Course has been developed. This tutorial's objective is to describe every TensorFlow method and object.

Regards,
Atonal Wilson

Hi,

Because you're utilizing a Fortigate 60D firewall for VPN and both sides of the tunnel are visible, the problem could be with the firewall settings or routing setups.

Here are a few things to look into:

1. Ensure that traffic from your local network to the AWS EC2 instance is allowed through the Fortigate firewall. You can examine the firewall rules to see if any limitations are in place that are preventing traffic.

2. Confirm that the Fortigate firewall's routing table is correctly configured to send traffic from your local network to the AWS VPC where the EC2 instance is hosted.

3. Check the EC2 instance's security group settings to confirm that all traffic from your local network is permitted. Ascertain that the security group permits inbound traffic on the appropriate ports and protocols for your ping requests.

4. Confirm that your local network is configured correctly to transport traffic to the AWS VPC. To divert traffic to the AWS VPC, you may need to add a route to your local network's routing table.

5. Finally, review the logs on the Fortigate firewall to see if there are any error messages that could help narrow down the problem.

I hope this helps you address your problem. If you're still having problems after reviewing these settings, you might want to consult with a network or firewall professional who can help you fix the issue in further detail.

To Know More You can Opt for vlocity platform developer certification

There are several things you can try to fix AWS VPN ping issues:

Check the routing configuration: Ensure that the routing configuration on both sides of the VPN connection is correct. Make sure the route tables are configured to route traffic between the VPN connection and the destination network.

Check the security group rules: Check the security group rules to ensure that they allow traffic from the VPN connection to the destination network. You may need to create a new security group rule or modify an existing one.

Check the network ACLs: Network ACLs can block traffic from the VPN connection. Check the network ACLs to ensure that they allow traffic from the VPN connection to the destination network.

Regards,

Rachel Gomez