From owner-freebsd-cloud@freebsd.org Mon Jan 25 21:51:49 2016 Return-Path: Delivered-To: freebsd-cloud@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 D6A5FA458FB for ; Mon, 25 Jan 2016 21:51:49 +0000 (UTC) (envelope-from jlott@averesystems.com) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 732D48FE for ; Mon, 25 Jan 2016 21:51:49 +0000 (UTC) (envelope-from jlott@averesystems.com) Received: by mail-wm0-x233.google.com with SMTP id 123so83307106wmz.0 for ; Mon, 25 Jan 2016 13:51:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=averesystems.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0FiRQCghxiyBpGZVatT/dYKzoUcqPpEjlBQgt2S0G2g=; b=OeU7x8E3wZNoJf1H8ALbhMh/hd3RJ4LRtkf5JUpXz38DGTOuaZ9dEXz+dTwWqB+dcQ 6497pkK3QxSsrQpGWem2TQXUplLOLp8h43ChHuruXoBbZtsFv3XNd8LpeZYyjrJCU5wD u0eFuEIpWeNNIPKxnVgKaNn/m77zYid7VIpXs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=0FiRQCghxiyBpGZVatT/dYKzoUcqPpEjlBQgt2S0G2g=; b=Nk5+7FjzZvSPm4LXFOuzDgsiEgs5ddkaOTriyCqaH0YWrx+CF/PtZ2LxBtcSjTkTE+ CmLOBNzNZoWfL6WM3bwFPXGHr5/ASgOudolHTHmAM4hP9MghdtBsUesYtJJI2eR7P3T0 iIWKD+fs2OYdAT0DDF1uCq0mrEzY3fPZmhpH8YRLCpGJtIu8pKi4TRlz+3zGcUeRZyjy PqPyj50LUTB13KlTX/gEQGCmd87OvwphEwsIhZPQ10PF9blTx0s7iafKnM5rrNZW1n7r b1GyVh8s7ycm+VYkvaRhWb8cFeFxw7PbL46ta3gnhJprE6p4O3F8pgBEbHt7xbSMqCMQ s40g== X-Gm-Message-State: AG10YORru67O09U+asj+VnI3NYlGxO/3f0zSKQI6Q6m67W+HVwKODqEM47vO0BGii/L5wWHJWzlo9cffIdUdTlgy MIME-Version: 1.0 X-Received: by 10.194.192.198 with SMTP id hi6mr19782604wjc.141.1453758706593; Mon, 25 Jan 2016 13:51:46 -0800 (PST) Received: by 10.27.176.95 with HTTP; Mon, 25 Jan 2016 13:51:46 -0800 (PST) In-Reply-To: <56A693D9.3010304@freebsd.org> References: <56A693D9.3010304@freebsd.org> Date: Mon, 25 Jan 2016 16:51:46 -0500 Message-ID: Subject: Re: EC2 Advanced Networking in HEAD From: Jeremiah Lott To: Colin Percival Cc: freebsd-cloud@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "FreeBSD on cloud platforms \(EC2, GCE, Azure, etc.\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jan 2016 21:51:50 -0000 On Mon, Jan 25, 2016 at 4:30 PM, Colin Percival wrote: > On 01/25/16 13:16, Jeremiah Lott wrote: > > I'm having very inconsistent results using the latest 11.0-CURRENT > snapshot > > AMI "FreeBSD 11.0-CURRENT-amd64-2016-01-22 (ami-0b95716b)". A pretty high > > percentage of the time (I'd say at least 50%), networking does not work > > when I create an instance. > > Just to rule out the obvious: Sometimes I accidentally launch instances > into > VPC subnets which default to not assigning public IP addresses. > We use a VPN. I definitely think the instance itself is configured correctly, because I can have a working instance, and I just stop/start it (not a reboot, have to actually do "stop"), then it will sometimes stop working. Sometimes I have an instance that is not working, and a start/stop "fixes" it. You can also see in the "System Log" (eventually) that the DHCP is failing to get an offer for its private IP when it is "broken". The behavior appears to have some correlation to instance type, with r3.large and r3.xlarge working much more often than any of the larger r3 instance types. However, I've done this long enough that I know that this apparent pattern in instance types could easily just be coincidence. Short snippet from a "broken" instance: Starting dhclient. ixv0: link state changed to UP DHCPREQUEST on ixv0 to 255.255.255.255 port 67 DHCPREQUEST on ixv0 to 255.255.255.255 port 67 DHCPDISCOVER on ixv0 to 255.255.255.255 port 67 interval 8 DHCPDISCOVER on ixv0 to 255.255.255.255 port 67 interval 11 DHCPDISCOVER on ixv0 to 255.255.255.255 port 67 interval 14 DHCPDISCOVER on ixv0 to 255.255.255.255 port 67 interval 17 DHCPDISCOVER on ixv0 to 255.255.255.255 port 67 interval 11 No DHCPOFFERS received. When it works correctly, you will get an DHCPACK on the first request. Jeremiah