metasploit-framework icon indicating copy to clipboard operation
metasploit-framework copied to clipboard

Nmap Error: 'Error compiling our pcap filter: expression rejects all packets'

Open Msilawedada opened this issue 1 year ago • 2 comments

Im having an issue when I use the metasploit through Nord VPN. I'm getting the following error

[*] [2024.07.01-10:43:00] Nmap Output: Starting Nmap 7.91 ( https://nmap.org ) at 2024-07-01 10:43 South Africa Standard Time
**[*] [2024.07.01-10:43:00] Nmap Error: 'Error compiling our pcap filter: expression rejects all packets'**
[*] [2024.07.01-10:43:00] Nmap Results: Importing scan data.
[+] [2024.07.01-10:43:01] Workspace:TEST03 Beginning step 3/176 Sweeping 1XX.1XX.1XX.1XX with UDP probes - Progress: 1%
[*] [2024.07.01-10:43:01] Sending 13 probes to 1XX.1XX.1XX.1XX->1XX.1XX.1XX.1XX (1 hosts)
[*] [2024.07.01-10:43:02] Discovered DNS on 1XX.1XX.1XX.1XX:53 (8f38838000010000000000000756455253494f4e0442494e440000100003)
[+] [2024.07.01-10:43:16] Workspace:TEST03 Beginning step 63/176 Sweeping 1XX.1XX.1XX.1XX with VxWorks probes - Progress: 35%
[+] [2024.07.01-10:43:27] Workspace:TEST03 Beginning step 172/176 Normalizing system information - Progress: 97%
[*] [2024.07.01-10:43:27] Beginning step 1/2 Normalizing 1XX.1XX.1XX.1XX - Progress: 0%
[*] [2024.07.01-10:43:27] Beginning step 2/2 Normalization complete - Progress: 50%
[+] [2024.07.01-10:43:27] Workspace:TEST03 Beginning step 173/176 Identifying unknown services - Progress: 97%
[+] [2024.07.01-10:43:27] Workspace:TEST03 Beginning step 174/176 Normalizing system information for newly identified services - Progress: 98%
[*] [2024.07.01-10:43:27] Beginning step 1/2 Normalizing 1XX.1XX.1XX.1XX - Progress: 0%
[*] [2024.07.01-10:43:27] Beginning step 2/2 Normalization complete - Progress: 50%
[+] [2024.07.01-10:43:27] Workspace:TEST03 Beginning step 175/176 Sweeping newly found services - Progress: 98%
[+] [2024.07.01-10:43:27] Workspace:TEST03 Beginning step 176/176 Normalizing system information for newly identified services - Progress: 99%
[*] [2024.07.01-10:43:27] Beginning step 1/2 Normalizing 1XX.1XX.1XX.1XX - Progress: 0%
[*] [2024.07.01-10:43:27] Beginning step 2/2 Normalization complete - Progress: 50%
[*] [2024.07.01-10:43:27] Sweep of 1XX.1XX.1XX.1XX-1XX.1XX.1XX.1XX complete (0 new hosts, 0 new services)
[*] [2024.07.01-10:43:27] Scanned 1 of 1 hosts (100% complete)
[+] [2024.07.01-10:43:27] Workspace:TEST03 Task Completed - Progress: 100%

However when I change the connection to use my WIFI things seem to be fine.

Msilawedada avatar Jul 01 '24 09:07 Msilawedada

It looks like there's not enough information to replicate this issue. Please provide any relevant output and logs which may be useful in diagnosing the issue.

This includes:

  • All of the item points within this template
  • The result of the debug command in your Metasploit console
  • Screenshots showing the issues you're having
  • Exact replication steps

The easier it is for us to replicate and debug an issue means there's a higher chance of this issue being resolved.

github-actions[bot] avatar Jul 01 '24 09:07 github-actions[bot]

This is most likely an issue with nmap or npcap rather than Metasploit.

  • https://github.com/nmap/npcap/issues/549

bcoles avatar Jul 01 '24 09:07 bcoles

Hi!

This issue has been left open with no activity for a while now.

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.

github-actions[bot] avatar Jul 31 '24 15:07 github-actions[bot]

Hi again!

It’s been 60 days since anything happened on this issue, so we are going to close it. Please keep in mind that I’m only a robot, so if I’ve closed this issue in error please feel free to reopen this issue or create a new one if you need anything else.

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.

github-actions[bot] avatar Sep 02 '24 15:09 github-actions[bot]