Hi Christian,

Attached is a txt file containing the verbose output.

Peter

Quoting Christian Helmuth <christian.helmuth@...1...>:

Hello Peter,

I have no good guess from your provided information. So, please post a complete log of 'make clean; make VERBOSE= test/lwip".

Greets

Christian Helmuth Genode Labs

http://www.genode-labs.com/ · http://genode.org/

Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

---

SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev _______________________________________________ Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main

Hi Christian,

Turns out that the errors was on my end. So now that everything builds, I was wondering how to get this server running natively. I'm trying to run the simple web server on an ia32 machine, but I keep getting "sending packet failed" messages on serial output. The other message I keep getting is from test-dde-linux_linux26_net, where the message is "network device 1 unknown", which would suggest that the ethernet port is not being detected. The contents of the config file is the following:

<config> <start> <filename>timer</filename> <ram_quota>512K</ram_quota> </start> <start> <filename>pci_drv</filename> <ram_quota>512K</ram_quota> </start> <start> <filename>nic_drv</filename> <ram_quota>512K</ram_quota> </start> <start> <filename>test-dde_linux26_net</filename> <ram_quota>16M</ram_quota> </start> <start> <filename>lwip_httpsrv_test</filename> <ram_quota>1M</ram_quota> </start> </config>

I have also included the listed files in the weaver_x86.xml file as well.

What steps do I need to do in order to get the web server up and running?

Thanks Peter

Christian Helmuth wrote:

Hello Peter,

I could not reproduce the error here. Did you change any Genode sources on your side? Could you please generate preprocessor output for lwip_sys_arch.o by running

/usr/local/genode-gcc/bin/genode-x86-g++ -DCONFIG_MAX_THREAD_BITS=10 -ffunction-sections -nostdinc -g -O2 -MMD -MP -MT 'lwip_sys_arch.o lwip_sys_arch.d' -Wall -static -fno-stack-protector -I. -I/home/petern/gen_build/genode-okl4-x86/include -I/home/petern/downloads/genode-9.11/libports/include/lwip -I/home/petern/downloads/genode-9.11/libports/contrib/lwip-1.3.1/src/include -I/home/petern/downloads/genode-9.11/libports/contrib/lwip-1.3.1/src/include/ipv4 -I/home/petern/downloads/genode-9.11/libports/contrib/lwip-1.3.1/src/include/api -I/home/petern/downloads/genode-9.11/libports/contrib/lwip-1.3.1/src/include/netif -I/home/petern/downloads/genode-9.11/libports/src/lib/lwip/include -I/home/petern/downloads/genode-9.11/base-okl4/include -I/home/petern/downloads/genode-9.11/base/include -I/home/petern/downloads/genode-9.11/os/include -I/home/petern/downloads/genode-9.11/demo/include -I/home/petern/downloads/genode-9.11/libports/include -I/home/petern/downloads/genode-9.11/linux_drivers/include -I/home/petern/downloads/genode-9.11/sampling/include -I/home/petern/downloads/genode-9.11/base-okl4/include/x86 -I/home/petern/downloads/genode-9.11/base/include/x86 -I/home/petern/downloads/genode-9.11/os/include/x86 -I/home/petern/downloads/genode-9.11/demo/include/x86 -I/home/petern/downloads/genode-9.11/libports/include/x86 -I/home/petern/downloads/genode-9.11/linux_drivers/include/x86 -I/home/petern/downloads/genode-9.11/sampling/include/x86 -I/home/petern/downloads/genode-9.11/base-okl4/include/32bit -I/home/petern/downloads/genode-9.11/base/include/32bit -I/home/petern/downloads/genode-9.11/os/include/32bit -I/home/petern/downloads/genode-9.11/demo/include/32bit -I/home/petern/downloads/genode-9.11/libports/include/32bit -I/home/petern/downloads/genode-9.11/linux_drivers/include/32bit -I/home/petern/downloads/genode-9.11/sampling/include/32bit -I/usr/local/genode-gcc/lib/gcc/i686-pc-linux-gnu/4.2.4/include -c /home/petern/downloads/genode-9.11/libports/src/lib/lwip/platform/sys_arch.cc -o PRE -E -dD

in your build directory and posting the file PRE? I'm sure we'll find the bug ;-)

Greets

Hi,

