Bug#834376: ifupdown: boot console says 'Failed to start Raise network interfaces' yet interface is up

On Aug 17, 2016, at 12:09 AM, Guus Sliepen wrote: > What you then have to do is clean up after the > kernel, by adding the following to /etc/network/interfaces: > > pre-up ip -6 a flush dev $IFACE mngtmpaddr > > You can add this to either the inet or inet6 stanza.

Bug#834376: ifupdown: boot console says 'Failed to start Raise network interfaces' yet interface is up

On Tue, Aug 16, 2016 at 11:50:33PM -0700, Rick Thomas wrote: > It may be worth noting that after “updateinitramfs -u” I don’t see > /etc/sysctl.conf in the new initrd file: > > > root@sheeva:~# lsinitramfs -l /boot/initrd.img | grep sysctl > > -rwxr-xr-x 205 root root0 Apr 17

Bug#834376: ifupdown: boot console says 'Failed to start Raise network interfaces' yet interface is up

It may be worth noting that after “updateinitramfs -u” I don’t see /etc/sysctl.conf in the new initrd file: > root@sheeva:~# lsinitramfs -l /boot/initrd.img | grep sysctl > -rwxr-xr-x 205 root root0 Apr 17 15:03 sbin/sysctl So if the kernel is picking up the RA before

Bug#834376: ifupdown: boot console says 'Failed to start Raise network interfaces' yet interface is up

On Aug 16, 2016, at 4:51 PM, Guus Sliepen wrote: > On Tue, Aug 16, 2016 at 03:56:56PM -0700, Rick Thomas wrote: > >>> Another option is to add the following line to /etc/systl.conf: >>> >>> net.ipv6.conf.all.accept_ra=0 >> >> Do I understand correctly that I should use

Bug#834376: ifupdown: boot console says 'Failed to start Raise network interfaces' yet interface is up

On Tue, Aug 16, 2016 at 03:56:56PM -0700, Rick Thomas wrote: > > Another option is to add the following line to /etc/systl.conf: > > > > net.ipv6.conf.all.accept_ra=0 > > Do I understand correctly that I should use this if I want to assign a static > IPv6 address that is *not* the same

Bug#834376: ifupdown: boot console says 'Failed to start Raise network interfaces' yet interface is up

> On Aug 16, 2016, at 1:57 PM, Guus Sliepen wrote: > > On Tue, Aug 16, 2016 at 01:07:15PM -0700, Rick Thomas wrote: > >> Thanks Pascal! > > Indeed thanks, now I have less explaining to do :) And thank you Guus :) Now I understand a lot more than I did. > Another option is

Bug#834376: ifupdown: boot console says 'Failed to start Raise network interfaces' yet interface is up

On Tue, Aug 16, 2016 at 01:07:15PM -0700, Rick Thomas wrote: > Thanks Pascal! Indeed thanks, now I have less explaining to do :) > >> Aug 14 17:02:41 sheeva systemd[1]: Starting Raise network interfaces... > >> Aug 14 17:02:46 sheeva ifup[893]: /sbin/ifup: waiting for lock on > >>

Bug#834376: ifupdown: boot console says 'Failed to start Raise network interfaces' yet interface is up

Thanks Pascal! On Aug 16, 2016, at 12:59 AM, Pascal Hambourg wrote: > Le 16/08/2016 à 09:03, Rick Thomas a écrit : >> >> Aug 14 17:02:41 sheeva systemd[1]: Starting Raise network interfaces... >> Aug 14 17:02:46 sheeva ifup[893]: /sbin/ifup: waiting for lock on >>

Bug#834376: ifupdown: boot console says 'Failed to start Raise network interfaces' yet interface is up

Package: ifupdown Version: 0.8.13 Severity: normal Dear Maintainer, Updated to latest debian Sid See attached screenlog of boot. note error message quoted in subject line After boot is completed we see: rbthomas@sheeva:~$ systemctl status networking.service * networking.service - Raise