Peter Memishian wrote:
I'm confused. According the DLPI specification, DL_DISABMULTI_REQ is valid in any state other than DL_UNATTACHED. DL_UNATTACHED only happens when a DL_DETACH_REQ is done (for DL_STYLE2 only). And as per 6522958, IP almost never sends a DL_DETACH_REQ today (and I'm about to rip out the code that does as part of fixing that bug).
FWIW it used to be that we wanted to send DL_DETACH_REQ to have the driver turn off interrupts etc. But with NWAM coming we'll always have the drivers active to be able to detect a cable that is plugged in, so this is just a historical note.
So does that mean we can address this issue pre-ARP-merge?
If you never detach and the drivers don't drop the multicast state on unbind (which would be a bug), then you should be able to fix this now. I assume the messages that go via ARP don't get reordered - if we do an ifconfig xx0 down up the DL_ENABMULTI from the up better be delivered to the driver after the DL_DISABMULTI_REQ from the down.
Erik _______________________________________________ networking-discuss mailing list [email protected]
