NETWORK NOT ESTABLISHED AFTER AWS VPN TUNNEL IS UP

Question

![Inbound Roules](/media/postImages/original/IM19mnAVF0Qh6YCgNaHZR1iw)
Hello,
I have setup my AWS VPN Tunnel connection which is IPSec over BGP. Both tunnels are up but cannot ping. I thought it was the security of network acl which I have enable All ICMP but still cannot ping my premise server and my premise server cannot ping me, but the all icmp is enabled

Brettski-AWS · Accepted Answer

I'd check two things:

1. You don't mention what operating system you're using but regardless of whether it is Windows or Linux, make sure that the host firewall is not blocking your traffic.
2. It's quite common for the customer VPN endpoint to be a firewall; if this is the case make sure that NAT is disabled for the VPN connection. In many firewall appliances the default is that it is enabled and that can make troubleshooting very difficult as NAT rules aren't established and traffic source/destination addresses are changed.

Riku_Kobayashi · Answer

Hello.

If I configure a network ACL to allow all traffic, does communication fail?  
Also, would it be possible for you to share the current settings for inbound and outbound?  
Also check that the security group's inbound rules allow ICMP.  
Additionally, check if the on-premises route is registered via BGP in the subnet route table.

NETWORK NOT ESTABLISHED AFTER AWS VPN TUNNEL IS UP

Relevant content