From owner-freebsd-net@FreeBSD.ORG Fri Jul 8 08:49:50 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 0CA4716A41C for ; Fri, 8 Jul 2005 08:49:50 +0000 (GMT) (envelope-from raglon@packetfront.com) Received: from mail.packetfront.com (mail.packetfront.com [212.247.6.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F30B43D49 for ; Fri, 8 Jul 2005 08:49:46 +0000 (GMT) (envelope-from raglon@packetfront.com) Received: from localhost (localhost [127.0.0.1]) by mail.packetfront.com (Postfix) with ESMTP id D0C99A3F7D; Fri, 8 Jul 2005 10:49:42 +0200 (CEST) Received: from mail.packetfront.com ([127.0.0.1]) by localhost (mail [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17856-01; Fri, 8 Jul 2005 10:49:42 +0200 (CEST) Received: from [192.168.1.159] (pf-raglon.int.packetfront.com [192.168.1.159]) by mail.packetfront.com (Postfix) with ESMTP id 8B514A3F7B; Fri, 8 Jul 2005 10:49:42 +0200 (CEST) Message-ID: <42CE3E0A.3040304@packetfront.com> Date: Fri, 08 Jul 2005 10:49:14 +0200 From: Ragnar Lonn User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Lee S Clark References: <003101c58055$f5eb2110$4b3010ac@antioch> In-Reply-To: <003101c58055$f5eb2110$4b3010ac@antioch> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at packetfront.com 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: Fri, 08 Jul 2005 08:49:50 -0000 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