I notice that the TCPMD5Unexpected does not increment when it should be. Specifically, according to the kernel source code (2.6.32.9) or later versions, this counter increments when three of the following happens for any incoming TCP packets: 1. it is expecting a MD5 hash in the TCP header option, but there is not. 2. it is not expecting a MD5 hash in the TCP header option, but there is one. 3. a wrong MD5 hash.
I specifically tested scenario 2 on both a standard linux machine with a slightly new kernel (2.6.38-10) and three android phones all with kernel (2.6.32.9-XXXXX). The TCPMD5Unexpected counter increments always on the linux machine but never on all three android phones. The three phones are captivate (android 2.2), nexus one (android 2.2), and atrix (android 2.2.2). The linux kernel version does not appear to be an issue as the code related to the TCPMD5Unexpected counter seems identical for both versions. Does anyone know what's possibly causing this?? Thanks a million! -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
