Your message dated Sun, 10 Jan 2016 23:14:29 +0100 with message-id <[email protected]> and subject line Re: ifupdown stops adding static routes when duplicate route is declared has caused the Debian Bug report #570347, regarding ifupdown stops adding static routes when duplicate route is declared to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 570347: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570347 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: ifupdown Version: 0.6.8+nmu1 When the /etc/network/interfaces contains a duplicate static route add statement, the ifupdown stops parsing the static routes with the error message : RTNETLINK answers: File exists Failed to bring up eth0 Here is a sample /etc/netork/interfaces with duplicate route add statement : --------------------------------------------------- auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 10.1.1.1 netmask 255.255.255.0 gateway 10.1.1.254 up ip route add 10.2.1.0/24 via 10.1.1.10 down ip route del 10.2.1.0/24 via 10.1.1.10 up ip route add 10.2.1.0/24 via 10.1.1.10 down ip route del 10.2.1.0/24 via 10.1.1.10 up ip route add 10.2.2.0/24 via 10.1.1.10 down ip route del 10.2.2.0/24 via 10.1.1.10 ---------------------------------------------------- with the file above, the 10.2.2.0 route will never be added to the routing table. could it be possible to get a better message than the RNETLINK file exists answer, and continue parsing the static routes ? I tested this on debian lenny (5.0.2) with kernel 2.6.26-2-686.
--- End Message ---
--- Begin Message ---> When the /etc/network/interfaces contains a duplicate static route add > statement, the ifupdown stops parsing the static routes with the error > message : > > RTNETLINK answers: File exists > Failed to bring up eth0 > > could it be possible to get a better message than the RNETLINK file > exists answer, I'm closing this bug, since it's a very old one. If anything, the bug is in the iproute2 package, because it's the /bin/ip program that produces these unhelpful error messages. > and continue parsing the static routes ? No, it's intended behavior that ifupdown aborts as soon as there is an error. -- Met vriendelijke groet / with kind regards, Guus Sliepen <[email protected]>
signature.asc
Description: Digital signature
--- End Message ---
