... snip ...
It's "dnf system-upgrade" now and it works great. However, you're so
far behind now that you might as well just do a re-install.
> you want to control the device. Otherwise you will have that problem
> where the interface gets taken away from Wireshark. I will assume that
> "wlp0s20f0u3" is your device.
>
> nmcli dev set wlp0s20f0u3 managed off
>
> yes, as per my previous message, I did turn 'manage' off.
I don't see anything in your first message about that. Is there another
thread going on the wireshark list?
No, no other thread. In the original email I used iw command to turn manage off.
Anyway, I've now switched to testing on my F32 box.
[root@localhost fhew]# nmcli dev set wlp2s0f0u4 managed off
[root@localhost fhew]# nmcli dev
DEVICE TYPE STATE CONNECTION
enp5s0 ethernet connected Wired connection 1
lo loopback unmanaged --
wlp2s0f0u4 wifi unmanaged --
[root@localhost fhew]# iwconfig
lo no wireless extensions.
enp5s0 no wireless extensions.
wlp2s0f0u4 unassociated ESSID:"" Nickname:"<WIFI@REALTEK>"
Mode:Managed Frequency=2.412 GHz Access Point: Not-Associated
Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
So now nmcli says it's unmanaged but iwconfig says it IS managed.
and BTW. NetworkManager doesn't even have the interface as one of it's options,
it only lists my Ethernet connector.
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)
[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.
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?