https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-secondary-cidr-on-vpc-ability-to-nat-to-pan-in-original-cidr/m-p/436549#M1343 <P>Hey all,</P><P>It has finally happened and we ran out of IPv4 space on Primary CIDR block for our VPC. We created a new CIDR and associated it to the same VPC. However it appears that I can't associate an ENI in the new CIDR to our Palo Alto in the original CIDR. And we can't use the NAT ENI in the original because it hops to the original then out which AWS doesn't allow.</P><P>&nbsp;</P><P>Has anyone tried this, or aware of how to work around this issue?&nbsp; Thanks, Chad</P> Fri, 24 Sep 2021 22:10:58 GMT Chad_Chamberlain 2021-09-24T22:10:58Z https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-secondary-cidr-on-vpc-ability-to-nat-to-pan-in-original-cidr/m-p/436549#M1343 <P>Hey all,</P><P>It has finally happened and we ran out of IPv4 space on Primary CIDR block for our VPC. We created a new CIDR and associated it to the same VPC. However it appears that I can't associate an ENI in the new CIDR to our Palo Alto in the original CIDR. And we can't use the NAT ENI in the original because it hops to the original then out which AWS doesn't allow.</P><P>&nbsp;</P><P>Has anyone tried this, or aware of how to work around this issue?&nbsp; Thanks, Chad</P> Fri, 24 Sep 2021 22:10:58 GMT https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-secondary-cidr-on-vpc-ability-to-nat-to-pan-in-original-cidr/m-p/436549#M1343 Chad_Chamberlain 2021-09-24T22:10:58Z