From owner-freebsd-net@FreeBSD.ORG Mon Jul 18 06:50:28 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 194FC16A41C for ; Mon, 18 Jul 2005 06:50:28 +0000 (GMT) (envelope-from mosfet@planet.eon.net) Received: from priv-edtnes51.telusplanet.net (outbound04.telus.net [199.185.220.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B80743D45 for ; Mon, 18 Jul 2005 06:50:27 +0000 (GMT) (envelope-from mosfet@planet.eon.net) Received: from antioch ([142.179.216.126]) by priv-edtnes51.telusplanet.net (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with SMTP id <20050718065026.IYUU24306.priv-edtnes51.telusplanet.net@antioch>; Mon, 18 Jul 2005 00:50:26 -0600 Message-ID: <000501c58b6d$73a50d60$4b3010ac@antioch> From: "Lee S Clark" To: "Ragnar Lonn" References: <003101c58055$f5eb2110$4b3010ac@antioch> <42CE3E0A.3040304@packetfront.com> Date: Mon, 18 Jul 2005 01:51:05 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Cc: freebsd-net@freebsd.org Subject: Re: EM(4), vlans & dhclient X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jul 2005 06:50:28 -0000 ----- Original Message ----- From: "Ragnar Lonn" To: "Lee S Clark" Cc: Sent: Friday, July 08, 2005 2:49 AM Subject: Re: EM(4), vlans & dhclient > Lee S Clark wrote: > > >- dhclient's interactions with either em(4) or some part of vlan(4) is flakey at best. occasionally all 3 vlan interfaces will obtain an IP, in other instances there is no traffic placed on the wire at all. typically one vlan int will get an IP the other two will not. i suppose this has something to do with em not liking promisc. > > > > > > Yeah, I've had some problems with multiple vlan interfaces too. I had > problems using multiple unique > MAC addresses for the different vlan interfaces on 5.x. The kernel would > drop packets destined for > e.g. vlan interface A that had MAC address X when the underlying > physical network interface had > another MAC address. It seemed easy to patch but we ended up using 4.x > instead anyhow and > there it works fine. > > >- the vlan interfaces _must_ have the same MAC as the parent (em0) otherwise the parent must be in promisc in order for the vlan int to recieve frames destined for it if a unique lladdr is applied. this may seem obvious, but is there a way to alter this behaviour to allow "unicast" MAC forwarding up from the parent to the vlan interfaces without enabling promisc (this might be another request for Linux veth on FreeBSD ;)? our ISP requires MAC registration in order to allocate IPs, one MAC = one IP, period. > > > > > > When we tested on 5.x, I'm fairly sure it didn't work *even if* the > physical interface was in promiscuous > mode. Maybe the behaviour isn't the same for all 5.x versions either. Or > maybe I'm just confused. > > Anyway, if you want to use several MAC addresses on a single physical > interface you have to set > the physical interface to promiscuous mode, AFAIK. Why don't you want to > enable promiscuous > mode? > > You also have to turn off the autosrc flag to keep the physical if from > overwriting the MAC > address of the vlan if on outgoing packets, but you probably knew that. > > You could try installing 4.11 and see how things work there, as a last > resort. > > /Ragnar > Sorry for the delayed reply; vacation. I don't have any particular aversion to promiscuous mode, just personal preference to avoid it. I certainly agree with you, 4.11 is looking very appealing. Thanks for the input! Cheers Lee