From owner-freebsd-i386@FreeBSD.ORG Fri Oct 30 07:30:07 2009 Return-Path: Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF158106568B for ; Fri, 30 Oct 2009 07:30:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 949638FC08 for ; Fri, 30 Oct 2009 07:30:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n9U7U79v077008 for ; Fri, 30 Oct 2009 07:30:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n9U7U7Mu077000; Fri, 30 Oct 2009 07:30:07 GMT (envelope-from gnats) Date: Fri, 30 Oct 2009 07:30:07 GMT Message-Id: <200910300730.n9U7U7Mu077000@freefall.freebsd.org> To: freebsd-i386@FreeBSD.org From: "Vadim Maksimenko" Cc: Subject: Re: i386/140052: bootonly failure X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vadim Maksimenko List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Oct 2009 07:30:07 -0000 The following reply was made to PR i386/140052; it has been noted by GNATS. From: "Vadim Maksimenko" To: , "Vadim Maksimenko" Cc: Subject: Re: i386/140052: bootonly failure Date: Fri, 30 Oct 2009 09:00:23 +0200 This is a multi-part message in MIME format. ------=_NextPart_000_0006_01CA593F.6A8E68D0 Content-Type: text/plain; charset="windows-1257" Content-Transfer-Encoding: 7bit Dear Sirs, The 8.0-RC2 exposes the same behavior: LAN is working (DHCP request/ack are ok), but no chance to connect anywhere. Yours faithfully, Vadim. ------=_NextPart_000_0006_01CA593F.6A8E68D0 Content-Type: text/html; charset="windows-1257" Content-Transfer-Encoding: quoted-printable

Dear Sirs,

The 8.0-RC2 exposes the same behavior: LAN is = working=20 (DHCP request/ack are ok), but no chance to connect anywhere.

Yours faithfully, Vadim.

------=_NextPart_000_0006_01CA593F.6A8E68D0--