On Mon, Aug 27, 2012 at 08:53:11AM -0000, Thomas Dreibholz wrote:
> The problem also occurs for my with a freshly-installed Ubuntu Server
> 12.04 (64 bit). The problem seems to be the existence of sub-interfaces.
> If there is eth0:1 (iface eth0:1 inet static) in
> /etc/network/interfaces, an additional waiting time of ~2min is added to
> the boot sequence.
Please file a separate bug report against ifupdown for this; this is a
separate root cause from the other issues that have been reported here.
> Commenting the sub-interface out resolves the delay- problem, but -- of
> course -- does not configure the necessary sub- interface.
As a workaround, you could also avoid the delay by using multiple addresses
on a single interface instead of using subinterfaces, which I believe is now
supported by ifupdown.
On Mon, Aug 27, 2012 at 08:53:11AM -0000, Thomas Dreibholz wrote: interfaces, an additional waiting time of ~2min is added to
> The problem also occurs for my with a freshly-installed Ubuntu Server
> 12.04 (64 bit). The problem seems to be the existence of sub-interfaces.
> If there is eth0:1 (iface eth0:1 inet static) in
> /etc/network/
> the boot sequence.
Please file a separate bug report against ifupdown for this; this is a
separate root cause from the other issues that have been reported here.
> Commenting the sub-interface out resolves the delay- problem, but -- of
> course -- does not configure the necessary sub- interface.
As a workaround, you could also avoid the delay by using multiple addresses
on a single interface instead of using subinterfaces, which I believe is now
supported by ifupdown.