-
Notifications
You must be signed in to change notification settings - Fork 3
(03) Kali Build Instructions
- OS Image to use: kali-linux-2022.4-installer-amd64.iso (or whatever the latest is)
- Guest OS Family: linux
- Guest OS version: Debian GNU/Linux 12 (64-bit)
- Hardware settings: 1 CPU / 4GB RAM / 100 GB HD / 2 NIC
- Add a second Network Adapter
- Set the Network Adaptor 1: “AdminNet”
- Set the Network Adaptor 2: “Grayspace”
- Add a second Network Adapter
During install, select “Install”
When it asks which network interface to select as primary, select eth1
The network will try to establish an IP via DHCP and this will fail.
On the next screen select “Do not configure the network at this time”
- For user, enter kali
- For password, enter toor
Then accept all defaults until you get to “write changes to disk”, change this to yes and hit continue
At “choose software to install” accept defaults and continue
At “Install the GRUB boot loader to your primary drive” select yes
At “Device for boot loader install”, select /dev/sda.
At install finished, select continue to reboot.
We didn’t set up networking during install, so we need to do that now.
Open a terminal, and do the following
sudo zsh
passwd
vi /etc/network/interfaces
Set “interfaces” to the following.
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
auto eth1
iface eth1 inet static
address 5.29.2.2/20
gateway 5.29.0.1
Save changes.
Next, you need to set the DNS resolver
vi /etc/resolv.conf
Set “resolve.conf” to the following.
Nameserver 8.8.8.8
Save Changes.
Next, restart networking and check if you got a DHCP lease on eth0
service networking restart
ip a
You should see that eth0 was given an IP in the 172.30.0.x/21 range via dhcp.
Then test the proxies ability to reach the internet from the kali box.
On kali open the firefox browser, edit settings, scroll down to the Network Settings section and click “Settings"
Then put in a proxy of 172.30.0.2 port 9999, make sure to check “Also use this proxy for HTTPS”
Then open a new tab and go to www.google.com and see if it loads. If it does then the Admin-net-DHCP server and IA-Proxy are both working correctly.
Move on to the next build.