From owner-freebsd-net@FreeBSD.ORG Mon Sep 28 21:38:05 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE0A4106566B for ; Mon, 28 Sep 2009 21:38:05 +0000 (UTC) (envelope-from juli@clockworksquid.com) Received: from mail-pz0-f194.google.com (mail-pz0-f194.google.com [209.85.222.194]) by mx1.freebsd.org (Postfix) with ESMTP id C0ACD8FC0A for ; Mon, 28 Sep 2009 21:38:05 +0000 (UTC) Received: by pzk32 with SMTP id 32so2812951pzk.3 for ; Mon, 28 Sep 2009 14:38:05 -0700 (PDT) MIME-Version: 1.0 Sender: juli@clockworksquid.com Received: by 10.142.209.21 with SMTP id h21mr272285wfg.162.1254172490282; Mon, 28 Sep 2009 14:14:50 -0700 (PDT) In-Reply-To: <6201873e0909281321s51e3d485i1074954d43b657d6@mail.gmail.com> References: <6201873e0909281321s51e3d485i1074954d43b657d6@mail.gmail.com> From: Juli Mallett Date: Mon, 28 Sep 2009 14:14:30 -0700 X-Google-Sender-Auth: 4e5fdbbcc94bd600 Message-ID: To: Adam Vande More Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Cc: freebsd-net@freebsd.org Subject: Re: tap dhcp 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: Mon, 28 Sep 2009 21:38:05 -0000 On Mon, Sep 28, 2009 at 13:21, Adam Vande More wrot= e: > Am I doing something wrong here? That depends on what you're expecting to happen. What do you think tap(4) does and what are you trying to accomplish with using it? Interface bridging controls what happens on packet ingress =97 when a packet comes in on one side of the bridge it is forwarded out the other. When dhclient(8) sends out a DHCPDISCOVER on tap0, that goes through the interface output routine. tap(4) works such that then would go to a user-space process reading from tap0 and then that process would forward it on to somewhere else where eventually it might find a DHCP server. If it does, the DHCP reply would come back, that user-space process would inject it into the kernel and the bridging code would pass it out em0. > kldload if_tap if_bridge > sysctl net.link.tap.user_open=3D1 > ifconfig tap0 create > ifconfig bridge create > ifconfig bridge0 addm tap0 addm em0 > > it# dhclient tap0 > DHCPDISCOVER on tap0 to 255.255.255.255 port 67 interval 6 > DHCPDISCOVER on tap0 to 255.255.255.255 port 67 interval 6 > DHCPDISCOVER on tap0 to 255.255.255.255 port 67 interval 13 > DHCPDISCOVER on tap0 to 255.255.255.255 port 67 interval 18 > DHCPDISCOVER on tap0 to 255.255.255.255 port 67 interval 18 > No DHCPOFFERS received. > No working leases in persistent database - sleeping. > > Although dhclient em0 works as expected. > > FreeBSD it.digitecinc.net 8.0-BETA4 FreeBSD 8.0-BETA4 #2: Mon Sep =A07 > 11:26:25 CDT 2009 > vandemorea@it.digitecinc.net:/usr/obj/usr/src/sys/GENERIC > i386 > > Repost from questions@ several days ago. > > Thanks, > > -- > Adam Vande More > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >