eewids icon indicating copy to clipboard operation
eewids copied to clipboard

Network Manager Crashes when Running kiscap2amqp

Open michalisk13 opened this issue 2 years ago • 3 comments

Hi,

I am running the eewids project server configuration so all the docker images are created except the kiscap2amqp.

For the kiscap2amqp, I am building it and I am running it on my Ubuntu machine. After I run it, my Network Manager crashes and nothing is responding. I am trying to issue commands like ifconfig or apt update, and the CLI is not responding.

Any idea what might be causing the problem?

Just for clarification, I am using the P-Link TL-WN722N v2/v3 [Realtek RTL8188EUS] for capturing the WiFi packets. I installed the drivers for Ubuntu 22.04 from the aircrack-ng repo here https://github.com/aircrack-ng/rtl8188eus

image

michalisk13 avatar Jan 24 '23 09:01 michalisk13

You have to reverse the stuff kiscap2rabbitmq is doing to get the wifi device doing its magic. Have a look here. I recommend stopping NetworkManager in the meantime, I guess.

techge avatar Jan 24 '23 20:01 techge

Hi,

Actually I am not using the start.sh script to start the dockers. I am just starting them through docker-compose from the terminal so I am missing the last bash commands which do some stuff on the device..

I did that because when I was running the script, the dockers and thus the services running on them were terminated almost immediately after they started.

So I guess the device is passed to the docker so I don't need to put the device on monitor mode on my host from before?

Thanks, Mak

michalisk13 avatar Jan 25 '23 09:01 michalisk13

No matter if you are using the start.sh script or not, you need to switch off the managed mode of the card and restart the Network Manager, as kiscap2rabbitmq needs to put the device in managed mode to capture the packets. That means, the start.sh was an attempt to make it easier to get back (and to get it running in the first place).

So if you are not using it you need to use at least these commands afterwards. Maybe you also need to switch off the NetworkManager yourself or restart it. Honestly, I am not completely sure anymore, what I did in the past, but the aforementioned stuff needs to get done for sure.

techge avatar Jan 29 '23 14:01 techge