On 5/12/19 8:07 am, Noah Meyerhans wrote:
T2 instances are based on Xen and use the Xen netfront (vif) interface.
These interfaces aren't PCI devices, so udev can't generate a name based
on the PCI bus ID. Compare the 'udevadm info' output for a t2 with that
of a t3. Because Debian doesn't
On Wed, Dec 04, 2019 at 01:16:27PM +1100, paul wrote:
> I'm reworking my old VPN server, and will use the Debian 10 AMI in AWS. I've
> noticed that predictable network interface names are enabled for t3 servers,
> but not t2 - I have test setup on a t2.micro and a t3.micro, and only the t3
> has
Hi folks,
I'm reworking my old VPN server, and will use the Debian 10 AMI in AWS.
I've noticed that predictable network interface names are enabled for t3
servers, but not t2 - I have test setup on a t2.micro and a t3.micro,
and only the t3 has predictable interface names. I'm trying to write
