Skip to contentSkip to conversation

QEMU networking

DISCUSSION Gary Thomas 4 participants 8 messages May 12, 2011 – May 19, 2011

lore
Share & tools
lore
#0 lore raw

I'm having a devil of a time getting networking to work when I run qemu (a Poky derived image, of course!) I'm running this on a box which itself is NAT'd to the real internet, like this:

   +-------------+        +------------------+
   |   QEMUarm   |<------>|   My_Desktop     |<----> Internet
   | 192.168.7.2 |        |   192.168.7.1    |
   +-------------+        |   192.168.1.125  |
                          +------------------+

Firstly, something is messing with the routing tables over time and I can't get past the first hop. If I reconfigure the network on the QEMU system like this:

  # ifconfig eth0 down
  # ifconfig eth0 up
  # route add default gw 192.168.7.1
I can then access past "My_Desktop", e.g.
  # ping 192.168.1.101
     -or-
  # ping 74.125.225.19    (www.google.com)
This works fine and the routing table (route.good) is correct.

A little while later (minutes), the routing changes and now I can't get past 'My_Desktop' (i.e. I can ping 192.168.1.125, but not 192.168.1.101) The routing table has changed (route.bad)

What causes this? I don't have avahi running anywhere and I've explicitly disabled that daemon on the QEMU system.

Finally, there seems to be no name resolution - /etc/resolv.conf comes up as:
nameserver 127.0.0.1
If I want to resolve any real names, I have to update it manually.

Note: I'm running core-image-sato with web-webkit added using zypper.

Are others actually using the network with QEMU images? like this?

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Kernel IP routing table

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.7.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth0
0.0.0.0         0.0.0.0         0.0.0.0         U     0      0        0 eth0
0.0.0.0         192.168.7.1     0.0.0.0         UG    0      0        0 eth0
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.7.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
0.0.0.0         192.168.7.1     0.0.0.0         UG    0      0        0 eth0
#1 lore raw
Quoted 22 lines · Gary Thomas

I'm having a devil of a time getting networking to work when I run qemu (a Poky derived image, of course!) I'm running this on a box which itself is NAT'd to the real internet, like this:

+-------------+ +------------------+
| QEMUarm |<------>| My_Desktop |<----> Internet
| 192.168.7.2 | | 192.168.7.1 |
+-------------+ | 192.168.1.125 |
+------------------+

Firstly, something is messing with the routing tables over time and I can't get past the first hop. If I reconfigure the network on the QEMU system like this:

# ifconfig eth0 down
# ifconfig eth0 up
# route add default gw 192.168.7.1
I can then access past "My_Desktop", e.g.
# ping 192.168.1.101
-or-
# ping 74.125.225.19 (www.google.com)
This works fine and the routing table (route.good) is correct.
Quoted 3 lines

A little while later (minutes), the routing changes and now I can't get past 'My_Desktop' (i.e. I can ping 192.168.1.125, but not 192.168.1.101) The routing table has changed (route.bad)

Actually, I can only ping 192.168.7.1 - nothing outside of that subnet works.

Quoted 19 lines

What causes this? I don't have avahi running anywhere and I've explicitly disabled that daemon on the QEMU system.

Finally, there seems to be no name resolution - /etc/resolv.conf comes up as:
nameserver 127.0.0.1
If I want to resolve any real names, I have to update it manually.

Note: I'm running core-image-sato with web-webkit added using zypper.

Are others actually using the network with QEMU images? like this?

_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#2 lore raw
In reply to Gary Thomas

I had the same problem on my Fedora host. It turned out that the iptables rules were prohibiting the forwarding of packets from one network to another, causing the route to the internet to black hole.

Check that you don't have any IP tables that are preventing the routing from working.

--Mark

Quoted 45 lines · Gary Thomas

I'm having a devil of a time getting networking to work when I run qemu (a Poky derived image, of course!) I'm running this on a box which itself is NAT'd to the real internet, like this:

    +-------------+        +------------------+
    |   QEMUarm   |<------>|   My_Desktop     |<----> Internet
    | 192.168.7.2 |        |   192.168.7.1    |
    +-------------+        |   192.168.1.125  |
                           +------------------+

Firstly, something is messing with the routing tables over time and I can't get past the first hop. If I reconfigure the network on the QEMU system like this:

   # ifconfig eth0 down
   # ifconfig eth0 up
   # route add default gw 192.168.7.1
