Public bug reported:
I'm reporting this bug that was resolved upstream in the hopes that it
might be backported to one of the versions of eglibc that is supported
by ubuntu. This is fixed in 2.20 but the most recent version shipped by
ubuntu in any flavor is 2.19.
The upstream report can be
Adding notes from IRC:
* use 'manual eth1' to avoid cloud-init blocking on boot waiting for interfaces
* /etc/network/interfaces originates from a hardcoded file in the image
* cloud-init places /etc/cloud/on-ec2 (or similar) flag file
* on interface add/remove have a rule that fires, checks ec2
Adding notes from IRC:
* use 'manual eth1' to avoid cloud-init blocking on boot waiting for interfaces
* /etc/network/interfaces originates from a hardcoded file in the image
* cloud-init places /etc/cloud/on-ec2 (or similar) flag file
* on interface add/remove have a rule that fires, checks ec2
My current thinking is that a udev rule will need to have a RUN hook
that updates /etc/network/interfaces or at a minimum runs the
appropriate ip commands based on what is discovered in the EC2 metadata
service. It seems like updating /etc/network/interfaces would be good
since ifup/ifdown rely on
My current thinking is that a udev rule will need to have a RUN hook
that updates /etc/network/interfaces or at a minimum runs the
appropriate ip commands based on what is discovered in the EC2 metadata
service. It seems like updating /etc/network/interfaces would be good
since ifup/ifdown rely on
Scott, thanks for the reply. This is not something I need at the moment,
but it does seem like a good way for me to perhaps learn more about
Ubuntu network configuration and udev rules. I did a bit of digging and
found the following files which seem relevant:
/lib/udev/write_net_rules
Scott, thanks for the reply. This is not something I need at the moment,
but it does seem like a good way for me to perhaps learn more about
Ubuntu network configuration and udev rules. I did a bit of digging and
found the following files which seem relevant:
/lib/udev/write_net_rules
Public bug reported:
I booted a c1.medium with ami-3fec7956, 2 interfaces and 2 IPs per
interface. I expected the 4 IPs to be configured on the instance when I
logged in, however only the primary interface had a single IP assigned.
DHCP does not seem to support multiple IPs per interface so the
Public bug reported:
I booted a c1.medium with ami-3fec7956, 2 interfaces and 2 IPs per
interface. I expected the 4 IPs to be configured on the instance when I
logged in, however only the primary interface had a single IP assigned.
DHCP does not seem to support multiple IPs per interface so the
