1 回答
- 最新
- 投票最多
- 评论最多
1
I just set up two new instances in IPv6-enabled subnets with security groups as you describe using Amazon Linux 2. I can ping (IPv4) and ping6 (IPv6) between the instances without any issues. I can also SSH using their IPv4 and IPv6 addresses.
I didn't have to add any routes to the instances - it just worked out of the box so I'd suggest not doing that if you don't have to.
You also haven't specified the OS type so it's difficult to figure out what else to suggest.
So, try this: Create a new VPC; new IPv4 and IPv6 CIDR ranges; two new subnets; then launch your instances.
相关内容
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前
Thanks for the response. Well if you check the instance would be using Network Manager and not the cloud-init.
systemctl status NetworkManager
The issue with NetworkManager is if we attach a second interface to the EC2 instance, that does not get configured inside the VM. so to avoid the manual configuration/routing for the secondary interface, we use cloud-init and it works fine. but with cloud-init ipv6 is not pingable across the AZ.
Also, kindly share the AMI that you used. we are using the centOS 7.9 image with cloud-init as cloud-init-19.4-7.el7.centos.5.x86_64
I used the default Amazon Linux 2 AMI on an ARM instance. For testing, i would encourage you to start simple: one ENI and see how it goes; then attach a second interface once you get things working.