nRF Sniffer Interface not showing up in Wireshark on macOS (11.5.1)

[Mohammad Afaneh]

I recently followed the instructions laid out in the "nRF Sniffer for Bluetooth LE" User Guide version 4.0.0 and having trouble seeing the nRF Sniffer interface in Wireshark (v 3.4.7).

The only way I could get it to show up is to run Wireshark as an administrator. I recall this being an issue a couple of years ago, has this not been fixed? or is there something special that needs to be done to enable Wireshark to see the nRF Sniffer when run in user mode? I can see all the other interfaces, but not the nRF Sniffer.

[Øyvind]

Hello, 

I will need to forward this to our developer team. I hope to have an answer by tomorrow.

Kind regards,
Øyvind

[Øyvind]

Did this work with the previous version, v3.x.0?

[Øyvind]

Ok, I see. 

Did you try with the following from the guide:

[Mohammad Afaneh]

Actually, I can't get to that step because I have to select it from the Interfaces list first (in which it does not show up). I also followed the steps in the troubleshooting section right above the one you pasted (which refers to the issue I'm having) with no luck.

I can simply switch between running Wireshark as an admin and as a user and the interface disappears when I run as user.

[Øyvind]

Hello, 

Sorry, I have not found a good answer to you, other than running Wireshark as administrator when you need to. As I don't have a Mac available at my home office, I will need to ask a colleague to replicate or at least try. 

Kind regards,
Øyvind

[Mohammad Afaneh]

Thanks. Please let me know once you or someone else is able to test it and report any updates.

I can continue using it in admin mode for now, but there’s an inherent risk running Wireshark in admin mode, and something that should probably be avoided. 

[Øyvind]

Sorry for the late response. Have not been able to get anyone to test this due to large amount of cases after the summer period. 

Mohammad Afaneh said:

Please let me know once you or someone else is able to test it and report any updates.

 Yes, sir, I will. I'll forward this to the BLE Sniffer team, and register an internal ticket to follow up. 

 

Mohammad Afaneh said:

I can continue using it in admin mode for now, but there’s an inherent risk running Wireshark in admin mode, and something that should probably be avoided. 

 I see what you mean, and unfortunately have no answer to that at the moment. 

Kind regards,
Øyvind

[Øyvind]

Have you checked the permissions of your Python environment? Could it be possible that you have either a different python environment for admin/user mode, or that the user does not have permission to open the sniffer port?

Could you please check in your /tmp/logs/log.txt log file?

[Mohammad Afaneh]

I don't see a folder named "/logs" under /tmp. How do I check the permissions of the Python environment? 

[Øyvind]

Hello, 

Not Python environment permission, but the sniffer port itself via the group "dialout".

E.g. adding the following permissions:

# Add yourself to the group dialout, Log out and in again.
sudo usermod -aG dialout $USER 

Might need add Wireshark as well. 

Let me know how that works.  Not sure about the Mac OS permission, might be best to search the web to verify 100%

Kind regards,
Øyvind

[Vidar Berg]

Mohammad Afaneh, I don't recall having to change permissions on my mac to get the sniffer to work. I have however had some problems related to having multiple python installations on my system that basically resulted in a different python instance being invoked from command line compared the one invoked by Wireshark.

Could you please try the following:

1. Open Wireshark from the terminal, but not as root, and see if it has the same effect as running Wireshark in admin mode. Apparently the PATH variable is different depending on how you launch a GUI application in macos. E.g. binaries in /usr/local/bin does not seem to get found.

2. Try to install PySerial for other Python installations. E.g. /usr/bin/python3 -m pip install --user pyserial &&  /usr/bin/python -m pip install --user pyserial 

[Mohammad Afaneh]

Thank you! That fixed it. serial was already installed for python 2.7 but not for python3. I suggest this be added to the user guide, as I suspect many people will face the same issue.