From owner-freebsd-current@FreeBSD.ORG  Thu Sep 22 10:35:07 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: current@freebsd.org
Delivered-To: freebsd-current@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2DE6F16A41F;
	Thu, 22 Sep 2005 10:35:07 +0000 (GMT)
	(envelope-from rwatson@FreeBSD.org)
Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D7F2043D45;
	Thu, 22 Sep 2005 10:35:06 +0000 (GMT)
	(envelope-from rwatson@FreeBSD.org)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by cyrus.watson.org (Postfix) with ESMTP id 3D41B46B4D;
	Thu, 22 Sep 2005 06:35:06 -0400 (EDT)
Date: Thu, 22 Sep 2005 11:35:06 +0100 (BST)
From: Robert Watson <rwatson@FreeBSD.org>
X-X-Sender: robert@fledge.watson.org
To: Marcin Jessa <lists@yazzy.org>
In-Reply-To: <20050922092250.55b4716a.lists@yazzy.org>
Message-ID: <20050922113336.K34322@fledge.watson.org>
References: <20050922092250.55b4716a.lists@yazzy.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: FreeBSD-net <freebsd-net@freebsd.org>,
	FreeBSD-Current <current@freebsd.org>
Subject: Re: tap devices and DHCP.
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Sep 2005 10:35:07 -0000


On Thu, 22 Sep 2005, Marcin Jessa wrote:

> I do not know if it's meant to be that way but tap devices cannot get 
> IPs assigned with DHCP. I did not check the old dhclient code but the 
> new one cannot hand over DHCP requests to tap devices. I was sure a tap 
> device acted as an ethernet device even though it's a virtual one, since 
> one can manually assign IP to tap. It can however assign IP to a bridge 
> (with DHCP) with dev tap as a member of it. Could someone explain me 
> please if this behaviour is on purpose or just a problem with DHCP?

That's certainly undesirable.  Could you tell us a little bit about the 
setup you're running?  Specifically, what's on the other end of the tap 
device, and how does it hook up to the DHCP server?

Could you show the ifconfig output for the interface before and after 
running dhclient?  And then again after manually assigning an address?

Thanks,

Robert N M Watson