> On 2015-10-07, Theo de Raadt wrote:
> >> I noticed that my bpgd is down after the reboot with the following new
> >> messages in dmesg:
> >>
> >> bgpd(13184): sysctl 6: 4 17 0 0 3 0
> >> bgpd(13184): syscall 202
> >
> > Please ktrace -di it. I suspect this is
On 2015-10-07, Theo de Raadt wrote:
>> I noticed that my bpgd is down after the reboot with the following new
>> messages in dmesg:
>>
>> bgpd(13184): sysctl 6: 4 17 0 0 3 0
>> bgpd(13184): syscall 202
>
> Please ktrace -di it. I suspect this is ICMPV6CTL_MTUDISC_LOWAT,
> I noticed that my bpgd is down after the reboot with the following new
> messages in dmesg:
>
> bgpd(13184): sysctl 6: 4 17 0 0 3 0
> bgpd(13184): syscall 202
Please ktrace -di it. I suspect this is ICMPV6CTL_MTUDISC_LOWAT,
I'll look into it and add it once I determine it is safe in tame.
Hi misc@,
I noticed that my bpgd is down after the reboot with the following new
messages in dmesg:
bgpd(13184): sysctl 6: 4 17 0 0 3 0
bgpd(13184): syscall 202
The message appears on boot:
starting network daemons: sshd bgpd ssmtpdbgpd(13184): sysctl 6: 4 17 0
0 3 0
bgpd(13184) syscall 202
4 matches
Mail list logo