Comment 1 for bug 1976526
Revision history for this message
|
|
#1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
A Fedora user opened an issue[0] about an issue with cloud-init on EC2. When they launch an instance on a IPv6-enabled subnet, cloud-init sets the `ipv6.method` to `dhcp` in NetworkManager.
However, AWS uses router advertisements to let instances know about the nearest router. Using the `ipv6.method: dhcp` setting prevents router advertisements from working. The instance ends up with an IPv6 address assigned, but it cannot route traffic.
A workaround is to run NetworkManager commands to fix the issue:
```
nmcli con edit CONNECTION_UUID
nmcli> set ipv6.method auto
nmcli> save
nmcli> activate
```
The instance immediately routes IPv6 traffic after making that change. The dhcp setting appears to be applied automatically for EC2 subnets with IPv6 addresses assigned[1].
I would expect `ipv6.method` to be `auto` in these situations.
Thank you!
[0] https:/
[1] https:/