Pause the evil twin when the AP disappear.

[scarfy000]

Q	A
New Feature	yes

Now that fluxion got smart and is able to track the targeted AP, it would be pretty neat if it could get even smarter by pausing the evil twin if the targeted AP disappear.

[ninjadarkgo]

And also if the modem changes channels, it does not keep attacking a something that does not exist since we can not disconnect the clients correctly.

[demecoandrea]

And also if the modem changes channels, it does not keep attacking a something that does not exist since we can not disconnect the clients correctly.

I think this is a great idea, I've been searching for this, because I have a router with autoswitch channel, and the attack stops working

Actually I discovered that it is possible to restart the attack, I made a little edit in the function
fluxion_conditional_bail (row 413)
I commented the line read -r bullshit, added a sleep 5 (just in case..) and then the attack is restarted on the right channel.

Obviously this only works in debug mode (-d) or maybe you could also edit the if [ ! $FLUXIONDebug ]; then block, but I didn't want to modify the script that much...

[LawnSounds]

That’s why you would want an extra network card for target tracking

[usuarionuevor]

also fluxion doesn't close "AP Authenticator" window, so if fluxion switch channel 5 times it still have 5 AP Authenticator windows opened at the same time, I don't know if this is the cause but I suspect it is, because I always get crash after a while with "no client found" (client IS there), when the crash happens the options "select another attack" or "exit" doesn't work, need force close and re-start the whole thing.

[minanagehsalalma]

@usuarionuevor you should start a new issue

[MPX4132]

And also if the modem changes channels, it does not keep attacking a something that does not exist since we can not disconnect the clients correctly.

This has already been implemented. It's the target tracking feature everyone skips out on. You'll very likely need secondary wireless hardware, the primary performing the attack, and the secondary monitoring the target.

edit: Actually, this is easily doable with the current infrastructure because I already implemented target tracking. I can just pause the attack at that point. I'll probably take a look at it sometime.