Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Capture session could not be initiated due to error getting information on pipe or socket

Using a TP Link TL-WN722N ver.1 on Ubuntu. Installed aircrack-ng, and then run the appropriate command to try to enable monitor mode on the device. Terminal suggested that the monitor mode worked.

However in the main home screen of Wireshark that shows network activities, there was nothing on the newly created monitor mode interface. When i clicked on the inactive monitor mode interface I got the following message: "Capture session could not be initiated due to error getting information on pipe or socket.." Also - when I went into Capture>Options in wireguard, the monitor mode was not checked?? - This might suggest that the monitor mode command didn't actually work (even though terminal appeared to report it did).

Not sure what I've got to do to get this monitor mode interface working?..

Capture session could not be initiated due to error getting information on pipe or socket

Using a TP Link TL-WN722N ver.1 on Ubuntu. Ubuntu 22.04 Installed aircrack-ng, and then run the appropriate command to try to enable monitor mode on the device. Terminal suggested that the monitor mode worked.

However in the main home screen of Wireshark that shows network activities, there was nothing on the newly created monitor mode interface. When i clicked on the inactive monitor mode interface I got the following message: "Capture session could not be initiated due to error getting information on pipe or socket.." Also - when I went into Capture>Options in wireguard, the monitor mode was not checked?? - This might suggest that the monitor mode command didn't actually work (even though terminal appeared to report it did).

Not sure what I've got to do to get this monitor mode interface working?..

Capture session could not be initiated due to error getting information on pipe or socket

Using a TP Link TL-WN722N ver.1 on Ubuntu 22.04 22.04. Installed aircrack-ng, and then run the appropriate command to try to enable monitor mode on the device. Terminal suggested that the monitor mode worked.

However in the main home screen of Wireshark that shows network activities, there was nothing on the newly created monitor mode interface. When i clicked on the inactive monitor mode interface I got the following message: "Capture session could not be initiated due to error getting information on pipe or socket.." Also - when I went into Capture>Options in wireguard, the monitor mode was not checked?? - This might suggest that the monitor mode command didn't actually work (even though terminal appeared to report it did).

Not sure what I've got to do to get this monitor mode interface working?..