Comment 7 for bug 1196907

Riku,

I'm pretty sure this is now happening for me using bridged networking.

=== Running the foundation model as:

/opt/arm/Foundation_v8pkg/Foundation_v8 --network-bridge=ARMaim --network bridged --image /scratch/oe-jdk8/jenkins-setup/build/tmp-eglibc/deploy/images/linux-system-foundation-Image--3.10+git0+2f9c206cc5-r0-genericarmv8-20130820153604.axf --block-device /scratch/oe-jdk8/jenkins-setup/build/tmp-eglibc/deploy/images/linaro-image-minimal-genericarmv8-20130820154502.rootfs.ext2

=== And on the device:

# ifconfig eth0

root@genericarmv8:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:02:F7:EF:00:01
          inet addr:192.168.1.137 Bcast:192.168.1.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:42083 errors:0 dropped:128 overruns:0 frame:0
          TX packets:26605 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:63391633 (60.4 MiB) TX bytes:1911712 (1.8 MiB)
          Interrupt:47 DMA chan:ff

where 192.168.1.x is my host network.

=== Doing the same as before. On my host:

$ ls -l openjdk8-aarch64-snapshot.tar.bz2
-rw-rw-r-- 1 aim aim 60668557 Aug 8 11:20 openjdk8-aarch64-snapshot.tar.bz2
$ md5sum !$
md5sum openjdk8-aarch64-snapshot.tar.bz2
9d17af7bf8b67b9b7af8b0e792c30238 openjdk8-aarch64-snapshot.tar.bz2

=== On the target:

root@genericarmv8:~# rm openjdk8-aarch64-snapshot.tar.bz2
root@genericarmv8:~# wget http://spicy:8080/net/openjdk8-aarch64-snapshot.tar.bz2
Connecting to spicy:8080 (192.168.1.2:8080)
openjdk8-aarch64-sna 100% |*******************************| 59185k 0:00:00 ETA
root@genericarmv8:~# ls -l openjdk8-aarch64-snapshot.tar.bz2
-rw-r--r-- 1 root root 60606359 Aug 20 15:52 openjdk8-aarch64-snapshot.tar.bz2
root@genericarmv8:~# md5sum openjdk8-aarch64-snapshot.tar.bz2
da71ff0f2630cfb2628c1c4dbb29086e openjdk8-aarch64-snapshot.tar.bz2

and indeed the untar generates the expected error:

I discovered this whilst trying to use bridged networking for bootstrapping the jtreg/openjdk tests (which now breaks that plan).