From: Gary Thomas <gary@mlbassoc.com>
To: Scott Garman <scott.a.garman@intel.com>
Cc: poky@yoctoproject.org
Subject: Re: QEMU networking
Date: Thu, 19 May 2011 08:48:13 -0600 [thread overview]
Message-ID: <4DD52DAD.7090200@mlbassoc.com> (raw)
In-Reply-To: <4DD523DC.1030504@intel.com>
On 05/19/2011 08:06 AM, Scott Garman wrote:
> On 05/12/2011 09:28 AM, Gary Thomas wrote:
>> On 05/12/2011 10:23 AM, Mark Hatle wrote:
>>> 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.
>
> 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.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2011-05-19 14:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 16:10 QEMU networking Gary Thomas
2011-05-12 16:16 ` 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 [this message]
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=4DD52DAD.7090200@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=poky@yoctoproject.org \
--cc=scott.a.garman@intel.com \
/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.