found 645813 0.7~beta1 thanks Stéphane Graber wrote: > Version: 0.7~alpha5.1ubuntu5
That is an unusual version number to file against Debian. :-)
To tighten things up I have marked it as found against 0.7~beta1.
> ifupdown 0.7~alpha5+really0.6.15 properly brings up both eth0 and eth0:0 when
> doing "ifup -a", after upgrading to ifupdown 0.7~beta1, only eth0 is up.
That isn't quite true. What really happens is that ifconfig isn't
displaying the information to you. In order to see it you will need
to use the 'ip' command from the 'iproute' package.
> root@debian01:~# ifdown -a
> root@debian01:~# ifconfig
> root@debian01:~# ifup -a
> root@debian01:~# ifconfig
> eth0 Link encap:Ethernet HWaddr 8a:90:f8:95:7a:80
> inet addr:192.168.122.17 Bcast:0.0.0.0 Mask:255.255.255.0
> inet6 addr: fe80::8890:f8ff:fe95:7a80/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:60745 errors:0 dropped:0 overruns:0 frame:0
> TX packets:46113 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:89047505 (84.9 MiB) TX bytes:3240597 (3.0 MiB)
Try the experiment again and at the points where you call 'ifconfig'
to display the network state please use the 'ip addr show' command to
show the network state instead. It will show you more information.
# ifdown -a
# ip addr show
# ifup -a
# ip addr show
In the 'ip addr show' output you should see something similar to this
that I tested on my machine:
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP
qlen 1
inet 192.168.122.17/24 scope global eth0
inet 192.168.122.18/24 scope global eth0
There it can be seen that the new ip address is up and active.
However no label has been assigned to it. As Nil's remarked in his
message to the bug I am sure this is an issue of labeling.
> root@debian01:~# ifup eth0:0
> ifup: interface eth0:0 already configured
Because the IP address is actually up and online at that time.
At this point I would like to mention a reference for aliases and
labels and what is changing and why. Unfortunately I don't have a
canonical reference to mention. In lieu of that I will point to the
Shorewall documentation which discusses this topic in some detail. It
is useful even if not canonical.
http://www.shorewall.net/Shorewall_and_Aliased_Interfaces.html
With the above in mind I have switched my own uses of this to the
method suggested in the Shorewall documentation. Now I use the 'up'
and 'down' script mechanism of ifupdown to call the 'ip' command to
bring aliases up and down automatically with the underlying network
device. This seems to be the new direction things have taken and it
works well in practice for me. In which case you might have the
following interfaces stanza to replicate your previous behavior done
the other way:
auto eth0
allow-hotplug eth0
iface eth0 inet static
address 192.168.122.17
netmask 255.255.255.0
gateway 192.168.122.1
up addr add 192.168.122.18/24 dev eth0 label eth0:0
down addr add 192.168.122.18/24 dev eth0 label eth0:0
Hope this helps,
Bob
signature.asc
Description: Digital signature
