Skip to content
This repository has been archived by the owner on Apr 19, 2020. It is now read-only.

subprocess.call() not working as expected #279

Closed
oliverhavrila opened this issue Sep 17, 2017 · 1 comment
Closed

subprocess.call() not working as expected #279

oliverhavrila opened this issue Sep 17, 2017 · 1 comment
Labels

Comments

@oliverhavrila
Copy link

Hello guys,

I hope you can help me.
I am using Kali linux 2017.1 on Raspberry Pi 2 and wireless card is: TP-LINK TL-WN722N
And this is error when i try to start it

[] Loading debugging mode
[
] Current Session::ID [ODg2Mjk=]
[] Configuring hostapd...
[
] Enable forwarding in iptables...
Traceback (most recent call last):
File "/usr/share/WiFi-Pumpkin/core/main.py", line 1312, in Start_PumpAP self.CoreSettings()
File "/usr/share/WiFi-Pumpkin/core/main.py", line 1166, in CoreSettings for line in self.SettingsAP['kill']: Popen(split(line), stdout=PIPE,shell=False,stderr=PIPE)
File "/usr/lib/python2.7/subprocess.py", line 390, in __init__errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1024, in _execute_child raise child_exception
OSError: [Errno 2] No such file or directory

Thanks a lot

@oliverhavrila oliverhavrila changed the title Start erro Start error Sep 17, 2017
@oliverhavrila
Copy link
Author

I send you output from the command bellow

list | grep "Supported interface modes" -A 10
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* mesh point
* P2P-client
* P2P-GO
* outside context of a BSS
Band 1:

mh4x0f added a commit that referenced this issue Oct 7, 2017
@mh4x0f mh4x0f changed the title Start error subprocess.call() not working as expected Oct 7, 2017
@mh4x0f mh4x0f added the solved label Oct 7, 2017
@mh4x0f mh4x0f closed this as completed Oct 7, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants