On 9/29/20 10:33 AM, Fulko Hew wrote:
No, no other thread. In the original email I used iw command to turn
manage off.
wlp2s0f0u4 wifi unmanaged --
wlp2s0f0u4 unassociated ESSID:"" Nickname:"<WIFI@REALTEK>"
Mode:Managed Frequency=2.412 GHz Access Point: Not-Associated
So now nmcli says it's unmanaged but iwconfig says it IS managed.
Ok, that is a little confusing. The nmcli "managed" means that
NetworkManger is handling the device. The iwconfig "managed" is
referring to the mode that the wifi device is in.
So I also tried both of the following to enable monitor:
[root@localhost fhew]# iw wlp2s0f0u4 set monitor none
command failed: No such device (-19)
That can't be the actual command you ran, because it's not valid.
You're missing a "dev".
[root@localhost fhew]# iwconfig wlp2s0f0u4 mode monitor
Error for wireless request "Set Mode" (8B06) :
SET failed on device wlp2s0f0u4 ; Invalid argument.
and neither worked. So I'm back to thinking it's a driver issue.
Yes, that seems very likely to be the reason for both those commands
failing.
P.S. Looking at the newer Wireshark, I still didn't see a 'monitor'
button. Perhaps it's because the wi-fi driver isn't supporting it?
When you open the capture options dialog, you might need to scroll to
the right to see the monitor checkbox.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
