Chris, I think you are right. I compared the config files and the difference is clear.
"CONFIG_TCP_MD5SIG=y=y" on a ubuntu machine. "# CONFIG_TCP_MD5SIG is not set" on the android phones. Thanks! On Mon, Jul 25, 2011 at 12:30 PM, Chris Stratton <[email protected]> wrote: > On Saturday, July 23, 2011 6:05:17 PM UTC-4, qzy888 wrote: > >> 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. > > Perhaps although you say the source code is the same, the binaries are not > due to differences in the kernel config? > > A lot of android devices seem to have a /proc/config.gz - you could pull > that, unzip it, diff against your desktop and read through the differences > for anything that seems relevant. Or you could read through the relevant > source code and makefiles and see what configuration options are required to > activate it. > > -- > unsubscribe: [email protected] > website: http://groups.google.com/group/android-kernel -- unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel
