I think consistent device names were mainly meant for laptops etc where a range of different interfaces popping in and out is a common use case. Servers are more or less the opposite.
Btw my NAT script now works great across stretch and buster, and also Ubuntu xenial/bionic work. Thx On Sat, 19 Oct 2019 at 07:35, Stephen Gelman <[email protected]> wrote: > On Oct 17, 2019, at 5:53 PM, Noah Meyerhans <[email protected]> wrote: > > Can you explain why this causes problems for you? We want to keep device > > renaming enabled for consistency with standard Debian installations, and > > we aren't aware of specific problems with it that necessitate it being > > disabled. > > Noah, > > I have found when testing buster AMIs that the consistent device naming is > unpredictable and different for different instance types. This is > generally tough for us to standardize configs with configuration > management. Yes, I am aware that I can dynamically look up the interface > but it adds an extra layer of complexity that we have found unnecessary. > This post on the AWS forums describes similar frustration using an ubuntu > image: https://forums.aws.amazon.com/thread.jspa?threadID=263125. > > Stephen > -- Sent from a mobile device - please excuse the brevity, spelling and punctuation.
