From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33)
	id 1BXCd7-0000ii-E0
	for qemu-devel@nongnu.org; Mon, 07 Jun 2004 01:25:05 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33)
	id 1BXCd5-0000iR-QY
	for qemu-devel@nongnu.org; Mon, 07 Jun 2004 01:25:05 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.33) id 1BXCd5-0000iH-PD
	for qemu-devel@nongnu.org; Mon, 07 Jun 2004 01:25:03 -0400
Received: from [206.72.67.39] (helo=claudius.sentinelchicken.org)
	by monty-python.gnu.org with smtp (Exim 4.34) id 1BXCcG-0007Qv-RV
	for qemu-devel@nongnu.org; Mon, 07 Jun 2004 01:24:13 -0400
Date: Sun, 6 Jun 2004 22:24:24 -0700
From: Tim <tim-qemu@sentinelchicken.org>
Subject: Re: [Qemu-devel] NE2K PCI and Windows 98SE & Cirrus Logic
Message-ID: <20040607052424.GD3296@sentinelchicken.org>
References: <40C39F70.5070205@dad-answers.com>
	<1086584098.887.18.camel@shawn.local>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1086584098.887.18.camel@shawn.local>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

> I don't unfortunately have any work-around for the network problems.
> I've also tried a manual network setup using the tun/tap device, but it
> doesn't work any better.

For the most part, network has been working fine for me.  I have used
the linux bridging module, across a real ethernet device and tun0, and
it worked ok.  I am now routing across my host OS (which I have done
before), and it is also working ok.  However, I have noticed that from
time to time my pings time out.  Typically the first one or two pings
when I ping a given host.  After that, it usually works fine for
subsequent pings, though sometimes re-surfaces.  Could it be a timing
issue with the virtual device?  Probably not the problems you are
experiencing Hetz, though worth mentioning.


I am using the most recent CVS (at least, as of this afternoon), and the
following command line:

qemu -pci -m 256 -cdrom win2k-install-cd.img -hda win2k-cow.img -boot c -n "$TUN_SCRIPT"

with the contents of $TUN_SCRIPT being:

sudo ifconfig tun0 192.168.19.1 netmask 255.255.255.0 broadcast 192.168.19.255
sudo sh -c 'echo 1 > /proc/sys/net/ipv4/ip_forward'


I am quite impressed with the momentum this project has had thus far.  I
tell all of my friends about it.  Keep up the good work!

tim