Fixed potential issue caused by network-manager.
When using multiple interfaces, the network manager was causing problems. Specifically, when attempting to use different master & monitor interfaces.
This commit is contained in:
parent
da92d965c7
commit
cd55ebca8c
|
@ -1295,6 +1295,11 @@ stop_attack() {
|
|||
|
||||
captive_portal_stop_interface
|
||||
|
||||
# Start the network-manager if it's disabled.
|
||||
if ! systemctl status network-manager.service &> /dev/null; then
|
||||
systemctl start network-manager.service
|
||||
fi
|
||||
|
||||
CaptivePortalState="Stopped"
|
||||
}
|
||||
|
||||
|
@ -1305,6 +1310,11 @@ start_attack() {
|
|||
|
||||
stop_attack
|
||||
|
||||
# Disable the network-manager if it's available.
|
||||
if systemctl status network-manager.service &> /dev/null; then
|
||||
systemctl stop network-manager.service
|
||||
fi
|
||||
|
||||
captive_portal_start_interface
|
||||
|
||||
echo -e "$FLUXIONVLine $CaptivePortalStartingDHCPServiceNotice"
|
||||
|
|
Loading…
Reference in New Issue