the emulator is just a "normal" program that uses the standard Winsock interface to access the network. If you have TCP checksum errors on a real network, this can only come from buggy network drivers, I'm afraid, since there is no way the emulator itself is generating these. That's really weird...
2009/5/6 Fabien Marchewka <fura...@gmail.com> > > Same problem on windows XP 32 bits SP3. No firewall and no antivirus, > antispam ... > I have trace but it seems to be not supported by traceview. > I have packets with incorrect tcp checksum from my host to proxy host. > host ip : 172.16.124.133 > proxy ip : 172.18.251.23 > log with wireshark : > No. Time Source Destination > Protocol Info > 1 0.000000 172.16.124.133 172.18.251.23 > TCP isg-uda-server > http-alt [ACK] Seq=1 Ack=1 Win=65535 [TCP > CHECKSUM INCORRECT] Len=0 > > Frame 1 (54 bytes on wire, 54 bytes captured) > Arrival Time: May 6, 2009 10:24:25.741972000 > [Time delta from previous captured frame: 0.000000000 seconds] > [Time delta from previous displayed frame: 0.000000000 seconds] > [Time since reference or first frame: 0.000000000 seconds] > Frame Number: 1 > Frame Length: 54 bytes > Capture Length: 54 bytes > [Frame is marked: False] > [Protocols in frame: eth:ip:tcp] > [Coloring Rule Name: Checksum Errors] > [Coloring Rule String: cdp.checksum_bad==1 || edp.checksum_bad==1 > || ip.checksum_bad==1 || tcp.checksum_bad==1 || udp.checksum_bad==1] > Ethernet II, Src: HewlettP_1d:a7:b6 (00:14:38:1d:a7:b6), Dst: > Oneacces_44:73:f5 (00:12:ef:44:73:f5) > Destination: Oneacces_44:73:f5 (00:12:ef:44:73:f5) > Address: Oneacces_44:73:f5 (00:12:ef:44:73:f5) > .... ...0 .... .... .... .... = IG bit: Individual address > (unicast) > .... ..0. .... .... .... .... = LG bit: Globally unique > address (factory default) > Source: HewlettP_1d:a7:b6 (00:14:38:1d:a7:b6) > Address: HewlettP_1d:a7:b6 (00:14:38:1d:a7:b6) > .... ...0 .... .... .... .... = IG bit: Individual address > (unicast) > .... ..0. .... .... .... .... = LG bit: Globally unique > address (factory default) > Type: IP (0x0800) > Internet Protocol, Src: 172.16.124.133 (172.16.124.133), Dst: > 172.18.251.23 (172.18.251.23) > Version: 4 > Header length: 20 bytes > Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: > 0x00) > 0000 00.. = Differentiated Services Codepoint: Default (0x00) > .... ..0. = ECN-Capable Transport (ECT): 0 > .... ...0 = ECN-CE: 0 > Total Length: 40 > Identification: 0xb8a8 (47272) > Flags: 0x04 (Don't Fragment) > 0... = Reserved bit: Not set > .1.. = Don't fragment: Set > ..0. = More fragments: Not set > Fragment offset: 0 > Time to live: 128 > Protocol: TCP (0x06) > Header checksum: 0x7267 [correct] > [Good: True] > [Bad : False] > Source: 172.16.124.133 (172.16.124.133) > Destination: 172.18.251.23 (172.18.251.23) > Transmission Control Protocol, Src Port: isg-uda-server (2551), Dst > Port: http-alt (8080), Seq: 1, Ack: 1, Len: 0 > Source port: isg-uda-server (2551) > Destination port: http-alt (8080) > Sequence number: 1 (relative sequence number) > Acknowledgement number: 1 (relative ack number) > Header length: 20 bytes > Flags: 0x10 (ACK) > 0... .... = Congestion Window Reduced (CWR): Not set > .0.. .... = ECN-Echo: Not set > ..0. .... = Urgent: Not set > ...1 .... = Acknowledgment: Set > .... 0... = Push: Not set > .... .0.. = Reset: Not set > .... ..0. = Syn: Not set > .... ...0 = Fin: Not set > Window size: 65535 > Checksum: 0xcfda [incorrect, should be 0x3e77 (maybe caused by > "TCP checksum offload"?)] > [Good Checksum: False] > [Bad Checksum: True] > > 0000 00 12 ef 44 73 f5 00 14 38 1d a7 b6 08 00 45 00 ...Ds... > 8.....E. > 0010 00 28 b8 a8 40 00 80 06 72 67 ac 10 7c 85 ac 12 . > (....@...rg..|... > 0020 fb 17 09 f7 1f 90 54 49 5a 77 87 19 42 3c 50 > 10 ......TIZw..B<P. > 0030 ff ff cf da 00 00 ...... > > > > On 5 mai, 18:23, David Turner <di...@android.com> wrote: > > 2009/5/5 stevensli <stevens...@gmail.com> > > > > > > > > > The version of Windows I am running is XP SP3, 32bit. Can this > > > problem be solved by adjusting the configuation of the emulator？ > > > Thanks! > > > > I'm just speculating at the moment, but I doubt it's related to the > > emulator's configuration. > > > > Essentially, the emulator doesn't deal very well with certain networking > > setups at the moment > > due to changes in its socket code that happened between 1.1 and 1.5. I > > suspect some interaction > > with the IPv6 localhost and a few other things. > > > > I could be wrong though, but I'll investigate. > > > > > > > > > On May 5, 11:50 pm, David Turner <di...@android.com> wrote: > > > > thanks for posting the details, they are helpful. Which exact version > of > > > > Windows are you running ? XP or Vista, 32 or 64 bit ? > > > > > > thanks in advance > > > > > > On Mon, May 4, 2009 at 12:05 PM, stevensli <stevens...@gmail.com> > wrote: > > > > > > > The -http-proxy works fine for emulator with 1.1r1 sdk, but not > work > > > > > for emulator with 1.5r1 sdk. I use those emulator on the same > > > > > development computer. The following is debug info: > > > > > > > D:\Downloads>emulator -avd avd15addon -sdcard d:\sd.iso -http-proxy > > > > > 127.0.0.1:58 > > > > > 65 -debug-proxy > > > > > proxy_http_setup: creating http proxy service connecting to: > > > > > 127.0.0.1:5865 > > > > > server name '127.0.0.1' resolved to 127.0.0.1:5865 > > > > > proxy_http_setup: creating HTTP Proxy Service Footer is (len=2): > > > > > ' > > > > > ' > > > > > http_service_connect: trying to connect to 64.233.189.104:80 > > > > > http_service_connect: using HTTP rewriter > > > > > tcp:64.233.189.104:80(1480): cannot connect to proxy: <unknown > error> > > > > > http_service_connect: trying to connect to 64.233.189.104:80 > > > > > http_service_connect: using HTTP rewriter > > > > > tcp:64.233.189.104:80(1480): cannot connect to proxy: <unknown > error> > > > > > http_service_connect: trying to connect to 64.233.189.104:80 > > > > > http_service_connect: using HTTP rewriter > > > > > tcp:64.233.189.104:80(1480): cannot connect to proxy: <unknown > error> > > > > > http_service_connect: trying to connect to 64.233.189.104:80 > > > > > http_service_connect: using HTTP rewriter > > > > > tcp:64.233.189.104:80(1480): cannot connect to proxy: <unknown > error> > > > > > http_service_connect: trying to connect to 64.233.189.104:80 > > > > > http_service_connect: using HTTP rewriter > > > > > tcp:64.233.189.104:80(1480): cannot connect to proxy: <unknown > error> > > > > > http_service_connect: trying to connect to 64.233.189.104:80 > > > > > http_service_connect: using HTTP rewriter > > > > > tcp:64.233.189.104:80(1480): cannot connect to proxy: <unknown > error> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Beginners" group. To post to this group, send email to android-beginners@googlegroups.com To unsubscribe from this group, send email to android-beginners-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~----------~----~----~----~------~----~------~--~---
