On Tue, 2011-12-27 at 23:36 -0600, Lloyd Standish wrote: > >Have you tried *not* using ifconfig to set up your interfaces? You > > should only be using iproute2. > > I've seen that mentioned before, and I'm confused. iproute2 means, for > firewall code, "ip" and "tc" - is that right? Yes, and "ip" can do everything that all the various net-tools commands do. > I usually bring up interfaces with "ifup" when I can Ah, therein lies an interesting situation. ifup is pretty old too, and makes calls to the ifconfig command, which is a real pain. However, unless someone tells me otherwise, I'm not aware of a replacement for it. There was a project a while ago called netconf, but this seems to have died: http://wiki.debian.org/netconf > , since that sets the interface address specified in /etc/network/interfaces, whereas "ifconfig <if> up" doesn't. That's the best way to do it with Debian. > I notice that after adding the Debian "vlan" package, ifup and ifdown > appear to bring virtual interfaces up and down OK. But ifup/down are > not part of iproute2, right? Yeah, correct. The most accepted way of doing it seems to be to use ifup and ifdown to bring the physical interface up and down, and to do everything else by adding "ip" commands into your /etc/network/interfaces file using the up/down/pre-up/pre-down/post-up/post-down options. > Do you know of any vlan problem with > ifup/down? Sometimes interfaces can't be taken down with "ifdown," > and I have to use ifconfig. I get similar problems when adding IPV6 addresses, although I use "ip" to sort it out manually ;-) Anybody know what happened to netconf? Andy -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
