Re: linux tcp stack behavior change

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 something back then.


	-`J'
-- 
-
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/

---

• References:
  • linux tcp stack behavior change
    • From: Jan Engelhardt <[email protected]>

• Prev by Date: Re: util-linux: orphan
• Next by Date: [PATCH -rt] update kmap_atomic on !HIGHMEM
• Previous by thread: linux tcp stack behavior change
• Next by thread: RE: linux tcp stack behavior change
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]