Bug#846583: cloud.debian.org: AWS Image should enable DHCPv6 client

2016-12-14 Thread Noah Meyerhans
On Wed, Dec 14, 2016 at 08:17:28AM +0100, Thomas Lange wrote: > I wonder why you need to source /usr/lib/fai/subroutines for importing > the ifclass subroutine. If your scripts are bash scripts, this > function should be already available. Hm. I have no idea why I thought that would be necessary.

Bug#846583: cloud.debian.org: AWS Image should enable DHCPv6 client

2016-12-13 Thread Thomas Lange
I wonder why you need to source /usr/lib/fai/subroutines for importing the ifclass subroutine. If your scripts are bash scripts, this function should be already available. -- regards Thomas

Bug#846583: cloud.debian.org: AWS Image should enable DHCPv6 client

2016-12-13 Thread Noah Meyerhans
On Sat, Dec 10, 2016 at 08:57:22PM +0100, Bernhard Schmidt wrote: > I don't think this will ever be fixed with ifupdown. I think > systemd-networkd and NetworkManager do the right thing here, but I have > never had a look at either for maintaining a _server_. So I will not > propose switching to th

Bug#846583: cloud.debian.org: AWS Image should enable DHCPv6 client

2016-12-10 Thread Noah Meyerhans
On Sat, Dec 10, 2016 at 04:31:23PM -0500, Sam Hartman wrote: > I've played with systemd-networkd a bit. > It seems capable enough to handle this use case, but it has some > significant drawbacks. I've looked in to systemd-networkd in the stretch images, but haven't managed to get it to acquire a D

Bug#846583: cloud.debian.org: AWS Image should enable DHCPv6 client

2016-12-10 Thread Sam Hartman
I've played with systemd-networkd a bit. It seems capable enough to handle this use case, but it has some significant drawbacks. It's not very backward compatible with expected sysadmin patterns. That is, as a sysadmin, I'd expect ifup and ifdown to work. I expect to be able to do things like ifd

Bug#846583: cloud.debian.org: AWS Image should enable DHCPv6 client

2016-12-10 Thread Bernhard Schmidt
On Thu, Dec 08, 2016 at 10:23:22PM -0800, Noah Meyerhans wrote: Hi Noah, > On Fri, Dec 02, 2016 at 12:25:44PM +0100, Bernhard Schmidt wrote: > > thanks for providing an AWS EC2 Image with Debian Jessie. > > > > AWS is now supporting IPv6 on EC2 instances, see > > > > > > https://aws.amazo

Bug#846583: cloud.debian.org: AWS Image should enable DHCPv6 client

2016-12-10 Thread Anders Jackson
2016-12-09 7:23 GMT+01:00 Noah Meyerhans : > On Fri, Dec 02, 2016 at 12:25:44PM +0100, Bernhard Schmidt wrote: > > thanks for providing an AWS EC2 Image with Debian Jessie. > > > > AWS is now supporting IPv6 on EC2 instances, see > > > > https://aws.amazon.com/de/blogs/aws/new-ipv6-support-f

Bug#846583: cloud.debian.org: AWS Image should enable DHCPv6 client

2016-12-08 Thread Noah Meyerhans
On Thu, Dec 08, 2016 at 10:23:22PM -0800, Noah Meyerhans wrote: > > For this /etc/network/interfaces needs to be amended with > > > > iface eth0 inet6 dhcp > > Unfortunately this breaks networking for instances in subnets with IPv6 > *disabled*, which is likely the vast majority of them for the f

Bug#846583: cloud.debian.org: AWS Image should enable DHCPv6 client

2016-12-08 Thread Noah Meyerhans
On Fri, Dec 02, 2016 at 12:25:44PM +0100, Bernhard Schmidt wrote: > thanks for providing an AWS EC2 Image with Debian Jessie. > > AWS is now supporting IPv6 on EC2 instances, see > > > https://aws.amazon.com/de/blogs/aws/new-ipv6-support-for-ec2-instances-in-virtual-private-clouds/. > >

Bug#846583: cloud.debian.org: AWS Image should enable DHCPv6 client

2016-12-02 Thread Bernhard Schmidt
Package: cloud.debian.org Severity: minor User: cloud.debian@packages.debian.org Usertags: aws Hi, thanks for providing an AWS EC2 Image with Debian Jessie. AWS is now supporting IPv6 on EC2 instances, see https://aws.amazon.com/de/blogs/aws/new-ipv6-support-for-ec2-instances-in-v