tyle=3D"caret-color: rgb(0, 0, 0); font-family: =
Menlo-Regular; font-size: 13px; font-style: normal; font-variant-caps: =
normal; font-weight: 400; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" class=3D"">machines, so =
not sure about repeatability.
I am also not entirely sure this is not a ping6 ff02::1%wlan0 =
while
the ifp was =
destroyed by netif restart at the same time the packet was
still on the =
way out?
with a different fault path.
If it was =
during create, the wlan(4) interface would not be associated
and UP at =
that point of if_attach_internal() and
`ifconfig inet6 -ifdisabled` would not have been run to be =
able to send
that packet =
in first place?
Emm, I'm still hacking the lifecycle of ifnet. I =
think you're right. By default inet6 is disabled on =
interfaces.
It seems to be impossible to send packets via =
disabled interfaces.
Othwerwise the packet would have had to "survive" the clone =
destroy andclone create =
cycle somewhere ...?diff --git a/sys/net/if.c =
b/sys/net/if.c
index c3c27fbf678f..16ee5667e7bb 100644
--- a/sys/net/if.c
+++ b/sys/net/if.c
@@ -947,11 +947,11 @@ if_attach_internal(struct ifnet *ifp, =
bool vmove)
}
#endif
- =
if_link_ifnet(ifp);
- if (domain_init_status =
>=3D 2)
&nb=
sp; if_attachdomain1(ifp);
+=
if_link_ifnet(ifp);
+
EVENTHANDLER_INVOKE(ifnet_a=
rrival_event, ifp);
if =
(IS_DEFAULT_VNET(curvnet))
&nb=
sp; devctl_notify("IFNET", ifp->if_xname, "ATTACH", =
NULL);
-- Bjoern A. =
Zeeb =
&n=
bsp; &nbs=
p; =
&n=
bsp; r15:7