Bug #2343
Packetrecorder broken ?
| Status: | Closed | Start date: | 08/06/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Resolution: | invalid | Release Note: |
Description
=[ metasploit v3.4.2-dev [core:3.4 api:1.0]
+ -- --=[ 576 exploits - 290 auxiliary
+ -- --=[ 212 payloads - 27 encoders - 8 nops
=[ svn r9960 updated today (2010.08.06)
[*] Fingerprint: Windows XP Service Pack 0 / 1 - lang:English
[*] Selected Target: Windows XP SP0/SP1 Universal
[*] Attempting to trigger the vulnerability...
meterpreter > run packetrecorder -i 192.168.0.2
[*] Starting Packet capture on interface 192
[*] Error Starting Packet Capture: Rex::Post::Meterpreter::RequestError sniffer_capture_start: Operation failed: 87
[*] Rex::Post::Meterpreter::RequestError sniffer_capture_dump: Operation failed: 87
[*] Stopping Packet sniffer...
[-] Error in script: Rex::Post::Meterpreter::RequestError sniffer_capture_stop: Operation failed: 87
History
Updated by Carlos Perez over 1 year ago
- Status changed from New to Closed
- Resolution set to invalid
you are giving it the wrong value, you should give it the interface ID not the IP, normaly this would be the ID 1 on most systems, on multi-homed systems do
meterpreter > use sniffer
Loading extension sniffer...success.
meterpreter > sniffer_interfaces
1 - 'Intel(R) PRO/1000 MT Network Connection' ( type:0 mtu:1514 usable:true dhcp:false wifi:false )
and you can determine the index of the card to use for sniffing.