Hi, I have created an ethers file, like described in the wireshark docs and put it into a personal profile (e.g. testETHERS) Is there an additional step needed to the MAC addresses resolved? I have enabled the physical name resolving. I am using Wireshark 3.0.6 64Bit for Windows.
ethers does not support a profile specific version, only the personal and global configuration directories. Some of the configuration files do, e.g. vlans, but the current state overall seems to be inconsistent and undocumented.
At the time of writing, in the current master branch, the following address resolution files can be loaded from a profile:
I don't know what the state is for 3.0.6.
Ok makes sense. But I have also tried the global and personal configuration directories. But it didn’t work.
Ok we start at the very beginning: where exactly have you stored the ethers. I have stored it in %appdata%roaming/wireshark
And Ihave also enabled the reasolve mac addresses in the preferences
Assuming %appdata% resolves to the path to your user's appdata then that seems to be the correct place. Easy to check in Wireshark using Help -> About Wireshark and select the Folders tab. You can double click on the link to open the directory in Windows Explorer.
That is what I did. but obviously it does not work. Is there something other which can prevent resolving the mac addreses from the ethers file? Or needs the ethers file itsswlf something special. E.g empty row at the end?
Did you restart Wireshark after editing your ethers file? If nothing is working, I'd suggest starting with a pristine %APPDATA%\Roaming\Wireshark folder and then making your ethers file modifications. Some other TBD preference may be affecting this, or perhaps something left over from an older version of Wireshark? Just copy all your files elsewhere first so you can diff them to figure out what the issue was, and also so you can more easily restore everything, except that which is causing the problem for you, once the root cause of this problem is found.
Thx. The strange thing is that all other resolutions like host or vlans do work. I think it is something at the local system which might cause this.
I seems to be a local problem (maybe due to some security settings) . On another system ethers is working well.
Asked: 2019-11-21 13:34:42 +0000
Seen: 1,759 times
Last updated: Nov 21 '19
Copyright Wireshark Foundation, 2017-2023 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
