On 2022-11-15, Courtney wrote:
> I had a similar issue going from 7.1 -> 7.2 (though looking back, I
> think the issue is
> I made my config change and never rebooted until I upgraded to 7.1).
Different issue I think.
> However, my issue was not so much unbound waiting for an interface, but
>
I had a similar issue going from 7.1 -> 7.2 (though looking back, I
think the issue is
I made my config change and never rebooted until I upgraded to 7.1).
However, my issue was not so much unbound waiting for an interface, but
rather I wanted to allow listening on IPv6 and thus added my
On 2022-11-10, Martin Schröder wrote:
> Am Do., 10. Nov. 2022 um 11:22 Uhr schrieb Stuart Henderson
>:
>> On 2022-11-09, Martin Schröder wrote:
>> > Am Do., 10. Nov. 2022 um 00:02 Uhr schrieb Martin Schröder
>> > :
>> >> This happens only on bootup of the machine... :-(
>> >
>> > I've tried
Am Do., 10. Nov. 2022 um 11:22 Uhr schrieb Stuart Henderson
:
> On 2022-11-09, Martin Schröder wrote:
> > Am Do., 10. Nov. 2022 um 00:02 Uhr schrieb Martin Schröder
> > :
> >> This happens only on bootup of the machine... :-(
> >
> > I've tried hard to get any log messages for this, but failed
On 2022-11-10, Jan Stary wrote:
> On Nov 10 00:39:59, mar...@oneiros.de wrote:
>> Am Do., 10. Nov. 2022 um 00:25 Uhr schrieb Jan Stary :
>> > With my current ISP, putting
>> >
>> > ifconfig pppoe0 down
>> >
>> > into rc.shutdown makes the subsequent boot faster with respect to pppoe.
>> >
On 2022-11-09, Martin Schröder wrote:
> Am Do., 10. Nov. 2022 um 00:02 Uhr schrieb Martin Schröder
> :
>> This happens only on bootup of the machine... :-(
>
> I've tried hard to get any log messages for this, but failed so far.
> Neither setting a log file for unbound nor "unbound_flags=-d -d"
On Nov 10 00:39:59, mar...@oneiros.de wrote:
> Am Do., 10. Nov. 2022 um 00:25 Uhr schrieb Jan Stary :
> > 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
Am Do., 10. Nov. 2022 um 00:25 Uhr schrieb Jan Stary :
> 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
On Nov 09 22:51:08, stu.li...@spacehopper.org wrote:
> On 2022-11-09, Jonathan Thornburg 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
Am Do., 10. Nov. 2022 um 00:02 Uhr schrieb Martin Schröder :
> This happens only on bootup of the machine... :-(
I've tried hard to get any log messages for this, but failed so far.
Neither setting a log file for unbound nor "unbound_flags=-d -d"
produced any output.
Best
Martin
Am Mi., 9. Nov. 2022 um 23:51 Uhr schrieb Stuart Henderson
:
> On 2022-11-09, Jonathan Thornburg wrote:
> 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
On 2022-11-09, Jonathan Thornburg 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
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.
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
Am Mi., 9. Nov. 2022 um 21:25 Uhr schrieb Jonathan Thornburg
:
> --- begin /etc/hostname.em0 ---
> inet autoconf
> --- end /etc/hostname.em0 ---
Well, this is DTAG vDSL, so I have
-- begin /etc/hostname.pppoe0
inet 0.0.0.0 255.255.255.255 NONE \
pppoedev vlan7 authproto pap \
Hi,
> since upgrading my router to 7.1 unbound doesn't start up automatically
> anymore,
> instead it times out:
>
> starting early daemons: syslogd pflogd unbound(timeout) ntpd.
>
> It can be started successfully manually later. This setup worked with 7.0.
I have a very similar configuration
Hi,
since upgrading my router to 7.1 unbound doesn't start up automatically anymore,
instead it times out:
starting early daemons: syslogd pflogd unbound(timeout) ntpd.
It can be started successfully manually later. This setup worked with 7.0.
System is an apu acting as a firewall/router for my
16 matches
Mail list logo
