Hi Quinn, Agreed - we have some very unique requirements! We need the actual link speed - to be able to identify cable issues, for example. Regarding the enhancement request - I saw that other people had already file some. But I think you are quite right - more is better! So I filed one: FB9074593 - Need coherent APIs for using NWEthernetChannel. As always, Thank You for your support! Devendra.

Seems like this is a bug, so I filed a feedback - FB9077424 Thanks. Devendra.

Hi Quinn, You can get this from the BSD interface name (en7 in my example) using the old school BSD API (SIOCGIFXMEDIA). If I understand this correctly, this ioctl provides the settings - and may not be the actual speed that the interface is working on. (BTW all of that is also available via NWInterface APIs). What we would need seems to what the ifconfig utility seems to use - SIOCGIFLINKPARAMS, but that one seems to be PRIVATE - so we are not able to use that. Thanks. Devendra.

Thanks Quinn for the update! Devendra.

For others who may land up here - this is now fixed in latest Monterey beta. Thanks. Devendra.

Please provide some specifics. Perhaps attach the panic log here.

What program is loading these plug-ins? This is our own program which is loading the plugins - using bundle APIs.

That's right - this setup has two separate libraries, both of them have the same binary name "MyLibrary". [The exported symbols are all different because the symbols contain the version "A" or "B" in the symbol names.] I was surprised that this could even work, but my coworkers told me that they have been using this scheme for some time, and it seems to work fine on most other Macs. Thanks. Devendra.

Yes, these are different versions of the same basic code, but with some additions, changes, etc. All the exported symbols however are prepended with a version specific identifier. For example, MyLibraryA would have A::SomeFunc(), while MyLibraryB would have B::SomeFunc().

I think that's what we'll just do - no need to live in the ambiguity! Thank you Quinn for your help - as always! Devendra.

If anybody is looking here, I want to update that the latest macOS versions have restored the functionality o taskinfo reporting information about kernel task threads.