Raspberry Pi Model 3 B - How to turn monitor mode off?

[the-bobo]

I have successfully built nexmon and used nexutil -m2 to get into monitor mode. How do I get out of monitor mode back into managed mode?

I tried nexutil -m0 and then sudo ifconfig wlan0 down and sudo ifconfig wlan0 up but i still can't connect.

edit: iwconfig tells me wlan0 is in Mode:Managed but ifconfig lists wlan0 as UP BROADCAST NOTRAILERS RUNNING PROMISC ALLMULTI

edit2: can confirm that rebooting the Raspberry Pi resolves the issue. ifconfig lists wlan0 as UP BROADCAST RUNNING MULTICAST after a reboot.

is there any way to solve this without a reboot?

edit3: after rebooting i can't run nexutil any more. trying nexutil gives the following error:

nex_init_netlink: socket error (93: Protocol not supported)
nex_init_netlink: socket error (93: Protocol not supported)
nex_init_netlink: bind error (9: Bad file descriptor)
nex_init_netlink: connect error (9: Bad file descriptor)

[haensche]

How could i solve the problem on a raspberry?

root@raspberrypi:~/nexmon/patches/bcm43438/7_45_41_26/nexmon/src# nexutil
nex_init_netlink: socket error (93: Protocol not supported)
nex_init_netlink: socket error (93: Protocol not supported)
nex_init_netlink: bind error (9: Bad file descriptor)
nex_init_netlink: connect error (9: Bad file descriptor)

Are there any missing files or permissions?

[matthiasseemoo]

Did you compile and load the nexmon brcmfmac driver. you also need to run nexutil as root Am 25.02.2017 2:05 nachm. schrieb "haensche" <[email protected]>:

…

How could i solve the problem on a raspberry? ***@***.***:~/nexmon/patches/bcm43438/7_45_41_26/nexmon/src# nexutil nex_init_netlink: socket error (93: Protocol not supported) nex_init_netlink: socket error (93: Protocol not supported) nex_init_netlink: bind error (9: Bad file descriptor) nex_init_netlink: connect error (9: Bad file descriptor) Are there any missing files or permissions? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#49 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALP_7mHUoAwkcnEcchLYLUUaGLKfwofiks5rgCc2gaJpZM4MLwJH> .

[haensche]

Thank you!
Reloading the driver worked!

root@raspberrypi:~/nexmon/patches/bcm43438/7_45_41_26/nexmon# rmmod brcmfmac root@raspberrypi:~/nexmon/patches/bcm43438/7_45_41_26/nexmon# insmod brcmfmac/brcmfmac.ko root@raspberrypi:~/nexmon/patches/bcm43438/7_45_41_26/nexmon# nexutil root@raspberrypi:~/nexmon/patches/bcm43438/7_45_41_26/nexmon# nexutil -m2

[jlcastillo]

I went from monitor to managed mode like this:

- go into managed mode from monitored mode (provided wlan0 is up and in monitor mode as shown by 'ifconfig' and 'iwconfig')

	rmmod brcmfmac 
	cp /home/pi/nexmon/patches/bcm43438/7_45_41_26/nexmon/brcmfmac43430-sdio.bin.orig /lib/firmware/brcm/brcmfmac43430-sdio.bin	
	modprobe brcmfmac
	ifconfig wlan0 up

however I'm still unable to change wlan0 channel in managed mode using 'iwconfig'.

[spadejack014]

I went from monitor to managed mode like this:

- go into managed mode from monitored mode (provided wlan0 is up and in monitor mode as shown by 'ifconfig' and 'iwconfig')

	rmmod brcmfmac 
	cp /home/pi/nexmon/patches/bcm43438/7_45_41_26/nexmon/brcmfmac43430-sdio.bin.orig /lib/firmware/brcm/brcmfmac43430-sdio.bin	
	modprobe brcmfmac
	ifconfig wlan0 up

however I'm still unable to change wlan0 channel in managed mode using 'iwconfig'.

I followed steps without any changes.but I still cannot run it.
trying nexutil gives the same error.
root@raspberrypi:/home/pi# nexutil -m2
nex_init_netlink: socket error (93: Protocol not supported)
nex_init_netlink: socket error (93: Protocol not supported)
nex_init_netlink: bind error (9: Bad file descriptor)
nex_init_netlink: connect error (9: Bad file descriptor)
ERR (__nex_driver_netlink): no valid answer received
what should I do to deal with the problems?

[spadejack014]

I run it on 3B ,4.19.50.
which bcm should i choose ? 43430 ,43438 , or 43455?

[spadejack014]

@haensche
how did you solve such problem?
I reload the driver but it didn't work .