when testing an image using runqemu qemux86, can you get networking to
work?? mine comes up disabled.  I want to test an application that requires
Internet access.

On Tue, May 22, 2012 at 10:45 AM, Autif Khan <autif.mlist@...
<mailto:autif.mlist@...>> wrote:

On Tue, May 22, 2012 at 7:43 AM, jfabernathy <jfabernathy@...
<mailto:jfabernathy@...>> wrote:
> when testing an image using runqemu qemux86, can you get
networking to
> work?? mine comes up disabled. I want to test an application
that requires
> Internet access.

Yes, I am able to get networking to work out of the box (bitbake
core-image-sato, etc.) Internetworking does not work out of the box.

This is accomplished over tun/tap devices - I do not know much about
these virtual networking devices - they have never failed for me :-)

The IP address of the emulated machine is 192.168.7.2 - The IP address
of host machine is 192.168.7.1

You can not (out of the box) communicate with machines other than the
host machine - so that would included internet etc.

So, if you have an ssh server or a web-server running on the host
machine - you can ssh to the host machine or browse a webpage using
the browser. Alternatively, you can run a proxy server on the build
machine and use it to get to the internet.

You can run ifconfig to see if the network is configured properly on
the emulated machine in the terminal. It should show 192.168.7.2 - if
you do not see this - you do not have networking working.


I can see the tap0 interface on my host at 192.168.7.1 by using ifconfig.
I can also see the eth0 on the qemu machine at 192.168.7.2
However, my host has an ip of 10.0.1.54 with a AP gateway at 10.0.1.1.
Somehow I need to connect the networks and I'm not sure exactly how to
do that so that DNS servers get used and the traffic all flows.
Jim A

On Tue, May 22, 2012 at 1:04 PM, Scott Garman <scott.a.garman@...
<mailto:scott.a.garman@...>> wrote:

On 05/22/2012 08:15 AM, James Abernathy wrote:



On Tue, May 22, 2012 at 10:45 AM, Autif Khan
<autif.mlist@... <mailto:autif.mlist@...>
<mailto:autif.mlist@... <mailto:autif.mlist@...>>__>
wrote:

On Tue, May 22, 2012 at 7:43 AM, jfabernathy
<jfabernathy@... <mailto:jfabernathy@...>
<mailto:jfabernathy@... <mailto:jfabernathy@...>>__>
wrote:
> when testing an image using runqemu qemux86, can you get
networking to
> work?? mine comes up disabled. I want to test an application
that requires
> Internet access.

Yes, I am able to get networking to work out of the box (bitbake
core-image-sato, etc.) Internetworking does not work out of
the box.

This is accomplished over tun/tap devices - I do not know
much about
these virtual networking devices - they have never failed
for me :-)

The IP address of the emulated machine is 192.168.7.2 - The
IP address
of host machine is 192.168.7.1

You can not (out of the box) communicate with machines other
than the
host machine - so that would included internet etc.

So, if you have an ssh server or a web-server running on the
host
machine - you can ssh to the host machine or browse a
webpage using
the browser. Alternatively, you can run a proxy server on
the build
machine and use it to get to the internet.

You can run ifconfig to see if the network is configured
properly on
the emulated machine in the terminal. It should show
192.168.7.2 - if
you do not see this - you do not have networking working.


I can see the tap0 interface on my host at 192.168.7.1 by using
ifconfig.
I can also see the eth0 on the qemu machine at 192.168.7.2
However, my host has an ip of 10.0.1.54 with a AP gateway at
10.0.1.1.
Somehow I need to connect the networks and I'm not sure exactly
how to
do that so that DNS servers get used and the traffic all flows.
Jim A


There is some sort of routing or IP forwarding bug in the sato
images that is due to be fixed soon. One thing I've found is you can
actually get out to the internet for about 30 seconds or so
immediately after the image boots. My suspicion is that some conman
script is killing the route after boot. core-image-minimal works
consistently, and since minimal doesn't use conman, I'm guessing
that is the culprit.

