failed to set hardware filter to promiscuous mode wireshark

All 3 laps are connected to same network.Ĭan anyone enlighten me the use of promiscuous mode with simple scenario?Ģ9988 is reverse(swap) of 9333, I'm just looking for that. I run the pcap executable in lap-1 hoping that I would able to capture packets transferred between lap-3 and lap-2 but pcap running in lap-1 is not able to do so with promiscuous mode on. So considering this, I made acting lap-3 as server and lap-2 remains as client. I googled about promiscuous mode and what I could infer was if device opens an interface in promiscuous mode it would able to capture all packets attached to that network.

The Hyper-V PowerShell module does a great job in making life easy from this perspective, for example. Then I turned off promiscuous mode and also in pcap_live_open function. Furthermore, Hyper-V does not let you simply set a promiscuous mode flag on a port, as you need to specify if a given port is supposed to be the source or the destination of the network packets, mirroring the traffic, hence the name.

Also in pcap_live_open method I have set promiscuous mode flag. I have turned on promiscuous mode using sudo ifconfig eth0 promisc. Click the red Stop button near the top left corner of the window when you want to stop capturing traffic.

I'm able to capture packets using pcap in lap1. To check if promiscuous mode is enabled, click Capture > Options and verify the Enable promiscuous mode on all interfaces checkbox is activated at the bottom of this window. Using netcat I sent data from lap2 to lap1. I made lap-1 as server and listen on 9333 port.

Failed to set hardware filter to promiscuous mode wireshark