From owner-freebsd-current@FreeBSD.ORG Sun Oct 24 14:06:56 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ACBAB1065673 for ; Sun, 24 Oct 2010 14:06:56 +0000 (UTC) (envelope-from wxs@atarininja.org) Received: from syn.atarininja.org (syn.csh.rit.edu [129.21.49.45]) by mx1.freebsd.org (Postfix) with ESMTP id 86FE18FC14 for ; Sun, 24 Oct 2010 14:06:56 +0000 (UTC) Received: by syn.atarininja.org (Postfix, from userid 1001) id A1E475C3B; Sun, 24 Oct 2010 09:47:42 -0400 (EDT) Date: Sun, 24 Oct 2010 09:47:42 -0400 From: Wesley Shields To: KOT MATPOCKuH Message-ID: <20101024134742.GA78060@atarininja.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Current Subject: Re: ports/151636: net/isc-dhcp31-server and net/isc-dhcp41-server does not work with VLAN interfaces X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Oct 2010 14:06:56 -0000 On Fri, Oct 22, 2010 at 11:48:19AM +0400, KOT MATPOCKuH wrote: > Hi all! > > I got another problem with latest kernel: net/isc-dhcp31-server not > started on VLAN interface with message: > Internet Systems Consortium DHCP Server 4.1.1-P1 > Copyright 2004-2010 Internet Systems Consortium. > All rights reserved. > For info, please visit https://www.isc.org/software/dhcp/ > Wrote 0 deleted host decls to leases file. > Wrote 0 new dynamic host decls to leases file. > Wrote 64 leases to leases file. > Unsupported device type 135 for "bge1.48" > > I tried to update dhcpd to net/isc-dhcp41-server, but without result. > > I attached a patch for net/isc-dhcp41-server , but not sure is it correct. > I think a similar change should solve the problem for net/isc-dhcp31-server... I'll go ahead and update the port with this change today. In the future you should contact the maintainer of the port, along with using the ports@ list, so that this kind of stuff doesn't get lost in mailing lists. Lastly, you should feed this patch upstream if you have not already. -- WXS