The script is continuing to run all the attacks (doesn't break the loop) even though the cracked password is visible in "print_final_results.py", "hashcat-output.txt" , "hashcat-potfile.txt".

When attempting to generate scripts using generate_hashcat_scripts.py, the following error throws:

Traceback (most recent call last):
  File "c:\Users\<username>\pwnagotchi-tools\generate-hashcat-scripts.py", line 256, in <module>
    generateScriptsForPMKIDsAndHCCAPXs()
  File "c:\Users\<username>\pwnagotchi-tools\generate-hashcat-scripts.py", line 200, in generateScriptsForPMKIDsAndHCCAPXs
    addNetworkToNetworkCrackedStatusData(filename)
  File "c:\Users\<username>\pwnagotchi-tools\generate-hashcat-scripts.py", line 233, in addNetworkToNetworkCrackedStatusData
    "bssid":getBSSID(filename),
  File "c:\Users\<username>\pwnagotchi-tools\generate-hashcat-scripts.py", line 180, in getBSSID
    return networkBSSIDData[pcapFileName]["bssid"]
KeyError: 'bssid'

Looking further into the offending line (180), it seems as though the script never actually gets the BSSID from the filename, shown in the excerpt below:

def getBSSID(filename):
    global networkBSSIDData
    pcapFileName = filename.replace(".pmkid", ".pcap")
    pcapFileName = pcapFileName.replace(".hccapx", ".pcap")
    return networkBSSIDData[pcapFileName]["bssid"]

I was wondering if it's possible to add linux support to the scripts, as I'm currently running Kali and unable to run the batch scripts.
If not it's totally fine and I can either switch back to my windows os and install everything there or create a pr to add support.

One of the steps requires generating a ssh-key for the pwnagotchi and placing it in the ssh folder.
I've had no problems until now because I never learnt about SSH and no don't know what to do :/

2500 has been depreciated, can you update this to use the 22000 format?

Thanks

Command vagrant up runs, but returns Timed out while waiting for the machine to boot after a long pause. Virtualization is enabled.

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'kalilinux/rolling'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: vagrant_default_1612767749786_51782
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 (guest) => 2200 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2200
default: SSH username: vagrant
default: SSH auth method: private key
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.