From owner-freebsd-net@FreeBSD.ORG  Thu Sep 22 07:22:47 2005
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
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 AB06116A41F;
	Thu, 22 Sep 2005 07:22:47 +0000 (GMT) (envelope-from lists@yazzy.org)
Received: from mail.yazzy.org (mail.yazzy.org [217.8.140.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4D86343D46;
	Thu, 22 Sep 2005 07:22:47 +0000 (GMT) (envelope-from lists@yazzy.org)
Received: from 217-13-2-82.dd.nextgentel.com ([217.13.2.82] helo=marcin)
	by mail.yazzy.org with esmtps (TLSv1:AES256-SHA:256)
	(YazzY.org) id 1EILPO-0000eO-30; Thu, 22 Sep 2005 09:22:18 +0200
Date: Thu, 22 Sep 2005 09:22:50 +0200
From: Marcin Jessa <lists@yazzy.org>
To: FreeBSD-Current <current@freebsd.org>, FreeBSD-net
	<freebsd-net@freebsd.org>
Message-Id: <20050922092250.55b4716a.lists@yazzy.org>
Organization: YazzY.org
X-Mailer: Sylpheed version 2.0.0 (GTK+ 2.6.8; i386-portbld-freebsd7.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: -2.5 (--)
Cc: 
Subject: tap devices and DHCP.
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Sep 2005 07:22:47 -0000

Hi guys.

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?

Cheers,
Marcin.