Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
02-24-2021 12:32 PM
Hi All, pretty dumb question here. I've setup the VM-series in AWS and attached three interfaces to the box. The intention here is to setup NAT (due to overlapping IP space) over a site-to-site VPN.
* management, I can get to this just fine and use the web console etc (call this 10.0.0.2/24)
* "inside" attached to eth1/1, is connected to our private network ( call this 10.0.0.3/24)
* "outside" attached to eth1/2, is connected to our public network in AWS and has an EIP associated (associated address is 10.1.0.2/24)
eth1/1 and eth1/2 are setup using DHCP in AWS, with eth1/2 having un-checked the "Automatically create default route to default gateway provided by server" box.
The question is where/how does one configure the "public or outside" interface to reach the internet via the EIP? I can't seem to get traffic to flow out that interface (using the EIP) no matter what set of routes I put in place.
02-25-2021 01:12 PM
To egress the internet from your 'public' interface, you'll need to put it into a Public AWS subnet. For this subnet in the aws route tables you'll route 0.0.0.0 to the Internet Gateway (IGW). Also set an EIP on your Eth1/2 ip address. The IGW does the nat translation as it leaves to the internet.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
