Change adapter mode to monitor

[PawelGluszek]

How can I change adapter mode to monitor?

If i dont have /etc/netplan folder. Should I create this folder or I have something wrong, I mean missing some report or something

[lennartkoopmann]

Nzyme will automatically configure the device to monitor mode. It will change to Mode: Monitor when nzyme is running. If this does not happen, the driver most likely does not support monitor mode and you need another WiFi adapter or driver.

Also. when running on a desktop distribution, you might have issues with NetworkManager attempting to constantly re-configure the device. It looks like you are on a Raspberry Pi and this problem should not be the issue here.

You can find supported and tested WiFi adapters here: https://www.nzyme.org/documentation/requirements

What WiFi adapter are you using?

[PawelGluszek]

Do you think that this driver will work?
https://github.com/quickreflex/rtl8188eus

[PawelGluszek]

I installed driver from above and it's still not working

23:39:25.414 [probe-loop-0] INFO  horse.wtf.nzyme.dot11.probes.Dot11Probe - Building PCAP handle on interface [wlxd46e0e18f6a4]
23:39:25.543 [probe-loop-0] ERROR horse.wtf.nzyme.dot11.probes.Dot11Probe - Could not initialize probe [broad-monitor-wlxd46e0e18f6a4]. Retrying soon.
horse.wtf.nzyme.dot11.probes.Dot11ProbeInitializationException: Could not build PCAP handle.
        at horse.wtf.nzyme.dot11.probes.Dot11MonitorProbe.initialize(Dot11MonitorProbe.java:149) ~[nzyme-1.0.0.jar:?]
        at horse.wtf.nzyme.dot11.probes.Dot11MonitorProbe.lambda$loop$0(Dot11MonitorProbe.java:163) ~[nzyme-1.0.0.jar:?]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
        at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
        at java.lang.Thread.run(Thread.java:834) [?:?]
Caused by: org.pcap4j.core.PcapNativeException: wlxd46e0e18f6a4: SIOCGIWPRIV: Argument list too long
        at org.pcap4j.core.PcapHandle.<init>(PcapHandle.java:166) ~[nzyme-1.0.0.jar:?]
        at org.pcap4j.core.PcapHandle.<init>(PcapHandle.java:45) ~[nzyme-1.0.0.jar:?]
        at org.pcap4j.core.PcapHandle$Builder.build(PcapHandle.java:1529) ~[nzyme-1.0.0.jar:?]
        at horse.wtf.nzyme.dot11.probes.Dot11MonitorProbe.initialize(Dot11MonitorProbe.java:143) ~[nzyme-1.0.0.jar:?]
        ... 6 more

[PawelGluszek]

Could somebody tell if this wifi adapter will work in monitor mode without downloading any drivers?
adapter

[steev]

That should be an rtl8187 chipset, and that should have kernel drivers built in.

[andrewbeard]

That should be an rtl8187 chipset, and that should have kernel drivers built in.

My understanding is that the later hardware revisions are actually rtl8188eus chipsets. There are a couple drivers out there but in-kernel monitor mode only works on the v1 hardware. I'd try this, but I have no personal experience with it:
https://github.com/aircrack-ng/rtl8188eus

Can you run this and post the output? It might help confirm which chipset you have.
ethtool -i wlxd46e0e18f6a4