Fluxion: Unable to start captive portal interface

Created on 1 Jan 2018  ·  26Comments  ·  Source: FluxionNetwork/fluxion


Read the wiki?

No*

Do you want to request a feature or report a bug?

Bug

What is the current behaviour?

I am using RT5370n WiFi chipset, have also tried Other interface such as the TLWN722N, but still couldn’t get the captive portal interface to work. The program output:
“Unable to start captive portal interface”
Then returns to menu. I am using fluxion 3.11 (the latest version), with Ubuntu Mate 16.04.02.

If the current behaviour is a bug, please provide the steps to reproduce it.

What do you think the expected behaviour should be?

If this is a feature request, what is the motivation or use case for the added feature?

Specs

Paste the output of ./script/diagnostics.sh [interface]


Most helpful comment

It's better to talk publicly as the others might need this in the future
just run make in the root folder of the repository, then run sudo make install
don't forget to install the kernel headers corresponding to your kernel version

All 26 comments

Forgot to mention, I have already captured a validated handshake

It seems your device's driver might not support virtual interfaces. You're going to have to check yourself whether the driver supports virtual interfaces or not following this guide. I'm going to close this issue because virtual interface support isn't an issue with fluxion, but an issue with your driver. You can continue to reply here to let us know what you find out. Again, it seems the issue isn't related to fluxion. If you can prove me wrong, and determine it's an issue with fluxion, we can reopen the issue.

@MPX4132 getting this same problem.
Fluxion worked flawlessly 1 month ago on kali, now i've tried it on my ubuntu and got this error.
Can't be driver problem. Can it?

Wait, so it was working fine before? Yeah, that sounds fishy. Do you by any chance know if there's been an update to the driver you guys are using?

It could also be the network-manager being overly aggressive.

@MPX4132 I managed to find the difference on the drivers, on my ubuntu, the version is the driverversion=4.10.0-42-generic
and on my kali, which is the one working:
driverversion=4.9.0-kali3-amd64

How can i copy the kali driver to my ubuntu? I did a lot of research with no luck.

@underscrew I don't know how to swap or setup drivers, sorry man. Someone else might be able to help, though. From what I read, you'll have to compile the driver yourself because apparently they're kernel specific (binary-specific).

Hello , i have a problem in the second step in fluxion for to create a "captive portal " this message appears when I select my wifi card :
] Select an interface for the access point.

[1] eth0 [+] Intel Corporation 8254EM Gigabite Ethernet Controller(rev
[2] wlan0 [+] TP-Link TL-WN722N v2
[3] Repeat
[4] Back

[fluxion2@kali]-[~] 2

[*] Unable to start captive portal interface, returning!

can someone Help please?

@Aoki07 you need to make the adapter run in concurrent mode, I used to face that problem but after enabling concurrent mode, it went fine

Hello @Quang-vip thanks for your answer , can you explain me how can do this?

@Aoki07 first you need to clone this repository: https://github.com/aircrack-ng/rtl8188eus
then open up _include/autoconf.h_

look for //#define CONFIG_CONCURRENT_MODE and uncomment it by removing the double forward slash
after that, build the driver then install it

restart your machine (that's what I usually do, you could hot-remove the driver then hot-insert it so you don't need to restart your machine)
run ip a and you should be able to see 2 wireless interfaces (apart from the built-in one if your machine has one)

then choose 1 for jamming and stuff, 1 for access point

now I'm stuck with the fact that my phone nor any other device can't connect to the rogue AP lol
(Edit: probably because of the DHCP server that fluxion uses)

Thanks when i remove the double forward slash how i can build the driver and install again? can we speak in private?

It's better to talk publicly as the others might need this in the future
just run make in the root folder of the repository, then run sudo make install
don't forget to install the kernel headers corresponding to your kernel version

hey @Quang-vip i have tried but not working

after install adaptor is not working at all

after install adaptor is not working at all

Could you be more specific? What did you do exactly?

you need to make the adapter run in concurrent mode, I used to face that problem but after enabling concurrent mode, it went fine

sir can i please have a talk in private as i to have the same issue and i was a begginer or can u provide any link of an vedio which helps me

please reply quang-vip fast

sir can i please have a talk in private as i to have the same issue and i was a begginer or can u provide any link of an vedio which helps me

like I said, it's better to talk here

its not nessessary to be in concurrent mode.

@Quang-vip i havent face this probleum.
now I'm stuck with the fact that my phone nor any other device can't connect to the rogue AP lol
(Edit: probably because of the DHCP server that fluxion uses)

the probleum that i am facing is in deauthentication.
it is not sending the packets at faster rate ,so as a result it is unable to deauthentcate properly.

the probleum that i am facing is in deauthentication.
it is not sending the packets at faster rate ,so as a result it is unable to deauthentcate properly.

Try using other deauth methods

Just do one thing when you are getting this error remove your adapter and pluging your problem will solve in my case when i remove mode: monitor when i plugin mode:auto

Hello , i have a problem in the second step in fluxion for to create a "captive portal " this message appears when I select my wifi card :
] Select an interface for the access point.

[1] eth0 [+] Intel Corporation 8254EM Gigabite Ethernet Controller(rev
[2] wlan0 [+] TP-Link TL-WN722N v2
[3] Repeat
[4] Back

[fluxion2@kali]-[~] 2

[*] Unable to start captive portal interface, returning!

can someone Help please?

Hello help please

@anil1143 why are you posting to an old long closed issue?
regarding your actual issue its due to the chipset in the adapter you have not supporting VIF. VIF is needed to be able to both deauth and create a fake AP at the same time. There is no way to give that adapter VIF support either. You would have to look into getting either a second adapter or one that supports monitor mode, AP mode and VIF.

here is a list of supported adapter/chipsets
Atheros AR9271 <- present in TP-Link TL-WN722N v1 or Alfa AWUS036NHA (2.4Ghz - USB)
MediaTek MT7612U <- present in Alfa AWUS036ACM (2.4Ghz/5Ghz - USB) (not recommended to be used on Virtual Machines, but it works very well on native Linux. The recommended Linux kernel version is 5.3 or greater). For Rpi 2/3 run this command to get the card working echo "options mt76_usb disable_usb_sg=1" > /etc/modprobe.d/mt76_usb.conf
Ralink RT2770 <- present in Alfa AWUS051NH (2.4Ghz/5Ghz - USB)
Ralink RT3070 <- present in TP-Link TL-WN7200ND or Alfa AWUS036NH (2.4Ghz - USB)
Ralink RT3572 <- present in Alfa AWUS052NHS (2.4Ghz/5Ghz - USB)
Ralink RT5372 <- present in D-Link DWA-137 (2.4Ghz - USB)
Ralink RT5572 <- present in Panda PAU07 or Panda PAU09 (2.4Ghz/5Ghz - USB)
Realtek RTL8187 <- present in Alfa AWUS036H (2.4Ghz - USB) (may require patched driver)
Realtek RTL8723BE <- present in Realtek RTL8723BE card (2.4Ghz - PCIe)

Was this page helpful?
0 / 5 - 0 ratings

Related issues

EOS123 picture EOS123  ·  3Comments

blueflame357 picture blueflame357  ·  20Comments

GNSMaverick picture GNSMaverick  ·  7Comments

kandarpgautam picture kandarpgautam  ·  15Comments

Geczy picture Geczy  ·  16Comments