From owner-freebsd-current@freebsd.org  Sat Mar 18 13:45:35 2017
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id C334CD10A27
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Sat, 18 Mar 2017 13:45:35 +0000 (UTC) (envelope-from andy@neu.net)
Received: from mail.neu.net (neu.net [104.225.8.138])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "freebsd-11-64", Issuer "freebsd-11-64" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 8EF78173C
 for <freebsd-current@freebsd.org>; Sat, 18 Mar 2017 13:45:35 +0000 (UTC)
 (envelope-from andy@neu.net)
Received: from neu.net (neu.net [104.225.8.138])
 by mail.neu.net (8.15.2/8.15.2) with ESMTPS id v2IDjWiY060878
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO)
 for <freebsd-current@freebsd.org>; Sat, 18 Mar 2017 09:45:32 -0400 (EDT)
 (envelope-from andy@neu.net)
Date: Sat, 18 Mar 2017 09:45:31 -0400 (EDT)
From: AN <andy@neu.net>
To: freebsd-current@freebsd.org
Subject: DHCP/network issues 
Message-ID: <alpine.BSF.2.20.1703180925320.45657@mail.neu.net>
User-Agent: Alpine 2.20 (BSF 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
X-Spam-Status: No, score=-0.0 required=5.0 tests=RP_MATCHES_RCVD
 autolearn=unavailable autolearn_force=no version=3.4.1
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.neu.net
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/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: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Mar 2017 13:45:35 -0000

Is anyone seeing network or DHCP issues with a recent update to 
12-current?

On new hardware
Dual Core Celeron J1800 Bay Trail 2.4GHz, 2MB L2 Cache
2 Gigabit Ethernet Intel NIC ports

I'm seeing the following issues:

- install latest 12-current snapshot 
FreeBSD-12.0-CURRENT-amd64-20170316-r315413-memstick.img, try DHCP during 
install and it fails.  Setup networking manually and try to ping default gateway results 
in the response
ping: sendto: Host is down

- install 11-stable snapshot, try DHCP IPv4 during install works 
perfectly.  After reboot DHCP works.

Then I did svnlite up to current, buildworld/install cycle and DHCP fails 
again on current.  I tried the whole process twice just to be sure, same 
result.