From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33)
	id 1CmFpM-0004d3-Gh
	for qemu-devel@nongnu.org; Wed, 05 Jan 2005 13:24:12 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33)
	id 1CmFpL-0004cd-PZ
	for qemu-devel@nongnu.org; Wed, 05 Jan 2005 13:24:11 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.33) id 1CmFpL-0004cI-Du
	for qemu-devel@nongnu.org; Wed, 05 Jan 2005 13:24:11 -0500
Received: from [213.165.64.20] (helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.34) id 1CmFdx-0000F7-Bk
	for qemu-devel@nongnu.org; Wed, 05 Jan 2005 13:12:25 -0500
Subject: Re: [Qemu-devel] NETDEV WATCHDOG: eth0: transmit timed out
From: Horst Schlonz <horst.schlonz@gmx.de>
In-Reply-To: <20050105154352.GA11125@jbrown.mylinuxbox.org>
References: <1104899444.20758.26.camel@localhost.localdomain>
	<20050105154352.GA11125@jbrown.mylinuxbox.org>
Content-Type: text/plain
Date: Wed, 05 Jan 2005 19:12:49 +0100
Message-Id: <1104948769.29588.11.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
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

Am Mittwoch, den 05.01.2005, 10:43 -0500 schrieb Jim C. Brown:
> On Wed, Jan 05, 2005 at 05:30:44AM +0100, Horst Schlonz wrote:
> > the problem is:
> > root@guest # ping -c1 172.20.0.1
> > PING 172.20.0.1 (172.20.0.1) 56(84) bytes of data
> > NETDEV WATCHDOG: eth0: transmit timed out
> > NETDEV WATCHDOG: eth0: transmit timed out
> > >From 172.20.0.2 icmp_seq=1 Destination Host Unreachable
> > 
> > --- 172.20.0.1 ping statistics ---
> > 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
> > root@guest #
> > 
> > can anyone confirm this? is something wrong with the emulated
> > realtek-network-device?
> > 
> 
> Looks like you may need to set up iptables. E.g. make sure the kernel firewall
> isn't blocking it.
> 
> Also possible that you are using the wrong driver in the guest OS, so it doesn't
> see the ethernet card.
> 

so, this is supposed to work, right? does it work for you? or am i
missing something here? i have tried various drivers (kernels, indeed).
suse 9.2, latest knoppix...   same problem there.

maybe it's the tun-driver of my host kernel. i have ubuntu hoary with
stock kernel 2.6.9-1-686 here. firewall tables are all clean on host and
guest, i have checked this already with iptables -L.