Tech Troubleshooting Hub

Common Issues and How to Fix Them

Welcome to the Tech Troubleshooting Hub! This page is dedicated to helping you quickly resolve common issues related to network security tools, web servers, Linux, hacking and more. Whether you’re having trouble with MITM attacks in Bettercap or facing challenges accessing your Apache webserver, we’ve got the solution. Browse through the sections below for step-by-step fixes.


Issue: ARP Spoofing Not Working in Bettercap

Description:
Target machine looses internet connection once ARP spoofing attack has been initialized.

Solution:
We need our attacker machine to be able to forward data between the router and devices on the network. We therefore need to add some firewall rules and enable packet forwarding.

1. Add firewall rules

Change wlp1s0 with your interface.

sudo iptables -A FORWARD -i wlp1s0 -j ACCEPT
sudo iptables -A FORWARD -o wlp1s0 -j ACCEPT

2. Enable packet forwarding:

Open this file and uncomment the line net.ipv4.ip_forward=1

nano /etc/sysctl.conf
packet forwarding ARP

Issue: Wireshark – Cant Capture Other Machines’ Traffic

Description:
Cannot view network traffic of other devices on your network in Wireshark.

Modern Ethernet networks are connected using network switches, which enhance efficiency by ensuring that data is not sent to every device on the network. Switches “learn” which devices are connected to specific ports and route the data directly between them. This means that with a normal setup, the only traffic visible to your device would be broadcast messages and messages directly targeted your device.

Solution:
The best solution is to do an ARP spoofing attack, which which will trick other devices into thinking your device is the router, and thus forwarding all traffic to you (MITM attack).

Follow this guide on how to Sniff Network Traffic with Bettercap and Wireshark.


Issue: Cannot Access Apache From Outside My Network

Description:
Cannot access Apache webserver from the internet or from outside my network.

Solution:
If you have a webserver running on a machine in your home and you want to be able to access it from anywhere on the internet, you will have to configure port forwarding and firewall rules. Allowing HTTP, HTTPS or any service for that matter, through your home router, you will have to configure port forwarding trough your routers web interface.

1. Determine the Local IP Address of Your Machine

hostname -I

2. Login to your Router’s Web Interface

You will need to access your router’s settings through its web interface. This is usually done by typing the router’s IP address into a web browser. Common Router IP Addresses include:

  • 192.168.0.1
  • 192.168.1.1
  • 10.0.0.1

Common default credentials are:

Username: admin
Password: admin or password

Otherwise check the back of your router – here the password will most likely be displayed. If you still can’t find it, search online for the default credentials for your router model.

3. Find the Port Forwarding Section

The location of port forwarding settings varies between router brands, but it’s typically found under Access control -> Port forwarding.

web interface router

4. Set Up Port Forwarding

You’ll need to configure the port forwarding rule to forward HTTP (port 80) and HTTPS (port 443) to the internal IP address of the computer. Leave the External host field empty.

port forwarding rules

Finally click add and apply.

5. Firewall Configuration

We need to make sure our firewall allows HTTP and HTPPS traffic. Run the command below.

sudo ufw allow 'Apache Full'

6. Restart Apache

sudo systemctl restart apache2

You should now be able to access your Apache webserver from outside your local network.


We hope these solutions helped you troubleshoot your issue. Be sure to bookmark this page as we continually update it with new solutions. If you encounter a problem that isn’t listed, feel free to reach out, and we’ll look into it!

Don’t Miss Out!