On Tue, Feb 19, 2013 at 11:20:07AM -0600, Brett Stauner wrote: > When I experienced this issue I did run "ifdown eth0" before trying to > configure and then running "ifup bond0" as the article here: > http://wiki.debian.org/Bonding suggests. Is the "ifcfg eth0 down" > different than using the ifdown command? And if that is the case the > documentation wiki should get updated to keep people from running into this > issue.
The wiki already mentions this:
“Sometimes, ifdown doesn't work, in that case use ifconfig eth0 down.”
Normally ifdown eth0 should just work though, but you have to run that before
modifying /etc/network/interfaces.
> If there are more tests or information I can provide let me know, I could
> run through the scenario again this week.
If you can still reproduce this problem, then it would be nice to have the
output of "ip addr show; ip route show" before and after each ifup/ifdown
command you give, so we can see where exactly the problem happens. Also, run
ifup and ifdown with the -v option so all commands that are executed are
shown.
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <g...@debian.org>
signature.asc
Description: Digital signature
