> are you accessing using "external clients" or the regular netclient?
"External Clients" on OSX Wireguard.
[More Info]
The use case that we have is when we need access an Akami Network through a whitelisted IP during development.
Our AWS networks have a Priv Subnet w/ a static IP NAT and a Public Subnet, both prod and staging.
Since wanted our all our local machine's traffic to go through the AWS NAT we hoped for: Local -> Bastion EC2 (Public Subnet) -> EC2 (Private Subnet) -> NAT -> Internet.
So to get setup, we tested: Local -> Bastion EC2 (Public Subnet) -> Internet. When we set the Bastion EC2 to have Egress of 0.0.0.0 the Wireguard's Handshake would never complete, just hang.
Let me know if there's anything else I can provide.
> are you accessing using "external clients" or the regular netclient?
"External Clients" on OSX Wireguard.
[More Info]
The use case that we have is when we need access an Akami Network through a whitelisted IP during development.
Our AWS networks have a Priv Subnet w/ a static IP NAT and a Public Subnet, both prod and staging.
Since wanted our all our local machine's traffic to go through the AWS NAT we hoped for: Local -> Bastion EC2 (Public Subnet) -> EC2 (Private Subnet) -> NAT -> Internet.
So to get setup, we tested: Local -> Bastion EC2 (Public Subnet) -> Internet. When we set the Bastion EC2 to have Egress of 0.0.0.0 the Wireguard's Handshake would never complete, just hang.
Let me know if there's anything else I can provide.