No, that will be the reason this virtual interface exists. I assume it’s the wlan0 interface that is bridged?
But, peculiar thing is this. If I boot my laptop with dock attached, remove and re-scan pci device, end up in the situation where NIC does not get IP from DHCP and then simply remove and re-attach (no reboot required) the thunderbolt cable - NIC works just fine, obtains IP from DHCP with no extra configuration.
Yes, that is strange.
Let’s examine the link status following the warm boot. I don’t actually expect to see a problem with this as wicked would not initiate a DHCP request without the ethernet device being ready at layer 1. Anyway…
/sbin/ethtool p1p1