From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33)
	id 1CmLfk-0007J2-Or
	for qemu-devel@nongnu.org; Wed, 05 Jan 2005 19:38:40 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33)
	id 1CmLfj-0007IW-VO
	for qemu-devel@nongnu.org; Wed, 05 Jan 2005 19:38:40 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.33) id 1CmLfj-0007II-R4
	for qemu-devel@nongnu.org; Wed, 05 Jan 2005 19:38:39 -0500
Received: from [213.165.64.20] (helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.34) id 1CmLUG-0001vL-Ew
	for qemu-devel@nongnu.org; Wed, 05 Jan 2005 19:26:48 -0500
Subject: Re: [Qemu-devel] NETDEV WATCHDOG: eth0: transmit timed out
From: Horst Schlonz <horst.schlonz@gmx.de>
In-Reply-To: <20050105213319.GA14108@jbrown.mylinuxbox.org>
References: <1104899444.20758.26.camel@localhost.localdomain>
	<20050105154352.GA11125@jbrown.mylinuxbox.org>
	<1104948769.29588.11.camel@localhost.localdomain>
	<20050105195042.GA13437@jbrown.mylinuxbox.org>
	<1104955592.29588.15.camel@localhost.localdomain>
	<20050105213319.GA14108@jbrown.mylinuxbox.org>
Content-Type: text/plain
Date: Thu, 06 Jan 2005 01:27:21 +0100
Message-Id: <1104971241.29588.46.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, 16:33 -0500 schrieb Jim C. Brown:
> On Wed, Jan 05, 2005 at 09:06:31PM +0100, Horst Schlonz wrote:
> > > Show us what is in your /etc/qemu-ifup script.
> > > 
> > user@host # cat /etc/qemu-ifup
> > #!/bin/sh
> > sudo -p "Password for $0:" /sbin/ifconfig $1 172.20.0.1
> > user@host #
> 
> Yes, you are missing the iptables lines. (Personally I prefer ipchains to
> iptables, but alas ...)
> 
> [script for setting up masquerading snipped]

well, i don't see how masquerading and forwarding will help me in
pinging from guest to host or vice versa. but i did as you say and - as
expected - it does not work. see subject for failure message.

> can you test out that script and see if it works?
> 

actually in the past few days i tried every qemu networking
configuration i could get my hands on. i tried -user-net and vde, i
fiddled with iptables, arp and tcpdump, masquerading, forwarding,
bridging, everything.

after manually filling all arp-caches with correct mac-adresses i can
even see icmp-packet coming out of the guest (with the ususal
WATCHDOG-failure, though). but the icmp-replys never show up in the
guest.

i think, the problem is, that every time network traffic is issued from
or to the guest, it does not work and these failure shows up
in /var/log/messages on the guest:
Jan  5 03:53:14 guest kernel: NETDEV WATCHDOG: eth0: transmit timed out

last hope for me was asking qemu devs on this list, but now i will try
one last thing. ditch the ubuntu-qemu and compile it myself.