You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.
[WARNING] No route found for IPv6 destination :: (no default route?)
Returned when the plugin is supposed to load, I have installed scapy and it is working fine. F- shows up at the top of the display.
Several others have had this issue too, if changes to config.toml need to be made we would greatly appreciate knowing what we'd need to add.
The text was updated successfully, but these errors were encountered:
[WARNING] No route found for IPv6 destination :: (no default route?) Returned when the plugin is supposed to load, I have installed scapy and it is working fine. F- shows up at the top of the display. Several others have had this issue too, if changes to config.toml need to be made we would greatly appreciate knowing what we'd need to add.
@lolzdatguy
apfaker.py has a default setting that should be working if set up properly.
config.toml settings are as follows:
# Enable the APFaker plugin
main.plugins.apfaker.enabled = true
# Set the list of SSIDs (fake Wi-Fi network names) to be broadcasted
main.plugins.apfaker.ssids = [
'Test Network 001',
'Test Network 002',
'Test Network 003',
]
# Set the maximum number of fake APs to create
main.plugins.apfaker.max = 2
# Set whether the SSID list should be repeated to create more fake APs
main.plugins.apfaker.repeat = true
# Set whether the fake APs should be password protected
main.plugins.apfaker.password_protected = false
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
[WARNING] No route found for IPv6 destination :: (no default route?)
Returned when the plugin is supposed to load, I have installed scapy and it is working fine. F- shows up at the top of the display.
Several others have had this issue too, if changes to config.toml need to be made we would greatly appreciate knowing what we'd need to add.
The text was updated successfully, but these errors were encountered: