All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Poky Project <poky@yoctoproject.org>
Subject: QEMU networking
Date: Thu, 12 May 2011 10:10:10 -0600	[thread overview]
Message-ID: <4DCC0662.6060404@mlbassoc.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1757 bytes --]

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?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

[-- Attachment #2: route.bad --]
[-- Type: text/plain, Size: 416 bytes --]

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

[-- Attachment #3: route.good --]
[-- Type: text/plain, Size: 260 bytes --]

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

[-- Attachment #4: qemu.ps --]
[-- Type: application/postscript, Size: 6302 bytes --]

             reply	other threads:[~2011-05-12 16:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-12 16:10 Gary Thomas [this message]
2011-05-12 16:16 ` QEMU networking Gary Thomas
2011-05-12 16:23 ` Mark Hatle
2011-05-12 16:28   ` Gary Thomas
2011-05-12 16:32     ` Mark Hatle
2011-05-19 14:06     ` Scott Garman
2011-05-19 14:48       ` Gary Thomas
2011-05-19 22:50 ` Joshua Lock

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DCC0662.6060404@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=poky@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.