WPS-PIN | General Public License as defined by the Free software | Wifi library
kandi X-RAY | WPS-PIN Summary
kandi X-RAY | WPS-PIN Summary
this scripts is edited under the general public license as defined by the free software foundation. this package is distributed in the hope that it will be useful, but without any warranty; it can be used and modified and shared but should be referenced to, it cannot be sold or be used for a commercial-economical purpose. see the details in the file licence.txt that is situated in the folder of the script or visit ) the discovery of one algorithm used in wpspin have been made parallely and previously by zhaochunsheng in a c. script named computepinc83a35. as i don't known c or programming and found this out after coding the first version of wps, this bash script doesn't use a dingle line of computepinc83a35. but it had to be saved that zhaochunsheng found the main algorithm on chinese access points months before i found it on a new belkin n router, without knowing it works. the page of the author
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of WPS-PIN
WPS-PIN Key Features
WPS-PIN Examples and Code Snippets
Community Discussions
Trending Discussions on WPS-PIN
QUESTION
I am using this configuration for wifi direct connection in Raspberry PI 2 B+
...ANSWER
Answered 2019-Feb-06 at 14:21Your Raspberry Pi is probably in the P2P Group Owner (GO) role since you are manually creating a group with the p2p_group_add
command (autonomous GO) rather than letting the devices negotiate based on their GO intent values. p2p_go_intent=1
in your config would likely have no effect in this case.
The device in the GO role should run a DHCP server in order to assign IP addresses to the connecting P2P Clients. Correspondingly, each client should run a DHCP client in order to receive an IP address.
Excerpt from Section 3.2.6.1 of the Wi-Fi P2P Technical Spec:
Higher-layer data services may use IP. The P2P Group Owner shall act as a DHCP server to provide IP addresses to the connected P2P Clients that use IP. The DHCP Server shall at a minimum support Internet Protocol version 4 (IPv4) and assignment of an IP address, subnet mask...
...A P2P Client that uses IP shall be capable of acting as a DHCP Client.
Note — While a P2P Device can select distinct IP subnets for each P2P Group for which it is P2P Group Owner, it is possible that a P2P Device connected to more than one P2P Group may end up with colliding subnets. Use of a random component in the selection of IP subnet may reduce the probability of (but not eliminate) this situation occurring
I think you will find that the Android device is waiting to receive an IP configuration via DHCP before moving on to a connected state, timing out if that does not happen.
To make the connection persistent the group needs to be created as a persistent group. You should be able to do that in the autonomous GO scenario with p2p_group_add persistent
. In the negotiated GO scenario you should be able to do something like p2p_connect [display|keypad|p2ps] persistent go_intent=15
. See the wpa_supplicant README-P2P for further details: https://w1.fi/cgit/hostap/plain/wpa_supplicant/README-P2P.
Finally, the command wps_pin any
allows any device to connect using the provided PIN but restricts the PIN to one-time-use. Either use the wps_pin
form or set a new PIN by running wps_pin any
again.
QUESTION
First of all, sorry for my poor poor english. I'm trying to write a bash script in order to perform AP WPS cracking using reaver. The problem is that after trying some WPS-PINs, the AP lock the WPS so I reaver is not usefull.
To solve this, I perform a mdk3
attack to force the AP to reboot and be able to attack it again (after reboot, the WPS restarts in unlocked state).
The problem with this approach is that:
- I have to be in front of the PC locking when the AP is locked and
- making an mdk3 attack, stop it when the AP is rebooted and performing again the reaver attack. The solution to this is obviously a script.
I wrote the following lines which should solve this.
I have to say that I'm a total noob in bash scripting, so the script is not "professional", it just a "workarround" to solve my problem.
...ANSWER
Answered 2017-Feb-09 at 11:16I finally got it. I found a workaround to solve this problem, redirectirng the stdout of the commands to files. I post the script, maybe, someone could use it.
!/bin/bashCommunity Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install WPS-PIN
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page