Is anyone able to give me some pointers on how to set up the TAP version of the HTTP server? My knowledge on setting up such things is not that good. More specifically, I'm unsure as to what do for setting up the DHCP server step stated in the following link: http://genode.org/documentation/release-notes/9.02#section-4

Thanks Peter

Hi all,

if you're working with ubuntu, you could also setup bridge-utils (apt-get install bridge-utils) on your host and try the following scripts:

-- qemu-start-nw

! #!/bin/sh ! # ! # This script requires qemu 0.11.50 or newer and a host ! # system with bridge utils. Must be run as root. ! ! qemu-ifup tap0 ! ! qemu -kernel $1 -serial stdio -m 1024 -usbdevice mouse -usbdevice keyboard -net nic,model=pcnet,macaddr=00:81:71:61:51:41 -net tap,ifname=tap0,script=no,downscript=no ! ! qemu-ifdown tap0

$1 would be the weaver.elf file. Don't make the first byte of the assigned mac address an odd number, because that would be a multicast mac address which might be ignored by some (linux-) peers.

-- qemu-ifup

! #!/bin/sh ! # ! # script to bring up the tun device in QEMU in bridged mode ! # first parameter is name of tap device (e.g. tap0) ! ! # ! # First take eth0 down, then bring it up with IP 0.0.0.0 ! # ! /sbin/ifconfig eth0 down ! /sbin/ifconfig eth0 promisc up ! ! # ! # Bring up the tap device (name specified as first argument, by QEMU) ! # ! /usr/sbin/openvpn --mktun --dev $1 --user `id -un` ! /sbin/ifconfig $1 up ! ! # ! # create the bridge between eth0 and the tap device ! # ! /usr/sbin/brctl addbr br0 ! /usr/sbin/brctl addif br0 eth0 ! /usr/sbin/brctl addif br0 $1 ! /sbin/ifconfig br0 up ! ! # ! # only a single bridge so loops are not possible, turn off spanning tree protocol ! # ! /usr/sbin/brctl stp br0 off

-- qemu-ifdown

! #!/bin/sh ! # ! # Script to bring down and delete bridge br0 when QEMU exits ! # ! # Bring down eth0 and br0 ! # ! /sbin/ifconfig eth0 down ! /sbin/ifconfig $1 down ! /sbin/ifconfig br0 down ! # ! # Delete the bridge ! # ! /usr/sbin/brctl delbr br0 ! # ! # bring up eth0 in "normal" mode ! # ! /sbin/ifconfig eth0 -promisc ! /sbin/ifconfig eth0 up ! # ! # delete the tap device ! # ! /usr/sbin/openvpn --rmtun --dev $1

Perhaps you must prevent local networking from using the bridged interface (for whatever reason, this does not seem to work in my case)

! route del -net 192.168.1.0 netmask 255.255.255.0 dev eth0 ! route add -net 192.168.1.0 netmask 255.255.255.0 dev wlan0

Good luck

Sven

Christian Helmuth wrote:

Hello Peter,

On Mon, Feb 22, 2010 at 11:29:38AM +1030, Peter Nguyen wrote:

...

Is anyone able to give me some pointers on how to set up the TAP version of the HTTP server? My knowledge on setting up such things is not that good. More specifically, I'm unsure as to what do for setting up the DHCP server step stated in the following link: http://genode.org/documentation/release-notes/9.02#section-4

I also discovered this deficiency in the documentation while writing a section of the release notes for Genode 10.02. The information regarding your question is:

[...] Therefore, the device has to be configured prior to running Genode like the following.

! sudo tunctl -u $$USER -t tap0 ! sudo ip link set tap0 up ! sudo ip address add 10.0.0.1/24 brd + dev tap0

Give it a try with the lwIP example scenario. Please note that lwIP is configured for DHCP and does not assign a static IP configuration to its end of the wire. Hence, you should run a DHCP server on tap0, e.g.

! sudo /usr/sbin/dhcpd3 -d -f -cf /tmp/dhcpd.conf -pf /tmp/dhcpd.pid -lf /tmp/dhcpd.lease tap0

An example 'dhcpd.conf' may look like

! subnet 10.0.0.0 netmask 255.255.255.0 { ! range 10.0.0.16 10.0.0.31; ! }

The DHCP server's log will show you that the driver fakes an ethernet NIC with the MAC address 01:02:03:04:05:06.

Happy Hacking

-- Sven Fülster

Hi Peter,

On Tue, Feb 23, 2010 at 01:40:42PM +1030, Peter Nguyen wrote:

