ms-web-bn / c41n Goto Github PK

hello, c41n only managed to show up once with AP showing but not connecting on device. ( got AP not connecting )
The second time around tried again but no AP showing at all. (no Ap shows up)

Hello, I am trying to host an AP with captive portal (Option 2 from your script) with:

alfa awus036nha atheros ar9271

And I am getting this error:

I tried to google it, but I can't find anything on it.
The AP works for a while then I get the error, when the error happens then I can't to connect to the AP anymore.

I'm sorry for writing here but it was the only way to contact you,
You are good in the cybersecurity field? Then you can write for us about your own tool on GitHub and the use of it.
Your article will be published with your name and a link to your website and social media accounts if you want. Please reply to us at Email: kalitutwrite @ gmail.com
Walid Salame
kalitut .com
Twitter:@xKaliSec

Hi MS-WEB-BN,

First: thanks for he job! It's possible to enable an ap really quickly

I've install C41N on a rasp zero 2w, with Pi OS Bulleye x32 without X and any desktop.

So the script has a first issue on line 401: we have to deleting "xterm -e" and the quotes.

After, for starting your script, I've to stop dnsmasq service, and systemd-resolved, otherwise I have an error because port 53 is already opened.

sudo systemctl stop systemd-resolved
sudo systemctl stop dnsmasq

Regards,

SIOCSIFFLAGS: Operation not permitted
Error for wireless request "Set Mode" (8B06) :
SET failed on device wlan0 ; Operation not permitted.
SIOCSIFFLAGS: Operation not permitted

How I can fix it?

The installation of xterm and apache2 needs to be added to the documentation.
Ubuntu:

apt install xterm
apt install apache2

Also, before starting, check that port 53 is not busy.
Ubuntu:

sudo ss -lp "sport = :domain"

Very often it is occupied by systemd-resolved. He needs to be stopped.
Ubuntu:

sudo systemctl stop systemd-resolved
sudo systemctl disable systemd-resolved
sudo systemctl mask systemd-resolved

To undo what you did:
Ubuntu:

sudo systemctl unmask systemd-resolved
sudo systemctl enable systemd-resolved
sudo systemctl start systemd-resolved

In order for dnsmasq to start via xterm, it is advisable to stop it too.

systemctl stop dnsmasq.service