Your message dated Sat, 09 May 2015 21:01:27 +0200
with message-id <[email protected]>
and subject line Re: Bug#731243: two reasons to separate bird/bird6
has caused the Debian Bug report #731243,
regarding two reasons to separate bird/bird6
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
731243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731243
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bird
Version: 1.4.0-1
Severity: wishlist
Since bird 1.3.11-2, bird6 is part of the bird package.
I have two idea's why i like the old situation more.
We use dual stack routers, when upgrading bird we can first upgrade
bird6 and then bird. With this approach you only have to disable one
stack and login using the other stack.
In some cases we don't want ipv6 routing. When starting a virtual
machine with bird, bird6 will always fail because bird6 is not
configured correctly, seeing red letters with failed when starting a
virtual machine does not feel right.
--
Frank Baalbergen - System / Network Engineer
T +31 (0)10 2760434 | [email protected] | www.mendix.com
--- End Message ---
--- Begin Message ---
tags 731243 wontfix
thanks
The original post from Frank contains a few different issues/questions:
1. Being able to upgrade first bird and then bird6 separately without
losing connectivity if you're logged in over the network.
It's a nice trick, but there are enough other best practice ways to
reach the same goal, like logging in over another host in a directly
connected network, use serial console, interface on management vlan, or
any other way of out of band access etc. So, ok, we can get over it.
And, when forgetting to do so (which occasionally happens), you'll get a
working command line back again after a few seconds, when bird is
restarted... unless.... dpkg is asking if you want to replace bird.conf
/ bird6.conf with a new version from the package, without you being able
to answer that question any more.
Having the bird.conf files as conffile does not really make sense,
because the files from the package do not contain any sensible
configuration, so a user will never want to revert back to it. About
this, follow-up in #784852
2. Either bird or bird6 being installed and started if you don't want
them, like on a v4-only or v6-only router. The most annoying thing here
was that bird6 always errored, but that's already fixed now.
The usual debian behaviour is to start any daemon you install, even if
you didn't configure it yet. It means that in the situation you don't
want to run bird for v4 or v6, you always end up having to stop and then
disable it. Ok, it's annoying, but we can also get over that.
So, closing with tag wontfix, also on behalf of the submitter. (I work
with Frank in the same team).
--
Hans van Kranenburg - System / Network Engineer
T +31 (0)10 2760434 | [email protected] | www.mendix.com
--- End Message ---
