Well, duh, of course you are right! MAC addresses don't route! So what IS this list?!
Also - for grins, I plugged my OWN list of MAC addresses from my laptop. I happen to have a boatload of virtual adapters for various reasons (I have VM's on my laptop) as well as typical 'corporate' VPN clients (Sophos, Fortinet, etc).
The Fortinet VPN showed up, but the Sophos VPN did not.
None of the virtual device MACs showed up.
So the lack of a 'hit' on MACs is not exactly something I'd read too much into.
FYI, I have over 20 'adapters' on my laptop (ipconfig /all). Part of the reason is I installed Microsoft's sandbox app, which creates a virtual adapter for every 'real' adapter, but does this even when the 'real' adapter itself is a non-physical device. So out of the 20 adapters, only 3 have hits on the MAC db from Wireshark.
The biggest surprise is that the sophos virtual adapter is not showing up, while the Fortinet virtual adapter does.
Well, duh, of course you are right! MAC addresses don't route! So what IS this list?!
Also - for grins, I plugged my OWN list of MAC addresses from my laptop. I happen to have a boatload of virtual adapters for various reasons (I have VM's on my laptop) as well as typical 'corporate' VPN clients (Sophos, Fortinet, etc).
The Fortinet VPN showed up, but the Sophos VPN did not. None of the virtual device MACs showed up.
So the lack of a 'hit' on MACs is not exactly something I'd read too much into.
FYI, I have over 20 'adapters' on my laptop (ipconfig /all). Part of the reason is I installed Microsoft's sandbox app, which creates a virtual adapter for every 'real' adapter, but does this even when the 'real' adapter itself is a non-physical device. So out of the 20 adapters, only 3 have hits on the MAC db from Wireshark.
The biggest surprise is that the sophos virtual adapter is not showing up, while the Fortinet virtual adapter does.