From owner-freebsd-hackers Sun May 16 15: 3: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 82BD914C91 for ; Sun, 16 May 1999 15:02:59 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id SAA52023; Sun, 16 May 1999 18:01:39 -0400 (EDT) Message-Id: <199905162201.SAA52023@cs.rpi.edu> To: Bernd Walter Cc: "Justin C. Walker" , Mike Smith , Greg Lehey , "Mark J. Taylor" , Daniel Eischen , freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: ifconfig: changing mac address In-Reply-To: Message from Bernd Walter of "Sun, 16 May 1999 11:48:42 +0200." <19990516114842.A48820@cicely8.cicely.de> Date: Sun, 16 May 1999 18:01:39 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > It seems there's a need, and the possibility. Would somebody like to > > > > suggest a syntax? > > > > > > The precedent would be the socket ioctls SIOCGIFHWADDR and > > > SIOCSIFHWADDR. The Linux emulator suppors the get-only version > > > already. > > It's already been mentioned that some adapters support multiple > > unicast media addresses (the DEC parts; the on-board enets for (most) > > PowerPC Macs; ...). It would be good to support aliases for media > > addresses as well. The 'alias' keyword for ifconfig could be > > overloaded for this, no? The driver could fail the request if it > > didn't support it; or if it has run out of slots for aliases. There > > should also be (I think) a way to tell the driver to go to > > promiscuous mode to emulate this (an "I really want this" request?), > > but I'm not sure it should be the default response to the "set > > hardware address" request. > An alias would be nice. A standby system must be reachable before it > will be active and will need another MAC to be. > But I don't see any sence in having more than one MAC on one IP-Address. > So talking on IP it should be an optional argument to the ip-alias. The linux method reeks of layer violation. I would suggest implimenting AF_LINK and using the already supported SIOC*ADDR routines on the AF_LINK socket. With that those IOCTLs there is already support for getting, setting and adding aliases. We do obviously need to support the other in linux-compat mode. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message