Date: Wed, 15 Jul 2020 18:44:23 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 248005] nd6 initializes nd_ifinfo->maxmtu = 0 on newly inserted network interfaces Message-ID: <bug-248005-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D248005 Bug ID: 248005 Summary: nd6 initializes nd_ifinfo->maxmtu =3D 0 on newly inserted network interfaces Product: Base System Version: 12.1-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: mjanelle@blackberry.com Created attachment 216476 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D216476&action= =3Dedit Proposed patch The issue is that if_attach is called prior to setting the interface MTU, w= hich will cause nd6_ifattach to attach the interface with an uninitialized MTU value(0). This issue will typically go unnoticed unless you start adding new network interface after the system has finished starting-up since drivers are mounted/attached then at some time after domainattach will explicitly be ca= lled by: SYSINIT(domainifattach, SI_SUB_PROTO_IFATTACHDOMAIN, SI_ORDER_SECOND, if_attachdomain, NULL); To reproduce the observed behaviour: 1. Start-up without a USB Ethernet device plugged in 2. Insert one and load the driver. 3. ndp -i <ifname> will show maxmtu=3D0 and not maxmtu=3D1500. I've attached a diff that will resolve the issue. --=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-248005-227>