Christoph Anton Mitterer wrote: > The wiki claims that the traditional way of defining multiple IPs > per physical interface, e.g. > iface eth0:1 inet static > address 1.2.3.4 > netmask 255.255.255.0 > is deprecated now, see > https://wiki.debian.org/NetworkConfiguration#Multiple_IP_addresses_on_One_Interface.
It doesn't quite say that this is deprecated. Although it does say that using "ifconfig" is being phased out in favor of "ip". That is certainly true. But it does say old and new ways. But you have to understand that it is a wiki too. The program documentation would be the better source for authoritative details. However note that when that wiki page content was added that ifupdown only used "ifconfig" internally. The only way to use "ip" to set up additional addresses was to do so externally through the use of up and down commands. However since that wiki page section was written the ifupdown internals have changed considerably. It has gotten a new maintainer and has been substantially updated. Now ifupdown uses "ip" internally. That wasn't true when the wiki page documented how to use "ip" to set up multiple IP addresses. I think the wiki page does not say anything out right wrong but could use some updating to reflect the current state of the ifupdown software with the later enhancements. Full disclosure: I wrote that section of the wiki page some years ago after battling through the problem myself when the old syntax was not working in the new Debian release. > If that's true (the "new" way seems a bit ugly though) ... But beauty is a matter of taste and in the eye of the beholder. :-) I actually like the use of the up and down commands because one of the problems with the old way was interlocking between physical and virtual interfaces was broken. I am not sure what the current state of that is in ifupdown but for a while that was a source of bugs. By using the up and down strategy to add additional IP addresses then there isn't ever any bad interactions. It feels simpler to me and simple is always better. But I think those bugs have all been addressed in the ifupdown code now. I personally don't know because I am avoiding tickling that area. > then please update > /usr/share/doc/ifupdown/examples/network-interfaces.gz > which still uses the old examples. > > Or even better, add support for #496591 or something similar. I don't know about the package examples but it would be useful to review and update the wiki page. We should clarify the current state of the ifupdown software now that it has been updated to use "ip" internally. Bob
signature.asc
Description: Digital signature