https://bugzilla.yoctoproject.__org/show_bug.cgi?id=2329
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=2329>

Scott

So if I read this right, I don't need any route or bridge commands to
make this work. If the bug gets fixed runqemu qemux86 should setup the
environment correctly so the web-webkit should get out to the internet
via the host machine connection?
JIm A

On 05/22/2012 10:26 AM, James Abernathy wrote:

On Tue, May 22, 2012 at 1:04 PM, Scott Garman <scott.a.garman@...
<mailto:scott.a.garman@...>> wrote:

On 05/22/2012 08:15 AM, James Abernathy wrote:



On Tue, May 22, 2012 at 10:45 AM, Autif Khan
<autif.mlist@... <mailto:autif.mlist@...>
<mailto:autif.mlist@... <mailto:autif.mlist@...>>__>
wrote:

On Tue, May 22, 2012 at 7:43 AM, jfabernathy
<jfabernathy@... <mailto:jfabernathy@...>
<mailto:jfabernathy@... <mailto:jfabernathy@...>>__>
wrote:

when testing an image using runqemu qemux86, can you get

networking to

work?? mine comes up disabled. I want to test an application

that requires

Internet access.

Yes, I am able to get networking to work out of the box (bitbake
core-image-sato, etc.) Internetworking does not work out of
the box.

This is accomplished over tun/tap devices - I do not know
much about
these virtual networking devices - they have never failed
for me :-)

The IP address of the emulated machine is 192.168.7.2 - The
IP address
of host machine is 192.168.7.1

You can not (out of the box) communicate with machines other
than the
host machine - so that would included internet etc.

So, if you have an ssh server or a web-server running on the
host
machine - you can ssh to the host machine or browse a
webpage using
the browser. Alternatively, you can run a proxy server on
the build
machine and use it to get to the internet.

You can run ifconfig to see if the network is configured
properly on
the emulated machine in the terminal. It should show
192.168.7.2 - if
you do not see this - you do not have networking working.


I can see the tap0 interface on my host at 192.168.7.1 by using
ifconfig.
I can also see the eth0 on the qemu machine at 192.168.7.2
However, my host has an ip of 10.0.1.54 with a AP gateway at
10.0.1.1.
Somehow I need to connect the networks and I'm not sure exactly
how to
do that so that DNS servers get used and the traffic all flows.
Jim A


There is some sort of routing or IP forwarding bug in the sato
images that is due to be fixed soon. One thing I've found is you can
actually get out to the internet for about 30 seconds or so
immediately after the image boots. My suspicion is that some conman
script is killing the route after boot. core-image-minimal works
consistently, and since minimal doesn't use conman, I'm guessing
that is the culprit.

https://bugzilla.yoctoproject.__org/show_bug.cgi?id=2329
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=2329>

Scott

So if I read this right, I don't need any route or bridge commands to
make this work. If the bug gets fixed runqemu qemux86 should setup the
environment correctly so the web-webkit should get out to the internet
via the host machine connection?
JIm A

Correct.

I'm hesitant to say this, but I'm hoping to have the bug fixed and patch submitted by the end of this week. Hopefully I haven't just jinxed myself. :)

Scott

https://bugzilla.yoctoproject.__org/show_bug.cgi?id=2329
<https://bugzilla.yoctoproject.org/show_bug.cgi?id=2329>

Scott

So if I read this right, I don't need any route or bridge commands to
make this work. If the bug gets fixed runqemu qemux86 should setup the
environment correctly so the web-webkit should get out to the internet
via the host machine connection?
JIm A

Correct.

I'm hesitant to say this, but I'm hoping to have the bug fixed and
patch submitted by the end of this week. Hopefully I haven't just
jinxed myself. :)

I did try it out on core-image-minimal and I can ping anything I have
the IP for. Not sure how you get the DNS connections working in qeum.