Date: Fri, 25 Dec 2020 01:57:52 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 252121] [patch] rtadvd should not put an upper limit on rdnssltime and dnsslltime Message-ID: <bug-252121-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252121 Bug ID: 252121 Summary: [patch] rtadvd should not put an upper limit on rdnssltime and dnsslltime Product: Base System Version: 12.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: ta0kira@gmail.com Created attachment 220903 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D220903&action= =3Dedit Removes upper limit on RDNSS and DNSSL lifetimes. rtadvd (in config.c) limits both rdnssltime and dnsslltime to 2*maxinterval= . If this limit is exceeded, rtadvd completely discards the corresponding rdnss = or dnssl and sends router advertisements without it. This means that sending R= As every 15s places an upper limit on rdnssltime of 30s. Specifically, this short lifetime seems to prevent Android 11 (maybe others) from accepting the RDNSS option. (It's unclear what its minimum is, but 600s seems to be fine.) I've attached a patch to effectively remove the upper limits. To make it minimally intrusive, I just set the upper limit to USHRT_MAX. (Potentially making it 32-bit would be a separate issue.) Note that RFC 8106 (https://tools.ietf.org/html/rfc8106) recommends a defau= lt value of 3*maxinterval for both parameters, and doesn't mention any sort of upper limit. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-252121-227>