Could the service file for radvd be updated to have something like
ConditionPathExists=/etc/radvd.conf
in the [Unit] section so that it at least doesn't error on upgrading to
Debian 10?
On Sat, 25 May 2019 00:48:45 +0300 sergio <sergio...@outerface.net> wrote:
> On 25/05/2019 00:24, Geert Stappers wrote:
>
>
> > Please do understand that radvd is not a webserver nor a database
> > engine like postgress.
> >
> > For radvd is no default configuration available that is harmless for
> > all sites where `apt install radvd` is done.
> >
> > That in other words: Starting radvd upon install with some "works
> > for me configuration" is considered HARMFULL.
>
> So it must not be started after `apt install radvd`.
>
>
> > I do understand the wish that radvd should be started upon install
> > like Apache, nginx or Postgress as we are used to in Debian. But I
> > don't know with which sane default configuration.
> >
> > Leaving ticket open for a while in case a good config shows up.
>
> The default configuration should be:
>
> interface <I> {
> AdvSendAdvert on;
> prefix ::/64 {};
> };
>
> Interface <I> should be asked by debconf during installation process.
>
>
>
> But really there is one more issue, prompted me to open this bug:
> I've dist-upgraded the host, with configured radvd. From stretch
> with sysvinit to buster with systemd. After dist-upgrade I was need to
> enable radvd manually with systemctl enable radvd.service.
>
>
> --
> sergio.
>
>
