- Newest
- Most votes
- Most comments
Network communications is (almost!) always two-way. So if host A (on premises) can ping and connect to host B (in AWS) then there is already bi-directional traffic happening. What you may be experiencing is the inability to establish connections in either direction.
If host B can't connect back to host A then there is something stopping it - this is usually in the form of packet filters, firewall rules or in many cases, Network Address Translation (NAT) that is happening in "middle boxes" such as the VPN termination point. In my experience, this is pretty common so check to make sure that NAT is disabled.
You can tell reasonably easily that this is happening: Do a debug or packet capture on host B and then ping from host A. If you don't see the original IP address of host A then you have NAT enabled somewhere and the NAT is what it stopping connections from being established in the other direction.
Hello.
This thread explains about achieving bi directional communication: https://forums.openvpn.net/viewtopic.php?t=21784
Also this blog post provides an overview of Access Server's routing feature to provide access to connected VPN clients.https://openvpn.net/vpn-server-resources/reach-openvpn-clients-directly-from-a-private-network/#introduction
I hope this might be helpful.
Relevant content
- asked a year ago
- asked 2 years ago
- asked a year ago
- AWS OFFICIALUpdated 3 years ago
