On Mon, 1 Jun 2015 03:30:36 +0200 Guilhem Moulin <guil...@guilhem.org> wrote:
> My test was probably not exhaustive, but added the following two lines > to a init-bottom script did the trick for me: > > ip addr flush dev eth0 > ip link set dev eth0 down Thanks for the work! > I'll see if the linux-initramfs-tool would be willing to accept an > ‘unconfigure_networking’ function using ip(1). I haven't looked at all the pieces in a long time. The idea of a function is appealing, but no matter what the sysadm is going to have to be involved in bringing the interface down and de-configuring it (per https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;att=1;bug=715487;filename=README.Debian.downnet.patch , right? Possibly a little extra editing on the part of a sysadm in this corner case is worth not having a function. But all this raises a question in my mind. If ip is available then why does ipconfig exist at all and why is it used? Why would it even be necessary to patch klibc/ipconfig? Patching ipconfig would only be useful in those environments where ip is not available, and in those environments the "ip flush" functionality would need to be built into ipconfig. In this case the right thing to do is not to add a function to linux-intramfs-tool but to dig around in the ip code and port the flush part back into ipconfig. With luck this won't be that hard now that we know where to look. (I think the "down" part is already done.) I'd love to see this working but best to do it right. Thoughts? Addendum: I don't recall thinking at all of vlan tagging (802.1Q), which is something to be considered when putting multiple networks onto a single segment. Maybe ipconfig already does this, maybe not. In any case this is an issue which can be deferred. Regards, Karl <k...@meme.com> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
