From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:53755) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QKm2Q-0007qX-PT for qemu-devel@nongnu.org; Fri, 13 May 2011 02:39:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QKm2P-00006o-Jw for qemu-devel@nongnu.org; Fri, 13 May 2011 02:39:50 -0400 Received: from fmmailgate01.web.de ([217.72.192.221]:55473) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QKm2P-000063-3m for qemu-devel@nongnu.org; Fri, 13 May 2011 02:39:49 -0400 Message-ID: <4DCCD223.90504@web.de> Date: Fri, 13 May 2011 08:39:31 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <4DCB486F.70509@landley.net> <4DCC8523.2000501@landley.net> <4DCC8E21.3030405@landley.net> In-Reply-To: <4DCC8E21.3030405@landley.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig785FFA1895EC9655D7215E5F" Sender: jan.kiszka@web.de Subject: Re: [Qemu-devel] -net interface association behavior change in current -git. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Rob Landley Cc: blauwirbel@gmail.com, Vincent Palatin , qemu-devel@nongnu.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig785FFA1895EC9655D7215E5F Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2011-05-13 03:49, Rob Landley wrote: > On 05/12/2011 08:19 PM, Vincent Palatin wrote: >>>> First of all, as you have 2 totally separated subnets in your setup,= I >>>> think your command-line should use "vlan=3D" parameter to isolate th= em, >>>> else you will end up with some random routing/broadcasting (and rand= om >>>> tends to change over time). >>> >>> Does the kernel need some sort of vlan support compiled into it for t= his >>> to work, or can the kernel not care? >> >> You don't need anything in your kernel, this is for Qemu network layer= >> configuration. >=20 > Oh good. (The kernel has a couple different VLAN config options, plus > cisco has vlan stuff in its routers... I've been trying not to get any= > of this complexity on me.) >=20 >>>> In my understanding, the Linux kernel might assign interface number >>>> depending on the order the interfaces are appearing. >>> >>> It's going in PCI bus order. And the _interfaces_ are still happily = in >>> PCI bus order both before and after this commit. What's changing is = the >>> association between interface and -net user or -net tap. >>> >>> The first one, with macaddr 11:11:11, is always eth0. But before the= >>> patch, eth0 is -net user, and after the patch eth0 is -net tap. >> >> So, did you try the vlan parameter which is supposed to associate each= >> interface with the proper thing (IMO the command line order should not= >> have anything to do with it) ? >=20 > Apparently you cannot stick a vlan on -redir, and if you do the error > message is a bit funky (cannot initialize -net user). Good to know... >=20 > Yup, that fixed it. Thanks. >=20 > By the way, does -redir only apply to -net user? -redir (like all the other free-standing usernet switches) is legacy as it can only be applied to a single usernet instance. And it's highly confusing to which it refers. That's also documented in the man page. > Actually, reading qemu > --help it looks like I should be using hostfwd=3D but the documentation= on > that is REALLY WEIRD: >=20 > This option can not be given multiple times, but multiple rules may > be combined. Where did you find this? A quick grep did not reveal the location to me. qemu-options.hx states it clearly: @item hostfwd=3D[tcp|udp]: [...] This option can be given multiple times. Jan --------------enig785FFA1895EC9655D7215E5F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk3M0iMACgkQitSsb3rl5xSIzgCfepefGNlxTSesjITAx+qRpjcH pWYAn1+Bey7av6BiQwprKXlKn0SH5EcT =E7sG -----END PGP SIGNATURE----- --------------enig785FFA1895EC9655D7215E5F--