Skip to main content

How to Disconnect any wifi Client/Device from your Wifi network?



 Deauthentication Attack


This attack is very useful, it allows us to disconnect any device ( whether it is a windows machine, OR android phone OR an ios phone anything connected to the wifi network ) from any network that is within our range, even if the network have encryption , even if it uses a key and we don't have that key.

For this we need to spoof our MAC address with the target client's MAC Address.,that we need to disconnect. So that we can pretent to be him and send a deauthentication packet to the router/Access point.

At the same time we need to Spoof the MAC address to the Access point/Router MAC Address, and tell the target client to re-authenticate yourself.

The program that is using for this purpose if aireplay-ng which is from the aircrack-ng package.

# aireplay-ng - - deauth [No of packets] -a [AP] [INTERFACE]

# aireplay-ng - - deauth 1000 -a 11:22:33:44:55:66 mon0 // Disconnet all clients

# aireplay-ng - - deauth [No of packets] -a [AP] -c [CLIENT][INTERFACE]

# aireplay-ng - - deauth 1000 -a 11:22:33:44:55:66 -c 00:AA:11:22:33:44 mon0 // Disconnet a specific client from an interface.

By issuing the above command, the device/ Client 00:AA:11:22:33:44 will lost the internet connection as we are sending continous 1000 deauth packets to this client. Hence his net connection will be lost and he evantually needs to re login for getting net connection in his machine.

Comments

Popular posts from this blog

K8s External Secrets integration between AWS EKS and Secrets Manager(SM) using IAM Role.

What is K8s External Secrets and how it will make your life easier? Before saying about External Secrets we will say about k8s secrets and how it will work. In k8s secrets we will create key value pairs of the secrets and set this as either pod env variables or mount them as volumes to pods. For more details about k8s secrets you can check my blog http://jinojoseph.blogspot.com/2020/08/k8s-secrets-explained.html   So in this case if developers wants to change the ENV variables , then we have to edit the k8s manifest yaml file, then we have to apply the new files to the deployment. This is a tiresome process and also chances of applying to the wrong context is high if you have multiple k8s clusters for dev / stage and Prod deployments. So in-order to make this easy , we can add all the secrets that is needed in the deployment, in the AWS Secret Manager and with the help of External secrets we can fetch and create those secrets in the k8s cluster. So what is K8s external Secret? It i...

Password reset too simplistic/systematic issue

Some time when we try to reset the password of our user in linux it will show as simple and systematic as below: BAD PASSWORD: it is too simplistic/systematic no matter how hard password you give it will show the same. Solution: ######### Check if your password is Ok with the below command, jino@ndz~$ echo 'D7y8HK#56r89lj&8*&^%&^%#56rlKJ!789l' | cracklib-check D7y8HK#56r89lj&8*&^%&^%#56rlKJ!789l: it is too simplistic/systematic Now Create a password with the below command : jino@ndz~$ echo $(tr -dc '[:graph:]' 7\xi%!W[y*S}g-H7W~gbEB4cv,9:E:K; You can see that this password will be ok with the cracklib-check. jino@ndz~$ echo '7\xi%!W[y*S}g-H7W~gbEB4cv,9:E:K;' | cracklib-check                 7\xi%!W[y*S}g-H7W~gbEB4cv,9:E:K;: OK Thats all, Thanks.

Certbot install in AWS EC2 instance Amazon machine image for HA Proxy LB Server

If you try to install certbot you will get a message like below in Amazon machine image EC2 instance. ------------------------------------------------------------ Sorry, I don't know how to bootstrap Certbot on your operating system! You will need to install OS dependencies, configure virtualenv, and run pip install manually. Please see https://letsencrypt.readthedocs.org/en/latest/contributing.html#prerequisites ------------------------------------------------------------ Fix: ###  Amazon Linux 2 doesn't have  epel-release  in its repositories, but I've found you can install the EPEL RPM package itself, and then you'll be able to install  certbot  or  certbot-nginx  from there. Download the RPM curl -O http://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm Then install it sudo yum install epel-release-latest-7.noarch.rpm Now you can install certbot sudo yum install certbot And then run it as usual sudo certb...