Originally Posted by Dutchy
Does the following command bring back a 1 or a 0?
It should be a one.
You should also check the the virbr0 interface:
ip addr show virbr0 || ifconfig virbr0
Thanks for assistance all!
Dutchy, on the host I get the following...
[root]# sysctl net.ipv4.ip_forward
net.ipv4.ip_forward = 1
[root]# ip addr show virbr0 || ifconfig virbr0
4: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
link/ether fe:54:00:93:2d:49 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
so '1', and 'up'. Also I am using a wired connection (turned off wireless) and 'Virtual Network Default: NAT' is set as the NIC in Virtual Machine Manager. Here's a pic of my connection details in VMM, to me everything looks fine...
The virtual machine should be issued an IP on the internal range via DHCP. Not sure how to check if this service is running on the host. Note that the first time I set this up everything just worked, so not sure why not this time. :-/
---------- Post added at 11:39 AM ---------- Previous post was at 09:40 AM ----------
I wondered if the problem was dhcpd not issuing an IP, so I checked with 'service dhcpd status', got the following result...
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
I figured that maybe I should enable it then so...
# systemctl enable dhcpd.service
Failed to issue method call: No such file or directory
So enabling dhcpd didn't work. Besides, does'nt Virtual Machine Manager not take care of dhcp for vm's by acting as heir dhcp server or something?