Date: Mon, 25 Jan 2016 16:51:46 -0500 From: Jeremiah Lott <jlott@averesystems.com> To: Colin Percival <cperciva@freebsd.org> Cc: freebsd-cloud@freebsd.org Subject: Re: EC2 Advanced Networking in HEAD Message-ID: <CANG7ib_7qeG4oEM6t6kFCyeqLEc7O=7MnG4PjKizZJNoYSLyMQ@mail.gmail.com> In-Reply-To: <56A693D9.3010304@freebsd.org> References: <CANG7ib83hRcYrUHFgS8uZqwhbqOi6t9hTooYYLUR-fC7%2B6CZ9Q@mail.gmail.com> <56A693D9.3010304@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 25, 2016 at 4:30 PM, Colin Percival <cperciva@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANG7ib_7qeG4oEM6t6kFCyeqLEc7O=7MnG4PjKizZJNoYSLyMQ>