From owner-freebsd-xen@FreeBSD.ORG Tue Apr 29 21:20:10 2014 Return-Path: Delivered-To: freebsd-xen@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A664DD1A for ; Tue, 29 Apr 2014 21:20:10 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 87DB61ABC for ; Tue, 29 Apr 2014 21:20:10 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s3TLKAs8029814 for ; Tue, 29 Apr 2014 21:20:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s3TLKACw029813; Tue, 29 Apr 2014 21:20:10 GMT (envelope-from gnats) Date: Tue, 29 Apr 2014 21:20:10 GMT Message-Id: <201404292120.s3TLKACw029813@freefall.freebsd.org> To: freebsd-xen@FreeBSD.org Cc: From: Thomas Zelch Subject: Re: bin/188990: [xen] dhclient(8) does not accept DHCP Offer on FreeBSD 10 as Xen DomU Guest X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Thomas Zelch List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2014 21:20:10 -0000 The following reply was made to PR bin/188990; it has been noted by GNATS. From: Thomas Zelch To: =?iso-8859-1?Q?Roger_Pau_Monn=E9?= Cc: bug-followup@FreeBSD.org, thomaszelch@gmail.com Subject: Re: bin/188990: [xen] dhclient(8) does not accept DHCP Offer on FreeBSD 10 as Xen DomU Guest Date: Tue, 29 Apr 2014 23:11:31 +0200 Hi Roger, I have just tried. When using a different Host for DHCP, everything seems to work fine. Any Ideas why this might be? If the problem is related to PR 188261, is there any way that i might = help narrow the problem down? Thomas Am 26.04.2014 um 10:35 schrieb Roger Pau Monn=E9 : > Could you try to move the DNS server to another host? There have been > reports of failures on if_xn when sending/receiving data to/from other > guests on the same host. >=20 > I know this is not a valid log-term solution, but it could help in > identifying the problem, which is probably related to PR 188261. >=20 > Roger.