OK, so now i've got the server up and running, and I can use the local web browser to access the address 10.0.0.16.

Great :-D

However, I was under the impression that this IP address could be accessed by other machines. Am I right in saying this? Or is access to this server only restricted to other qemu instances?

I'm not sure if I understand your question, but... Qemu is using the Linux tun/tap network device to provide a virtual ethernet NIC to the guest OS. The tap device is subject to Linux' standard networking configuration, i.e., is just a new NIC at the host. If you don't configure your system for bridging (as Sven outlined) or with special IP forwarding rules, no other machine has access to your emulated system in Qemu.

Cheers

Hi Peter,   my scripts were just a suggestion because they work in my special case. I'm using a machine with two interfaces, eth0 and wlan0.   With the scripts, I bridge qemu to eth0, and during this step, eth0 becomes unusable for my host OS for whatever reason.   Therefore, I tell my host OS to use wlan0 instead by modifying the routing tables:   ! route del -net 192.168.1.0 netmask 255.255.255.0 dev eth0 ! route add -net 192.168.1.0 netmask 255.255.255.0 dev wlan0   Perhaps you must also set the default route to the second interface:   ! route add default gw 192.168.1.1 dev wlan0   With this configuration, I reach qemu over the external 'link' from wlan0 to eth0.   Note, that this might be a dirty solution far from being perfect in any case :)   Good luck   Sven

Peter Nguyen <peter.nguyen@...29...> hat am 23. Februar 2010 um 13:17 geschrieben:

Christian,

So i copied the three scripts Sven provided, and I am not able to get  the bridged connection working. Every time i run the script, the  current eth0 connection is closed, and another ethernet connection is  created that results in no interaction with the outside world. When i  close the server and run the ifdown.sh script, the ethernet connection  goes back to normal.

Am i meant to follow the instructions you provided in your email  before i run these scripts? I tried doing that myself and it didn't  work.

---

Peter Nguyen Jacaranda Research Group

On 23/02/2010, at 7:47 PM, Christian Helmuth wrote:

...

Hi Peter,

On Tue, Feb 23, 2010 at 01:40:42PM +1030, Peter Nguyen wrote:

...

OK, so now i've got the server up and running, and I can use the  local web browser to access the address 10.0.0.16.

Great :-D

...

However, I was under the impression that this IP address could be accessed by other machines. Am I right in saying this? Or is access to this server only restricted to other qemu instances?

I'm not sure if I understand your question, but... Qemu is using the Linux tun/tap network device to provide a virtual ethernet NIC to the guest OS. The tap device is subject to Linux' standard networking configuration, i.e., is just a new NIC at the host. If you don't configure your system for bridging (as Sven outlined) or with special IP forwarding rules, no other machine has access to your emulated system in Qemu.

Cheers

Christian Helmuth Genode Labs

http://www.genode-labs.com/ · http://genode.org/

Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

---

-- Download Intel&#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main

---

Download Intel&#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Genode-main mailing list Genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main

-- Sven Fülster

Hi,

from looking at the scripts it seems the bridging interface lacks an IP address, means instead of eth0 you have to use the bridging interface as target/source for communication now. Then you should be able to connect from the "outside" to your qemu virtualized system as well as the host computer.

Regards,

Robert

PS: I found http://www.gentoo-wiki.info/Bridging to be enlightening about the whole bridging issue itself; you can skip the Gentoo specific stuff which tails the more generic description of bridging on Linux.

On 02/23/2010 04:34 PM, Christian Helmuth wrote:

Peter,

On Tue, Feb 23, 2010 at 10:47:10PM +1030, Peter Nguyen wrote:

...

So i copied the three scripts Sven provided, and I am not able to get the bridged connection working. Every time i run the script, the current eth0 connection is closed, and another ethernet connection is created that results in no interaction with the outside world. When i close the server and run the ifdown.sh script, the ethernet connection goes back to normal.

Sounds strange, but I'm not very familiar with bridged setups. Maybe it does not work this way for you as it seems to work suboptimal for Sven too. He wrote

Perhaps you must prevent local networking from using the bridged interface (for whatever reason, this does not seem to work in my case)

and configures his host to route over his wireless - Sven?

...

Am i meant to follow the instructions you provided in your email before i run these scripts? I tried doing that myself and it didn't work.

No, Sven's scripts should work without my notes.

Greets