odhcp6c RENEW timeout issue leads to OOM/OOPS [Was: Re: QEMU x86/64 ubus issues ... ]

Hans Dedecker dedeckeh at gmail.com
Tue Dec 1 15:12:30 EST 2020


Hi Petr,

On Sat, Nov 28, 2020 at 8:48 PM Hans Dedecker <dedeckeh at gmail.com> wrote:
>
> Hi,
>
> On Sat, Nov 28, 2020 at 5:04 PM Petr Štetiar <ynezz at true.cz> wrote:
> >
> > Hans Dedecker <dedeckeh at gmail.com> [2020-11-26 21:19:30]:
> >
> > Hi,
> >
> > > Is it possible to have a pcap trace of the DHCPv6 messages on the wan ?
> > > I hope to find some time next weekend to investigate the issue further
> >
> > http://ynezz.true.cz/openwrt/odhcp6c/capture.pcap.gz#
> Thank you for the traces; looking into the DHCPv6 packets make the issue clear.
> Packet 22 is a DHCPv6 reply packet in response to a renew which in its
> turn is triggered by a DHCPv6 reconfigure packet.
> The packet contains an IA-PD option but no IA prefix option which is
> strange. According to the DHCPv6 RFC renew messages must be kept
> sending when T1 has expired for either an IA address or IA prefix when
> the server does not reply the IA address or IA prefix which is
> happening in this case.
> I will do further investigation how we could protect odhpc6c against
> such DHCPv6 server behavior
Can you check if commit
https://git.openwrt.org/?p=project/odhcp6c.git;a=commit;h=a7b2221f687264c020b7a18a4e690d79f312a667
fixes the issue in your setup ?
While doing the test can you put odhcp6c into verbose mode (-v) and
take again a pcap trace on the wan ?

Hans
>
> Hans
> >
> > Cheers,
> >
> > Petr



More information about the openwrt-devel mailing list