Repository navigation
SSH scanning is broken since commit eb79c42b057c7cb2654d0a86213edb3494b8d4fb on FreeBSD #3438
Description
Describe the bug
SSH scanning is broken since commit eb79c42
Starting Nmap 7.99SVN ( https://nmap.org ) at 2026-08-17 01:37 +0200
NSOCK ERROR [12.7810s] mksock_bind_addr(): Bind to 192.168.1.239:0 failed (IOD #1): Invalid argument (22)
NSOCK ERROR [12.7810s] mksock_bind_addr(): Bind to 192.168.1.239:0 failed (IOD #2): Invalid argument (22)
NSOCK ERROR [12.7810s] mksock_bind_addr(): Bind to 192.168.1.239:0 failed (IOD #3): Invalid argument (22)
NSOCK ERROR [12.7810s] mksock_bind_addr(): Bind to 192.168.1.239:0 failed (IOD #4): Invalid argument (22)
To Reproduce
nmap -p 22 --open -sV 192.168.1.2-254
Expected behavior
nsock shouldn't error out during scan
Version info (please complete the following information):
- OS: FreeBSD 15.1-RELEASE (amd64)
- Output of
nmap --version:
Nmap version 7.99SVN ( https://nmap.org )
Platform: amd64-portbld-freebsd15.1
Compiled with: nmap-liblua-5.4.8 openssl-3.5.6 nmap-libssh2-1.11.1 libz-1.3.2 libpcre2-10.47 libpcap-1.10.6 nmap-libdnet-1.18.0 ipv6
Compiled without:
Available nsock engines: kqueue poll select
- Output of
nmap --iflist
************************INTERFACES************************
DEV (SHORT) IP/MASK TYPE UP MTU MAC
vtnet0 (vtnet0) 192.168.1.239/24 ethernet up 1500 00:A0:98:00:83:D7
lo0 (lo0) 127.0.0.1/8 loopback up 16384
lo0 (lo0) ::1/128 loopback up 16384
lo0 (lo0) fe80:2::1/128 loopback up 16384
**************************ROUTES**************************
DST/MASK DEV METRIC GATEWAY
127.0.0.1/32 lo0 0
192.168.1.239/32 lo0 0
192.168.1.0/24 vtnet0 0
0.0.0.0/0 vtnet0 0 192.168.1.1
::1/128 lo0 0
fe80::1/128 lo0 0
::/96 lo0 0 ::1
::ffff:0.0.0.0/96 lo0 0 ::1
fe80::/64 lo0 0
ff02::/16 lo0 0 ::1
fe80::/10 lo0 0 ::1
Additional context
@bonsaiviking @dmiller-nmap
Also affects 7.991 release, let me know if you need any more information
Activity
Fix mksock_bind_addr EINVAL on FreeBSD in service/connect scans. Fixes …
Try to use the correct sockaddr size when setting source. See #3438
diizzyy commentedon Aug 22, 2026
Closing as this is now fixed