From owner-freebsd-ports@FreeBSD.ORG  Fri May 12 07:02:27 2006
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
X-Original-To: freebsd-ports@freebsd.org
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6598A16A403
	for <freebsd-ports@freebsd.org>; Fri, 12 May 2006 07:02:27 +0000 (UTC)
	(envelope-from sem@FreeBSD.org)
Received: from relay-er5.mbrd.ru (relay-er5.mbrd.ru [194.117.71.33])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E22FC43D48
	for <freebsd-ports@freebsd.org>; Fri, 12 May 2006 07:02:26 +0000 (GMT)
	(envelope-from sem@FreeBSD.org)
Received: from msd.mbrd.ru ([172.16.33.193])
	by relay-er5.mbrd.ru with esmtpa (Exim 4.x) id 1FeRfN-000LyP-6S
	for freebsd-ports@freebsd.org; Fri, 12 May 2006 11:02:25 +0400
Message-ID: <44643300.8070104@FreeBSD.org>
Date: Fri, 12 May 2006 11:02:24 +0400
From: Sergey Matveychuk <sem@FreeBSD.org>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: freebsd-ports@freebsd.org
X-Enigmail-Version: 0.93.2.0
Content-Type: text/plain; charset=KOI8-R
Content-Transfer-Encoding: 7bit
Subject: isc-dhcp-server problem - need help to explore
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 May 2006 07:02:27 -0000

There are a few reports isc-dhcp-server 3.0.4 does not give out a
newtwork info (IP addresses) to Windows XP clients when 3.0.3 did.

I and the port maintainer have no such problem.

Who have the problem, could you provide more detailed info please?
dhcp.conf, tcpdump output etc.

Just "does not work" reports are useless.

Thanks.
-- 
Sem.