0

The network files in Fedora 22 server edition looks very different compared to those in F17, where I can find this howto.

My aim is to have KVM guests to be accessible over ssh and http as if they were real physical servers.

In my /etc/sysconfig/network-scripts/ifcfg-enp2s0f1 I have

HWADDR=xx:xx:xx:xx:xx:xx
TYPE=Ethernet
BOOTPROTO=dhcp
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
NAME=enp2s0f1
UUID=xxx
ONBOOT=yes
PEERDNS=yes
PEERROUTES=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6_PRIVACY=no

So the question is what do I need to change, so KVM guests can be accessed as if they were real physical servers?

5
  • Do you have valid IPv4 and/or IPv6 addresses to assign to those guests?
    – MadHatter
    Sep 4, 2015 at 9:23
  • That will be routable IPv4. Sep 4, 2015 at 9:24
  • Is that a question or an answer? If you mean "by 'valid', do you mean non-RFC1918?", then yes, I do (and they must be routed to you, not currently in use, etc.).
    – MadHatter
    Sep 4, 2015 at 9:24
  • Hopefully the answer to your question? The IPv4 addresses are public =) Sep 4, 2015 at 9:26
  • The guests will get public IPv4 addresses, so ssh and http can by accessed by anyone. Sep 4, 2015 at 9:28

1 Answer 1

1

Assuming you have your virtual switching infrastructure set up correctly, then for IPv4, set up a DHCP server to assign each of those addresses to the relevant guest. You have configured the clients to request their addresses via DHCP (BOOTPROTO=dhcp).

Alternatively, configure the v4 addresses into the guests statically, the method for which is unchanged since the F17 guide you link to.

DEVICE=enp2s0f1
BOOTPROTO=static
DNS1=AAA
GATEWAY=XXX
IPADDR=YYY
NETMASK=ZZZ
ONBOOT=yes
DNS2=BBB

Substituting for XXX etc. with appropriate values.

IPv6 is trickier, but you have not thus far answered my question about v6, so we'll leave it for now.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .