A VM created w/ fedora-cloud-base image comes with ipv6 disabled.
Could we treat IPv6 as a first class citizen and have IPv6 enabled by default on the fedora-cloud-base image ?
Steps to reproduce: #1 - start a vm using the img [0]. #2 - list the ipv6 connection method of the eth0 interface:
eth0
[root@localhost ~]# nmcli c s "System eth0" | grep -i ipv6.method ipv6.method: ignore
Expected Results: ipv6.method: auto
Additional info: We're currently achieving this result via cloud-init:
... networkData: | version: 2 ethernets: eth0: dhcp4: true accept-ra: true
[0] - https://download.fedoraproject.org/pub/fedora/linux/releases/33/Cloud/x86_64/images/Fedora-Cloud-Base-33-1.2.x86_64.qcow2
This is entirely appropriate for the Amazon EC2 images. IPv6 is enabled or disabled at the VPC/Subnet and it is expected to be on by default at the instance.
Metadata Update from @dustymabe: - Issue tagged with: meeting
We discussed this at the community meeting today.
* AGREED: we should/will remove networking configuration from the cloud images and let NetworkManager default configs apply, which should get us in a situation where ipv6 is no longer ignored. (dustymabe, 16:39:52)
@davdunc has agreed to help us make this change.
Metadata Update from @ngompa: - Issue untagged with: meeting - Issue tagged with: AWS, GCP, OpenStack
@davdunc is still planning to get to this
Metadata Update from @ngompa: - Issue tagged with: Azure, OCI
Login to comment on this ticket.