F18 Host Only one Guest (currently) cannot connect to host, ping, web anything

[Frank Murphy]

Installed my first guest F16 Xfce 32bit (EOL, test)

No virt-preview installed standard repos only.

Virt-Manager in use.

The default "virt-network is there"
have tried it both NAT and routed,
deleted it, re-installed no joy.

Both eth0, eth1 show up in "Network Interfaces" tab
with their DHCP ipv4 info (ipv6 disabled on host by choice)

 ~]# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.6  netmask 255.255.255.0  broadcast
 192.168.0.255 ether 90:2b:34:98:cb:28  txqueuelen 1000  (Ethernet)
        RX packets 60  bytes 9351 (9.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 51  bytes 5856 (5.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.193  netmask 255.255.255.0  broadcast
192.168.0.255 ether a0:f3:c1:00:56:bb  txqueuelen 1000  (Ethernet)
        RX packets 138  bytes 75894 (74.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 165  bytes 15167 (14.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 0  (Local Loopback)
        RX packets 12  bytes 840 (840.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 12  bytes 840 (840.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.1.1  netmask 255.255.255.0  broadcast
192.168.1.255 ether 52:54:00:c6:4c:07  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 4  bytes 854 (854.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


~]# rpm -qa | grep virt
libvirt-daemon-qemu-0.10.2.3-1.fc18.x86_64
virt-manager-0.9.4-4.fc18.noarch
libvirt-daemon-driver-interface-0.10.2.3-1.fc18.x86_64
python-virtinst-0.600.3-2.fc18.noarch
libvirt-daemon-driver-storage-0.10.2.3-1.fc18.x86_64
libvirt-daemon-config-nwfilter-0.10.2.3-1.fc18.x86_64
libvirt-daemon-driver-libxl-0.10.2.3-1.fc18.x86_64
libvirt-daemon-driver-nodedev-0.10.2.3-1.fc18.x86_64
libvirt-daemon-driver-qemu-0.10.2.3-1.fc18.x86_64
libvirt-daemon-0.10.2.3-1.fc18.x86_64
libvirt-client-0.10.2.3-1.fc18.x86_64
virt-manager-common-0.9.4-4.fc18.noarch
libvirt-daemon-kvm-0.10.2.3-1.fc18.x86_64
libvirt-daemon-driver-nwfilter-0.10.2.3-1.fc18.x86_64
libvirt-python-0.10.2.3-1.fc18.x86_64
virt-viewer-0.5.4-3.fc18.x86_64
libvirt-daemon-driver-network-0.10.2.3-1.fc18.x86_64
libvirt-daemon-driver-xen-0.10.2.3-1.fc18.x86_64
libvirt-0.10.2.3-1.fc18.x86_64
libvirt-daemon-driver-uml-0.10.2.3-1.fc18.x86_64
libvirt-daemon-driver-lxc-0.10.2.3-1.fc18.x86_64
libvirt-daemon-config-network-0.10.2.3-1.fc18.x86_64
libvirt-daemon-driver-secret-0.10.2.3-1.fc18.x86_64


cat default.xml <snipped>
<network>
  <name>default</name>
  <uuid>e5216e09-7d6d-7999-0327-67ca7ecc5c60</uuid>
  <forward dev='eth1' mode='route'>
    <interface dev='eth1'/>
  </forward>
  <bridge name='virbr0' stp='on' delay='0' />
  <mac address='52:54:00:C6:4C:07'/>
  <ip address='192.168.1.1' netmask='255.255.255.0'>
    <dhcp>
      <range start='192.168.1.10' end='192.168.1.25' />
    </dhcp>
  </ip>
</network>


Booting F16-DVD in rescue mode on guest still no joy.

-- 
Regards,
Frank
http//www.frankly3d.com

[Laine Stump]

On 03/24/2013 08:29 AM, Frank Murphy wrote:
>  Installed my first guest F16 Xfce 32bit (EOL, test)
>
>  No virt-preview installed standard repos only.
>
>  Virt-Manager in use.
>
>  The default "virt-network is there"
>  have tried it both NAT and routed,
>  deleted it, re-installed no joy.
>
>  Both eth0, eth1 show up in "Network Interfaces" tab
>  with their DHCP ipv4 info (ipv6 disabled on host by choice)
>
>   ~]# ifconfig
>  eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>          inet 192.168.0.6  netmask 255.255.255.0  broadcast
>   192.168.0.255 ether 90:2b:34:98:cb:28  txqueuelen 1000  (Ethernet)
>          RX packets 60  bytes 9351 (9.1 KiB)
>          RX errors 0  dropped 0  overruns 0  frame 0
>          TX packets 51  bytes 5856 (5.7 KiB)
>          TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
>  eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>          inet 192.168.0.193  netmask 255.255.255.0  broadcast
>  192.168.0.255 ether a0:f3:c1:00:56:bb  txqueuelen 1000  (Ethernet)
>          RX packets 138  bytes 75894 (74.1 KiB)
>          RX errors 0  dropped 0  overruns 0  frame 0
>          TX packets 165  bytes 15167 (14.8 KiB)
>          TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
>
>  virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
>          inet 192.168.1.1  netmask 255.255.255.0  broadcast
>  192.168.1.255 ether 52:54:00:c6:4c:07  txqueuelen 0  (Ethernet)
>          RX packets 0  bytes 0 (0.0 B)
>          RX errors 0  dropped 0  overruns 0  frame 0
>          TX packets 4  bytes 854 (854.0 B)
>          TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
>
>
>  cat default.xml <snipped>
>  <network>
>    <name>default</name>
>    <uuid>e5216e09-7d6d-7999-0327-67ca7ecc5c60</uuid>
>    <forward dev='eth1' mode='route'>
>      <interface dev='eth1'/>
>    </forward> 
1) setting forward dev='eth1' very likely isn't doing what you think
it's doing. Setting the forward dev does not change any routing
decisions for the packets, it merely causes packets that would have been
forwarded out any other interface to instead be rejected/dropped.

2) Add that to the fact that your eth0 and eth1 both have IP addresses
on the same subnet, and you're setup for almost certain failure (since
it's unclear which interface would be used for any given packet)

3) If your network has forward mode='route', then the machines on the
network beyond the host must have a route for 192.168.1.0/24 that points
back at your virt host (192.168.0.6 or 192.168.0.193, pick one).

My recommendation:


1) since eth1 appears to be connected to the same subnet as eth0, just
disable it (if you *really* need the extra bandwidth, bond the two
interfaces together).

2) remove the "dev='eth1'" and "<interface
dev='eth1'/>" from your
network definition.

3) unless a) you need to support incoming connections to your guests
from the outside *and* b) the rest of the network has a route for
192.168.1.0/24 pointing back at the host, change the forward mode of the
network from 'route' to 'nat'.


>    <bridge name='virbr0' stp='on' delay='0'
> />
>    <mac address='52:54:00:C6:4C:07'/>
>    <ip address='192.168.1.1' netmask='255.255.255.0'>
>      <dhcp>
>        <range start='192.168.1.10' end='192.168.1.25' />
>      </dhcp>
>    </ip>
>  </network>
>
>
>  Booting F16-DVD in rescue mode on guest still no joy.
>

[Frank Murphy]

On Tue, 26 Mar 2013 10:37:00 -0400
Laine Stump <laine(a)laine.org&gt; wrote:

<snipped/>
>  
>  My recommendation:
>  
>  
>  1) since eth1 appears to be connected to the same subnet as eth0,
>  just disable it (if you *really* need the extra bandwidth, bond the
>  two interfaces together). 
I took your advice bonded eth0,eth1 as bond0 mode=6

and still have  firewalld enabled on the host,
trying the nkotb

-- 
Regards,
Frank
http//www.frankly3d.com