Re: linux tcp stack behavior change

2006-12-27 Thread Jan Engelhardt
On Dec 27 2006 03:03, Jan Engelhardt wrote: > >I have been noticing that running nmap -sF on oneself does not generate >a reply from the TCP stack on 2.6.18(.5). In other words: [...] Alright same behavior on 2.6.13 and nmap 3.81, so the problem is somewhere on my side having misdocumented some

RE: linux tcp stack behavior change

2006-12-26 Thread Askadar
> 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]