The attached patch reads /etc/tayga.conf and runs those commands. It
also destroys the tunnel when tayga is stopped.
I must say I'm worried a bit about those who don't expect initscript
doing this and do manual configuration. Changing initscript to do this
automatically may break network configuration on upgrades.
Do you think that adding a CONFIG_INTERFACES=no in /etc/default/tayga
(defaulting to no so that the default behaviour does not change) and
wrapping the whole interface configuration with and 'if' would do?
Maybe we could add the script or the patch to
/usr/share/doc/tayga/example.setup? I find it cumbersome and error
prone to first fill out all the details in the config file and then
having to redo that manually.
As for network configuration on upgrades ... I don't see how that could
break it. But I understand that is something that should be looked at.
I just checked miredo and the initscript doesn't do anything but
start/stop the program. Maybe upstream should apply the addresses and
routes just as miredo does, the program has all the information available.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
