> However, I know that plain -sF worked with previous kernels. Using > nmap-4.00 on 2.6.18.5 yields the same result, so I do not think it is > caused by a change in nmap code. Could someone with 2.6.13-2.6.17 verify > that the TCP stack returned a RST?
Works for me on 2.6.18.3: [EMAIL PROTECTED] bb]# tcpdump -ni lo & [EMAIL PROTECTED] bb]# nmap localhost -n -sX -p 22 Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2006-12-26 21:26 EST 21:26:09.217187 IP 127.0.0.1.46872 > 127.0.0.1.22: FP 4139391634:4139391634(0) win 1024 urg 0 21:26:09.217355 IP 127.0.0.1.22 > 127.0.0.1.46872: R 0:0(0) ack 4139391635 win 0 Interesting ports on 127.0.0.1: PORT STATE SERVICE 22/tcp closed ssh [EMAIL PROTECTED] bb]# uname -a Linux DS-12 2.6.18-ARCH #1 SMP PREEMPT Sun Nov 19 09:14:35 CET 2006 i686 Intel(R) Pentium(R) 4 Mobile CPU 1.80GHz GenuineIntel GNU/Linux [EMAIL PROTECTED] bb]# pacman -Q kernel26 kernel26 2.6.18.3-1 - Björn - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/