FS#16114 - [initscripts] net: wrong error message when using multiple IPv6 on one NIC

Attached to Project: Arch Linux
Opened by Nicolas Doualot (slubman) - Wednesday, 09 September 2009, 21:22 GMT
Last edited by Tom Gundersen (tomegun) - Sunday, 08 May 2011, 13:01 GMT
Task Type Bug Report
Category Arch Projects
Status Closed
Assigned To Aaron Griffin (phrakture)
Thomas Bächler (brain0)
Tom Gundersen (tomegun)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Using IPv6 and IPv4, I've configured my rc.conf to assign multiple IPv6 adress to one NIC (and use DHCP in v4).
The config works, but on boot I got error messages relating to the lines where I set the IPv6 address


Additional info:
* package version(s) :
initscripts 2009.08-1
net-tools 1.60-14

* config and/or log files etc.

in /etc/rc.conf :

eth0="dhcp"
eth0_ipv6_0="eth0 add fd8d::3/64"
eth0_ipv6_1="eth0 add 2a01:XXXX:XXXX::3/64"
INTERFACES=(eth0 eth0_ipv6_1 eth0_ipv6_0)


error messages displayed on startup:
eth0_ipv6_0 no such device
eth0_ipv6_1 no such device

But, the interface are configured correctly when the boot is finished.
This task depends upon

Closed by  Tom Gundersen (tomegun)
Sunday, 08 May 2011, 13:01 GMT
Reason for closing:  No response
Comment by Aaron Griffin (phrakture) - Thursday, 24 September 2009, 21:49 GMT
http://projects.archlinux.org/?p=initscripts.git;a=commitdiff;h=acac4f47597320f55995bdaf692d6f2335a1d67e
Comment by Nicolas Doualot (slubman) - Saturday, 03 October 2009, 06:53 GMT
  • Field changed: Percent Complete (100% → 0%)
Now there is no error message for the eth0_ipv6* lines, but There an error message:

dhcp: unknown interface: no such device
Comment by Aaron Griffin (phrakture) - Monday, 05 October 2009, 21:47 GMT
Fixed again:
http://projects.archlinux.org/?p=initscripts.git;a=commitdiff;h=743745339502da513cce7acbc9b67fbce4378091
Comment by adam stokes (boris) - Tuesday, 15 December 2009, 17:41 GMT
When bringing down an interface with attached ip aliases the initscript will still attempt to bring down those aliased devices even though the parent interface is already down which causes the initscript to return with a false status.

the way i've gotten around that is to ignore aliases on ifdown all together

`echo ${1} | grep -q '_'`
if [ $? -gt 0 ]; then
/sbin/ifconfig ${1} down >/dev/null 2>&1
fi

I'm sure there is a prettier way but you get the idea

thx
Comment by Tom Gundersen (tomegun) - Wednesday, 27 April 2011, 10:18 GMT
We are considering limiting the scope of the network initscript to not include this usecase. Is there any reason you cannot use netcfg instead?

Loading...