I can then access past "My_Desktop", e.g.
   # ping 192.168.1.101
      -or-
   # ping 74.125.225.19    (www.google.com)
This works fine and the routing table (route.good) is correct.

A little while later (minutes), the routing changes and now I can't get past 'My_Desktop' (i.e. I can ping 192.168.1.125, but not 192.168.1.101) The routing table has changed (route.bad)

What causes this? I don't have avahi running anywhere and I've explicitly disabled that daemon on the QEMU system.

Finally, there seems to be no name resolution - /etc/resolv.conf comes up as:

   nameserver 127.0.0.1

If I want to resolve any real names, I have to update it manually.

Note: I'm running core-image-sato with web-webkit added using zypper.

Are others actually using the network with QEMU images? like this?

_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky

#3 lore raw
Quoted 6 lines · Mark Hatle

I had the same problem on my Fedora host. It turned out that the iptables rules were prohibiting the forwarding of packets from one network to another, causing the route to the internet to black hole.

Check that you don't have any IP tables that are preventing the routing from working.

I don't have any tables that would cause this on my box other than what is set up by runqemu (it adds some NAT/MASQUERADE rules). I have the same behaviour on Fedora and Ubuntu hosts.

That said, it's the configuration on the target that's causing problems. I don't know what's getting in there and changing the routing periodically.

Quoted 51 lines · Gary Thomas
Quoted 41 lines

I'm having a devil of a time getting networking to work when I run qemu (a Poky derived image, of course!) I'm running this on a box which itself is NAT'd to the real internet, like this:

     +-------------+        +------------------+
     |   QEMUarm   |<------>|   My_Desktop     |<---->  Internet
     | 192.168.7.2 |        |   192.168.7.1    |
     +-------------+        |   192.168.1.125  |
                            +------------------+

Firstly, something is messing with the routing tables over time and I can't get past the first hop. If I reconfigure the network on the QEMU system like this:

    # ifconfig eth0 down
    # ifconfig eth0 up
    # route add default gw 192.168.7.1
I can then access past "My_Desktop", e.g.
    # ping 192.168.1.101
       -or-
    # ping 74.125.225.19    (www.google.com)
This works fine and the routing table (route.good) is correct.

A little while later (minutes), the routing changes and now I can't get past 'My_Desktop' (i.e. I can ping 192.168.1.125, but not 192.168.1.101) The routing table has changed (route.bad)

What causes this? I don't have avahi running anywhere and I've explicitly disabled that daemon on the QEMU system.

Finally, there seems to be no name resolution - /etc/resolv.conf comes up as:

    nameserver 127.0.0.1

If I want to resolve any real names, I have to update it manually.

Note: I'm running core-image-sato with web-webkit added using zypper.

Are others actually using the network with QEMU images? like this?

Quoted 4 lines

_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky

_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#4 lore raw
Quoted 8 lines · Gary Thomas
Quoted 6 lines · Mark Hatle

I had the same problem on my Fedora host. It turned out that the iptables rules were prohibiting the forwarding of packets from one network to another, causing the route to the internet to black hole.

Check that you don't have any IP tables that are preventing the routing from working.

Quoted 6 lines

I don't have any tables that would cause this on my box other than what is set up by runqemu (it adds some NAT/MASQUERADE rules). I have the same behaviour on Fedora and Ubuntu hosts.

That said, it's the configuration on the target that's causing problems. I don't know what's getting in there and changing the routing periodically.

Ahh, sorry, my reading comprehension has gone away today.

Check if you have a dhcp client running on the target side. It's possible that it keeps requesting updates and there is a bug (or "feature") in the client that resets your routes automatically?

--Mark

Quoted 52 lines
Quoted 51 lines · Gary Thomas
Quoted 41 lines

I'm having a devil of a time getting networking to work when I run qemu (a Poky derived image, of course!) I'm running this on a box which itself is NAT'd to the real internet, like this:

     +-------------+        +------------------+
     |   QEMUarm   |<------>|   My_Desktop     |<---->  Internet
     | 192.168.7.2 |        |   192.168.7.1    |
     +-------------+        |   192.168.1.125  |
                            +------------------+

Firstly, something is messing with the routing tables over time and I can't get past the first hop. If I reconfigure the network on the QEMU system like this:

    # ifconfig eth0 down
    # ifconfig eth0 up
    # route add default gw 192.168.7.1
