Project

General

Profile

Actions
Copy link

Bug #16523

open

NMAP - Cannot Determine Source Address for Interface

Added by Emanuel C about 2 months ago. Updated 12 days ago.

Status:
Incomplete
Priority:
Low
Assignee:
-
Category:
Nmap
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:
6100

Description

  • When issuing nmap commands with source interface, nmap refuses to use the described interface with the following output:
nmap -e "interface" -sS -oN /root/nmap.result --append-output "target subnet" 

I cannot figure out what source address to use for device "interface", does it even exist? QUITTING!
  • The interface exists and its valid in the pfSense, but it is not listed in the command "nmap --iflist"
  • "nmap --iflist" shows a different outbound interface for the target subnet while pfSense shows the valid in netstat -rn | grep "target subnet" command

Tested against pfSense Plus 25.07.1

Actions
Copy link
 #1

Updated by Kris Phillips 12 days ago

  • Status changed from New to Incomplete

Tested on 25.11. Works fine.

Shell Output - nmap -e "vtnet0" -sS -oN /root/nmap.result --append-output "172.21.92.1/32"

Starting Nmap 7.94 ( https://nmap.org ) at 2025-12-13 14:03 CST
Nmap scan report for pfSense.netgate.lan (172.21.92.1)
Host is up (0.00019s latency).
Not shown: 996 filtered tcp ports (no-response)
PORT STATE SERVICE
22/tcp open ssh
53/tcp open domain
8080/tcp open http-proxy
8443/tcp open https-alt
MAC Address: 90:EC:77:34:F0:DB (silicom)

Nmap done: 1 IP address (1 host up) scanned in 4.84 seconds

Marking Incomplete.

Actions
Copy link

Also available in: Atom PDF