Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756550Ab2BHGnR (ORCPT ); Wed, 8 Feb 2012 01:43:17 -0500 Received: from lennier.cc.vt.edu ([198.82.162.213]:58228 "EHLO lennier.cc.vt.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756117Ab2BHGnP (ORCPT ); Wed, 8 Feb 2012 01:43:15 -0500 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3-dev To: Kay Sievers Cc: Henrique de Moraes Holschuh , Jiri Slaby , "Eric W. Biederman" , Greg KH , LKML , ML netdev Subject: Re: network regression: cannot rename netdev twice In-Reply-To: Your message of "Wed, 08 Feb 2012 04:50:15 +0100." From: Valdis.Kletnieks@vt.edu References: <4F27120A.4040106@suse.cz> <4F27C54F.1010107@suse.cz> <20120204021457.GA25386@khazad-dum.debian.net> <20120208020038.GE13296@khazad-dum.debian.net> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1328683324_3347P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Wed, 08 Feb 2012 01:42:04 -0500 Message-ID: <14373.1328683324@turing-police.cc.vt.edu> X-Mirapoint-Received-SPF: 198.82.161.152 auth3.smtp.vt.edu Valdis.Kletnieks@vt.edu 2 pass X-Junkmail-Status: score=10/50, host=zidane.cc.vt.edu X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A020205.4F321940.00B9,ss=1,re=0.000,fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=single engine X-Junkmail-IWF: false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2756 Lines: 67 --==_Exmh_1328683324_3347P Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable On Wed, 08 Feb 2012 04:50:15 +0100, Kay Sievers said: > After years of working in that area I will stop to work on these hacks > to promise stable ethX names. It was just wrong, like enumerations > always are in hotplug setups. So (real world case) I've got a server that's got a 1G ethernet connected= to the public net, a 1G ethernet that's a cluster management network, and a 10G ethernet that connects to our HPC clusters. And I want to add iptables rules that distinguish based on interface. Cur= rently I can nail the management net to eth0, the public net to eth1, and the 10= G to eth2, and then just add =22-i eth1=22 or whatever in the iptables ruleset= . I really don't care if the 0/1/2 move around - but if we're not having na= iled-down interface names, what will take the place of '-i ethN' in iptables? > People who need predictable interface names should just manually > configure custom/descriptive names, or names which are reliably > derived from the hardware, like firmware-provided names or the pci > slot number. Or is this sort of thing in /etc/udev/rules.d/70-persistent-net.rules SUBSYSTEM=3D=3D=22net=22, ACTION=3D=3D=22add=22, DRIVERS=3D=3D=22?*=22, A= TTR=7Baddress=7D=3D=3D=2200:25:90:0b:f2:80=22, ATTR=7Btype=7D=3D=3D=221= =22, KERNEL=3D=3D=22eth*=22, NAME=3D=22eth0=22 what you are trying to move to, and my systems are already onboard and I should just move along, nothing to see here? ;) --==_Exmh_1328683324_3347P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Exmh version 2.5 07/13/2001 iQIVAwUBTzIZOwdmEQWDXROgAQKFqhAAoqjjoFtAHfddKC06dWIBUikCHPFK90ny cvg8HEMxVcIZBJBUGpXxm8jA9u1Q2GouJ1aYhp4tIQMsN7GjLqKLCPKI+Re1ePDW 4nGSMcGWKY4iE6pWtbmhQfsrcPJtvxgUQCgwAfU5+sTEpBcaoFglA3wvN4WCGrbM +UzMqwW/E6vuKDn4QY8q6Nc7WqgiDbDaW1ZxRKP2zkY2/Y23u2eY6AfAwj2XV+1c ft9EmB8fkTwdAYuGY8pWpyN+WKm6H2sAYHggqqxi8PL2Jfw87hNZkJsLFByxldSY pyDK86pOjG1z88Tq3ZXXxx5RkXx/+ZA3QLpSjKg4TDXkoK9gW8RGWs0WYKHa4biv VfJFzSem83f31xds+xjKKYkTr4jEyRT/ybfZ2frCagSrr8HDXgR3WhgwqW2N82HV ECCCE7HGLYzsxb92KsIyVKqosY+OYCQelYmheRnU5sRQvnFfJiTrWExBUs12iSgX eo0W8RbaQBG+8uJU8N3p2ZFD62/BOyLaoly16/7MJcyghmvEv4QP/yH8Nz3ORHpV IKJvhSKfiSDBld3ca3+/jE3fhWrVjueLxWcTYHvOmNHvV+Xww8sO/rl0W7x0dnvb cgAGJZxwd/y5BQOx9V1SGReRYm3zpx8wvgL9OuRXUcmMsxU2AM3akwznfCmeMqRU RIPoEEwC6Jw= =JUGY -----END PGP SIGNATURE----- --==_Exmh_1328683324_3347P-- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/