Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 30 Nov 2001 14:40:21 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 30 Nov 2001 14:40:12 -0500 Received: from [212.103.141.42] ([212.103.141.42]:8176 "EHLO godzilla.infohit.si") by vger.kernel.org with ESMTP id convert rfc822-to-8bit; Fri, 30 Nov 2001 14:40:04 -0500 Subject: Device (LAN Cards) Naming Date: Fri, 30 Nov 2001 20:35:14 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 Thread-Topic: Device (LAN Cards) Naming Thread-Index: AcF51tOnL3654OVmEdWK5AACsy5ICg== content-class: urn:content-classes:message From: "Mauricio Culibrk" To: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi to all! *** PLEASE, respond directly to mauricio@infohit.si (I'm not subscribed) *** I have a question about network interface naming in linux 2.4.x or 2.2.x Is it possible to define a name for each interface instead of having eth0, eth1 etc? I'm using a linux box dedicated for routing & filtering and I would like to have descriptive interface names such as: public, private, branch etc... so the output of ifconfig (and all other commands dealing with interfaces) would be more 'concrete' Is it possible? How? Thanks a lot! mauricio *** PLEASE, respond directly to mauricio@infohit.si (I'm not subscribed) *** - 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/