I can then access past "My_Desktop", e.g.
    # ping 192.168.1.101
       -or-
    # ping 74.125.225.19    (www.google.com)
This works fine and the routing table (route.good) is correct.

A little while later (minutes), the routing changes and now I can't get past 'My_Desktop' (i.e. I can ping 192.168.1.125, but not 192.168.1.101) The routing table has changed (route.bad)

What causes this? I don't have avahi running anywhere and I've explicitly disabled that daemon on the QEMU system.

Finally, there seems to be no name resolution - /etc/resolv.conf comes up as:

    nameserver 127.0.0.1

If I want to resolve any real names, I have to update it manually.

Note: I'm running core-image-sato with web-webkit added using zypper.

Are others actually using the network with QEMU images? like this?

Quoted 4 lines

_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky

_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky

#5 lore raw
In reply to Gary Thomas
Quoted 11 lines · Gary Thomas
Quoted 9 lines · Mark Hatle

I had the same problem on my Fedora host. It turned out that the iptables rules
were prohibiting the forwarding of packets from one network to another, causing
the route to the internet to black hole.

Check that you don't have any IP tables that are preventing the routing from
working.

Quoted 7 lines

I don't have any tables that would cause this on my box other than what is set up by runqemu (it adds some NAT/MASQUERADE rules). I have the same behaviour
on Fedora and Ubuntu hosts.

That said, it's the configuration on the target that's causing problems. I don't know what's getting in there and changing the routing periodically.

Hi Gary,

Did you ever find out what was causing this? I'd like to know for reference.

Thanks,

Scott

Signature · 3 lines
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
#6 lore raw
Quoted 17 lines · Scott Garman
Quoted 16 lines · Gary Thomas
Quoted 9 lines · Mark Hatle

I had the same problem on my Fedora host. It turned out that the iptables rules
were prohibiting the forwarding of packets from one network to another, causing
the route to the internet to black hole.

Check that you don't have any IP tables that are preventing the routing from
working.

I don't have any tables that would cause this on my box other than what is set up by runqemu (it adds some NAT/MASQUERADE rules). I have the same behaviour
on Fedora and Ubuntu hosts.

Quoted 6 lines
Quoted 2 lines

That said, it's the configuration on the target that's causing problems. I don't know what's getting in there and changing the routing periodically.

Hi Gary,

Did you ever find out what was causing this? I'd like to know for reference.

No, I only saw it on QEMU and not a native build. I've not had time to look at it since - using the native build helped me diagnose the problem I was checking, so I didn't need QEMU any more.

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#7 lore raw
In reply to Gary Thomas
Quoted 29 lines · Gary Thomas

I'm having a devil of a time getting networking to work when I run qemu (a Poky derived image, of course!) I'm running this on a box which itself is NAT'd to the real internet, like this:

    +-------------+        +------------------+
    |   QEMUarm   |<------>|   My_Desktop     |<----> Internet
    | 192.168.7.2 |        |   192.168.7.1    |
    +-------------+        |   192.168.1.125  |
                           +------------------+

Firstly, something is messing with the routing tables over time and I can't get past the first hop. If I reconfigure the network on the QEMU system like this:

   # ifconfig eth0 down
   # ifconfig eth0 up
   # route add default gw 192.168.7.1
I can then access past "My_Desktop", e.g.
   # ping 192.168.1.101
      -or-
   # ping 74.125.225.19    (www.google.com)
This works fine and the routing table (route.good) is correct.

A little while later (minutes), the routing changes and now I can't get past 'My_Desktop' (i.e. I can ping 192.168.1.125, but not 192.168.1.101) The routing table has changed (route.bad)

What causes this? I don't have avahi running anywhere and I've explicitly disabled that daemon on the QEMU system.

Quoted 6 lines

Finally, there seems to be no name resolution - /etc/resolv.conf comes up as:

   nameserver 127.0.0.1

If I want to resolve any real names, I have to update it manually.

Note: I'm running core-image-sato with web-webkit added using zypper.

I suspect ConnMan may have something to do with it. Though that's only a suspicion based on some past experience.

Cheers,
Joshua

Signature · 3 lines
Joshua Lock
        Yocto Project Build Monkey
        Intel Open Source Technology Centre