NETWORK NOT ESTABLISHED AFTER AWS VPN TUNNEL IS UP
0
2 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
I'd check two things:
- 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.
- 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.
0
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.
Relevanter Inhalt
AWS OFFICIALAktualisiert vor einem Jahr- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
Yes,my inbound rules allow ICMP and outbound allows all traffice
If I allow all traffic, both inbound and outbound, in a network ACL, does communication fail?
Also, can you confirm that the subnet route tables and customer gateway route tables are registered with each other's communication routes in BGP?