Jump to content


Active Members
  • Content Count

  • Joined

  • Last visited

  • Days Won


About SymPak

  • Rank
    Hak5 Fan +
  • Birthday 08/02/1989

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Interests
    Cars, Computers, Laser engraving, IT, Network Security, Cisco

Recent Profile Visitors

1,141 profile views
  1. Try killall wpa_supplicant if you have iwlist scanning issues :)
  2. So after looking into it a little I have found that using -M <BSSID> with -e <ESSID> should work as you would like. The problems start when encryption details differ. For instance my lab setup had two routers one with WPA2 and the other with WPA and both had the same ESSID and password. The infusion searches for ESSID only and configured /etc/config/wireless with the wrong configuration. After changing both routers to WPA I was able to selectively connect using the BSSID. I will include BSSID searching and configuration in the next version. However it is likely that for your setup
  3. The feature is there I just had trouble getting it to work. I can look into it tomorrow. In the meantime I think you can use -M (might be -m I can't remember what monitor uses) to specify the bssid.
  4. Update submitted and awaiting approval! Approved! This update brings internet connection monitoring, auto rerty reconnection, commands to be run depending on connection status, adding commands through the infusion, monitor interface support and general improvements. See original post for more details. -SymPak
  5. Clicking remove config on wlan 0-1 removes the config for wlan 0-1 and part of wlan1. Some of wlan1 remains in /etc/config/wireless
  6. Status update! Working on implementing the retry feature is proving to be more difficult than I had originally anticipated. I have also added the essid to the whitelist and blacklist files. Last, the commands feature. You will be able to pass variables from the script into your commands. So if the connection is successful you could say run 'pineapple infusion connect -w "$ESSID"' and have that access point added to the whitelist after the fact. More to come -SymPak
  7. I am still working on the retry feature. I am basically calling the script again within itself and once I get that working I will simplify my function calls. Then I can work on a daemon function. Adding the ESSID into the blacklist and whitelist shouldn't be a problem. Ill look into adding that to my next release. It also technically uses the ESSID for connection so that wouldn't be a big deal to look into either. Ive also got my commands feature figured out. You can add commands through the script and can run them if the connection is successful, if it fails or both. Hopefully I will have som
  8. Thank you for pointing that out. Whitelists do work with passwords. I forgot to remove that once I got the passwords working. Early versions for the MKIV did not work with passwords. I could implement a loop to search for networks. It would be a startup option with a retry value. 0 would be an infinite loop until it connects. To run the script in the background "&" would need to be used
  9. Connect Version 1.1 Features Connects to networks with the strongest signal Save preferred networks with -W option (Open and password protected) Add commands to be run by the pineapple after the script completes. Upon successful connection, failed connection or both run specified commands Macchanger support Upon connection, start karma (PineAP not yet supported) Prevent connection to certain access points with blacklists Check Internet connection status with -s Monitor internet connection status with -m and specify how many failed attempts to retry. 0 = infinite Auto retry tries to
  10. Feel free to use parts of my script that I made for the MKIV. http://forums.hak5.org/index.php?/topic/29487-wifi-connect-script/
  11. Updated to v1.3! This update adds the ability to stop the script with the WPS button if needed, network address detection for ICS, ICS sharing to br-lan by default and command execution upon successful connection. See the original post for details! -SymPak
  12. What interface and options did you run the script with? If you ran it on the internal interface it is probably still in client mode.
  13. Glad to hear you got it working! The reason it might not have been working in 2.8.0 is due to a bug in the firmware.
  14. Sorry for the late reply. What firmware version are you on and what version of the script are you running?
  15. What he is saying is that the mark IV hardware was chosen so it wouldn't have to be replaced until there is need to do so. It is unlikely that we will see any new devices for a while. You should be safe in ordering a mark IV. That being said, the announcement is tomorrow so you might as well wait and see.
  • Create New...