Closed eisengrau closed 3 years ago
Thanks for opening your first issue here! š
š Be sure to:
1. š Have a look at the Wiki and README for information
2. š Search for similar issues (open and closed)
3. āļø Provide enough information to understand, recreate and help out with your problem
4. ā¹ļø Let us know if you find a solution and please share it with us
5. š Close the issue when your problem has been solved
Ok, it seems like the issue was, that I have the deauther's SSID to hidden, and, seemingly OpenWrt didn't like that, even if I added the correct ESSID and BSSID of the deauther.
On a further note, is there a possibility to change the mode on how the deauther connects to a client? Eg. it is possible to specify in the config that the deauther should connect to an AP as a client, instead the other way around?
On a further note, is there a possibility to change the mode on how the deauther connects to a client? Eg. it is possible to specify in the config that the deauther should connect to an AP as a client, instead the other way around?
Currently not, but something I will have a look at for version 3.0 š
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Yes
Describe the error A clear and concise description of what the problem is. What do you think causes it?
Hello,
I would like to set this up as a permanent member of my network, so I can access the web interface from my other clients. I was planning to set up a new 2.4Ghz wireless client interface on one of my OpenWrt-based APs, specify the SSID/WPA key of the deauther, and route the IP address of it to my home network ones. Or just set a static interface IP for the OpenWrt device within the same range (192.168.4.100/24).
By the way, is the dhcp lease given out by the deauther is a /24 range? Or /32? Or... the question here is, multiple devices could connect to it using the default IP setup?
As I have seen in the OpenWrt logs (and on it's web inteface) that it is trying to connect, but it disconnects endlessly with the below error messages:
_(Reason: 3=DEAUTHLEAVING)
To Reproduce Steps to reproduce the behavior:
Expected behavior
OpenWrt should connect to the deauther and get an IP or establish connection with deauther as any other wireless client, eg. Windows PC
Environment (please complete the following information):
Attempts Tried deauther v2.10 and 2.50 RC
Additional context Deauther is working as expected by directly connecting to it with another wireless client, eg. Windows 10 PC and USB Wi-Fi adapter.