On Nov 09 22:51:08, [email protected] wrote:
> On 2022-11-09, Jonathan Thornburg <[email protected]> wrote:
> > Hi,
> >
> >> I suspect that pppoe is a bit slow at startup, so unbound somehow times out
> >> but has no problems once the network setup/the machine is stable.
>
> The only times I've seen ISPs take more than a few seconds to do pppoe
> (unless they're broken) are if they have an old session hanging around
> from a reboot or crash where the previous session wasn't terminated
> cleanly.
With my current ISP, putting
ifconfig pppoe0 down
into rc.shutdown makes the subsequent boot faster with respect to pppoe.
I suspect it's waht you say: the session gets "terminated properly"
somehow; without it, it takes longer before the ISP assigns me
an address.
> > It's an ugly kludge, but what if you put a wrapper script around the
> > unbound binary which delays 30 or 60 seconds before executing the actual
> > unbound binary?
>
> "!sleep 30" or something in hostname.pppoe0 after "up"?
!while ! ifconfig pppoe0 | grep -F 185.63.96.79; do date ; sleep 10; done
at the end oh hostname.pppoe makes sure services only start
after I have an address; and dmesg -s shows the waiting, if any.
(Of course, I know the address here - tweak as needed.)
Jan
