Date: Mon, 25 Jan 2016 13:30:01 -0800 From: Colin Percival <cperciva@freebsd.org> To: Jeremiah Lott <jlott@averesystems.com>, freebsd-cloud@freebsd.org Subject: Re: EC2 Advanced Networking in HEAD Message-ID: <56A693D9.3010304@freebsd.org> In-Reply-To: <CANG7ib83hRcYrUHFgS8uZqwhbqOi6t9hTooYYLUR-fC7%2B6CZ9Q@mail.gmail.com> References: <CANG7ib83hRcYrUHFgS8uZqwhbqOi6t9hTooYYLUR-fC7%2B6CZ9Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. > I am using various r3 instance types in the > us-west-2b AZ. Sometimes when I create an instance, everything works fine > and I get a DHCP lease for my ixv0 device. Other times, ixv0 is probed, but > I never get a DHCP offer (which was the broken behavior from before). > Changing the instance type or stopping/stopping the instance can switch an > instance's NIC from "working" to "non-working" and vice-versa. However, I'm > not convinced it has to do with instance type per-se (changing instance > type changes a lot of things about the underlying hardware). Anyone else > successfully using this latest AMI? Since advanced networking is on by > default now, I'd expect others who are using the AMI to see problems as > well. It worked in my tests, but they were far from exhaustive. (This is why I turned it on in HEAD -- so that everybody else can find the bugs!) -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56A693D9.3010304>