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

Post a Comment

Popular posts from this blog

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.
Post a Comment
Read more

Nginx Ingress controller setup in K8S MultiNode Cluster with HA-Proxy as External LB

https://github.com/nginxinc/kubernetes-ingress/blob/master/docs/installation.md Pre-requisites: ############### >> K8s cluster setup with 1 Master and 2 Worker nodes. >> Deployed an application with Deployment name "client-sb" >> Also you need to create an HA-proxy server by spinning an Ec2 instance. After login the Ha-proxy server. # yum install haproxy # vi /etc/haproxy/haproxy.cfg delete everything after the global and defaults starting from "Main front-end which proxys to the backend" paste the below code in the end of the file: --------------------- frontend http_front   bind *:80   stats uri /haproxy?stats   default_backend http_back backend http_back   balance roundrobin   server kube 10.0.1.14:80   server kube 10.0.1.12:80 --------------------- # systemctl status haproxy # systemctl enable haproxy # systemctl start haproxy 1. Create a Namespace, a SA, the Default Secret, the Customization Confi...
Post a Comment
Read more

Setting /etc/hosts entries during the initial deployment of an Application using k8s yaml file

Some times we have to enter specific hosts file entries to the container running inside the POD of a kubernetes deployment during the initial deployment stage itself. If these entries are not in place, the application env variables mentioned in the yaml file , as hostnames , will not resolve to the IP address and the application will not start properly. So to make sure the /etc/hosts file entries are already there after the spin up of the POD you can add the below entries in your yaml file. cat > api-deployment.yaml apiVersion: apps/v1 kind: Deployment metadata: spec:   template:     metadata:     spec:       volumes:       containers:       - image: registryserver.jinojoseph.com:5000/jinojosephimage:v1.13         lifecycle:           postStart:             exec:               command:...
Post a Comment
Read more