FAQ

Clients are not automatically connected to the fake access point

This is a social engineering attack and it's pointless to drag clients in automatically. The script relies on the fact that a user should be present in order to enter the wireless credentials.

There's no Internet connectivity in the fake access point

There shouldn't be one. All of the traffic is being sinkholed to the built in captive portal via a fake DNS responder in order to capture the credentials.

I need to sign in (on Android)

This is how the script works. The fake captive portal is set up by the script itself to collect the credentials. Don't freak, it's all okay.

The MAC address of the fake access point differs from the original

The MAC address of the fake access point differs by one octet from the original in order to prevent fluxion de-authenticating clients from itself during the session.

Why are all my interfaces purple/negative (-)?

Interfaces with a negation symbol are currently being used by other processes.
To force the usage of busy interfaces start fluxion with the FLUXIONWIKillProcesses flag:

export FLUXIONWIKillProcesses=1; ./fluxion.sh

What if I want to run fluxion with multiple flags?

Separate the flags with command delimiters (semicolons ';'):

export FLUXIONWIKillProcesses=1; export FLUXIONWIReloadDriver=1 ./fluxion.sh

Where is the handshake location?

You can find every saved handshake in:
fluxion/attacks/Handshake Snooper/handshakes

Where is the temporary folder?

You can find that folder in:

Fluxion 3
/tmp/fluxspace

Fluxion 2 and older
/tmp/FluxTemp

Note:
The folder get erased after exit. If the debug mode is on the folder get not erased.