Exploring Technology with FromedToTechJourney.xyz

‹ Back

 

Wifi-Hacking

 

Currently in my Ethical Hacking journey, I am not sure about how to complete write-ups for the things that I accomplish in my Home-Lab.  The following post below tracks the steps I took and my experience with Wifi Hacking my home lab.

 

I participated in the Career Village at the Diana Initiative conference during Hacker Summer Camp.  One speaker in particular, Kat Fitzgerald encouraged us to build and practice in our Home Labs.  One suggestion she made was to scan our home networks.  That is not what this blog post is about.  I was captivated by Kat sharing how people create imposter wifi's.  I wanted to see if I could do something like that in my home.  I found a video on YouTube by NetworkChuck on the 3 Levels of WiFi Hacking.  I am currently a Level 1 Hacker or as he puts it, a Noob Hacker.  I conducted a Man in the Middle attack.

I built a Virtual Machine this summer using VMWare Fusion on my Mac.  I installed Kali Linux on the VM.  Somehow as I started watching NetworkChuck's video, I derailed myself and built this website.  When I logged into my VM, I had to update my Kali Linux in the terminal by  adding "sudo apt update" and then "sudo apt upgrade -y" in my terminal.  NetworkChuck suggested the commands be chained but my environment didn't like those commands, "sudo apt update && sudo apt upgrade -y".

He then told me to fire up my Kali Linux and get Bettercap running on the system.  I ran the "sudo bettercap -iface eth0" command per the NetworkChuck's instruction and that didn't work for me.  I received the error message, "cp: cannot stat 'bettercap': No such file or directory".  Instead I did some googling and found the following commands to help:

git clone https://github.com/bettercap/bettercap

cd bettercap

make build

sudo make install

 

Well those commands worked until I got to sudo make install.  That is when things stopped working for me.  I then decided to go back to the terminal and run the command, "sudo bettercap".  That did the trick.  My terminal was now looking like NetworkChuck's screen with slight modifications to get there.  

 

My screen now said gateway monitor started ...

 

I add the command, "net.probe on".  That command made the terminal state, "net.probe starting net.recon as a requirement for net.probe".  Lastly, I ran the command "net.show".