So, it appears this is not a network-manager bug after all. Should it be re-tagged as a kernel issue?
So, it appears this is not a network-manager bug after all. Should it be re-tagged as a kernel issue?