> For the complete documentation index, see [llms.txt](https://ceh-practical.cavementech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ceh-practical.cavementech.com/module-8.-sniffing/3.-detect-network-sniffing.md).
# 3. Detect Network Sniffing
## 1. Detect ARP Poisoning and promiscuous mode in a switched network
If you have a doubt on a target machine, ping it.
```
hping3 -c 1000000000 192.168.18.110
```
Now open Wireshark and edit preferences. Click on protocols options
From ARP menus, select detect ARP and IP spoofing.
Click **Analyze** from the menu bar and select **Expert Information** from the drop-down options. The **Wireshark . Expert Information** window appears; click to expand the **Warning** node labeled **Duplicate IP address configured (10.10.1.11)**, running on the **ARP/RARP** protocol.
Arrange the **Wireshark . Expert Information** window above the **Wireshark** window so that you can view the packet number and the **Packet details** section. In the **Wireshark . Expert Information** window, click any packet (here, **463**).
On selecting the packet number, **Wireshark** highlights the packet, and its associated information is displayed under the packet details section. Close the **Wireshark . Expert Information** window. The warnings highlighted in yellow indicate that duplicate IP addresses have been detected at one MAC address, as shown in the screenshot.
### Nmap promiscuous/ Monitor mode detection
```
sudo nmap --script sniffer-detect 192.168.18.1
```
## 2. Detect ARP Poisoning using Capsa Network Analyzer
{% embed url="" %}
Requires use of school and work emails.
We can use hubu framework for arp poisoning
```
hubu.arp.poison 192.168.18.11 192.168.18.12
```
In the diagnosis tab, we can locate the ARP warning.
### CEH Practical Full Course
{% embed url="" %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://ceh-practical.cavementech.com/module-8.-sniffing/3.-detect-network-sniffing.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.