Hello Andrew, Apologies for the terse reply in the previous message (it was mainly ment to the submitter to state our workaround, more detailed now):
On Thu, Oct 31, 2013 at 08:23:41AM +0100, Andrew Shadura wrote: > On Thu, 31 Oct 2013 07:50:42 +0100 > Salvatore Bonaccorso <bonac...@ee.ethz.ch> wrote: > > > We have a very similar problem. As workaround in our case to flush the > > addresses in the pre-up iface options worked. So doing in > > /etc/network/interfaces: > > What problem? Elaborate, please. Yes, sure and thanks first of all. I have to do a disclaimer first, we are using this not in production yet as we are on the way trying to achieve a load balancing setup now with IPv6 too with Linux Virtual Server Cluser[1] with IPv6 too on Wheezy based hosts. We had this previously for IPv4 only using lvs-dr (direct routing)[2]. [1] http://www.linuxvirtualserver.org/ [2] http://www.linuxvirtualserver.org/VS-DRouting.html http://www.austintek.com/LVS/LVS-HOWTO/HOWTO/LVS-HOWTO.LVS-DR.html http://www.austintek.com/LVS/LVS-HOWTO/HOWTO/LVS-HOWTO.arp_problem.html The additional IP's on the loopback device for the real servers are needed in this setup, see e.g. [3] (at least the IPv4 approach), for a recent post on the linux-ha list. [3] http://lists.linux-ha.org/pipermail/linux-ha/2013-June/047148.html So we tried to add additional addresses originally in /etc/network/interfaces for the loopback as: iface lo inet6 loopback up ip -6 addr add 2001:db8:0:0:1::1 dev lo which gives the same error message as reported: Sat Nov 2 07:43:37 2013: [....] Configuring network interfaces...RTNETLINK answers: File exists Sat Nov 2 07:43:37 2013: Failed to bring up lo. > > pre-up ip -6 addr flush dev lo > > What are you trying to achieve with this? We added this to workaround this, and ended in having: iface lo inet6 loopback pre-up ip -6 addr flush dev lo up ip -6 addr add 2001:db8:0:0:1::1/64 dev lo resulting finally in # ip -6 addr show dev lo 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 inet6 2001:db8::1:0:0:1/64 scope global valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever > > pre-up /sbin/sysctl --system > /dev/null > > What is this for? This is actually not needed to show a minimal example. My coworker added this only to ensure that when he brings up and down the interface, to assure settings from all system configuration files are read, when playing around with these settings on the /etc/network/interfaces. > Anyway, since recently, you don't need to declare loopback interface at > all. Okay thanks for this hint. Is the above usecase thus wrong approach? Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
