08-17-2018, 05:46 PM
Correct. Running hcxdumptool without disable arguments and/or setting a filterlist is the most aggressive mode.
hcxdumptool will run deauthentications against established connections and disassociations if a M4 was received.
You can view your RF-signature here (tx=xxx) and control it via switches:
INFO: cha=3, rx=3315, rx(dropped)=832, tx=311, powned=4, err=0
--disable_ap_attacks --disable_deauthentications:
INFO: cha=1, rx=799, rx(dropped)=12, tx=1, powned=0, err=0
--disable_ap_attacks --disable_deauthentications --disable_client_attacks --disable_active_scan:
INFO: cha=5, rx=1403, rx(dropped)=11, tx=0, powned=0, err=0
hcxdumptool will run deauthentications against established connections and disassociations if a M4 was received.
You can view your RF-signature here (tx=xxx) and control it via switches:
INFO: cha=3, rx=3315, rx(dropped)=832, tx=311, powned=4, err=0
--disable_ap_attacks --disable_deauthentications:
INFO: cha=1, rx=799, rx(dropped)=12, tx=1, powned=0, err=0
--disable_ap_attacks --disable_deauthentications --disable_client_attacks --disable_active_scan:
INFO: cha=5, rx=1403, rx(dropped)=11, tx=0, powned=0, err=0