Score:0

RRAS NAT on specific fixed IP address

ng flag

I have an AWS EC2 VPC-based Windows Server instance that has two private IP addresses and two elastic IP addresses on a single network interface with IP addresses:

IP Role
172.16.30.245 Primary
172.16.30.197 Secondary

I have configured in the NIC the primary IP address and under the advanced tab I have added the secondary IP address however this has caused an undesired effect under RRAS. Clients connect using OpenVPN and have static routes added for certain networks and RRAS is forwarding those packets over the default gateway. After adding the secondary IP address to the NIC, RRAS started mapping OpenVPN IP addresses to the secondary IP address of the AWS NIC and they don't seem to be accepted by the default gateway for internet access.

I have tried to add the primary IP address in the address pool as 172.16.30.245/32 but that has stopped mapping IPs altogether. Disabling NAT also didn't help. As soon as I remove the secondary IP address from the AWS NIC, RRAS correctly maps OpenVPN IP addresses and everything is working.

How do I get RRAS to NAT IP addresses to a specific IP address, albeit 172.16.30.245/32 instead of 172.16.30.197?

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.