# Fedora 31 cloud image

**URL:** <https://linux-community.web.cern.ch/t/fedora-31-cloud-image/31>\
**Category:** FEDORA\
**Created:** [October 30, 2019, 4:49pm UTC](https://linux-community.web.cern.ch/t/fedora-31-cloud-image/31 "2019-10-30T16:49:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![schwicke](https://linux-community.web.cern.ch/user_avatar/linux-community.web.cern.ch/schwicke/32/54_2.png) [@schwicke](https://linux-community.web.cern.ch/u/schwicke)\
**Post date:** [October 30, 2019, 4:49pm UTC](https://linux-community.web.cern.ch/t/fedora-31-cloud-image/31/1 "2019-10-30T16:49:11Z")

</div>

Hi,  
did anybody try the Fedora 31 cloud image yet ? I did on our Cloud infrastructure, and it came up without IPv6 enabled. Checking /etc/sysconfig/networking-scripts indeed I found that the required IPv6 settings are missing.

Bug or feature ?

---

<div class="post-metadata">

**Author:** ![schwicke](https://linux-community.web.cern.ch/user_avatar/linux-community.web.cern.ch/schwicke/32/54_2.png) [@schwicke](https://linux-community.web.cern.ch/u/schwicke)\
**Post date:** [October 30, 2019, 4:52pm UTC](https://linux-community.web.cern.ch/t/fedora-31-cloud-image/31/2 "2019-10-30T16:52:16Z")

</div>

btw I fixed it manually by connecting with IPv4 (ssh -4 …) and adding

> IPV6INIT=“yes”  
> IPV6\_AUTOCONF=“yes”  
> IPV6\_DEFROUTE=“yes”  
> IPV6\_PEERDNS=“yes”  
> IPV6\_PEERROUTES=“yes”  
> IPV6\_FAILURE\_FATAL=“no”  
> DHCPV6C=yes

to

> /etc/sysconfig/network-scripts/ifcfg-eth0

+ restart the network/ rebooting
