Menu
▾
▴
[coLinux-devel] [ colinux-Bugs-2688891 ] Using pcap/ndis bridge can't connent to colinux services
|
From: SourceForge.net <no...@so...> - 2009-03-16 20:17:48
|
Bugs item #2688891, was opened at 2009-03-16 18:36 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2688891&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Daemons (Windows) Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Using pcap/ndis bridge can't connent to colinux services Initial Comment: Hi, i've upgraded my really old colinux install to the lastest develoment snapshot (20090315 and 20090305 for modules and kernel). Trying to setup networking i've seen that using pcap-bridge or ndis-bridge doesn't let me to connect to the colinux machine: - if i try to do a ping from colinux to host machine all goes ok - if i try to do a ping from my host machine to colinux all goes ok - if i try to download something from the web server that resides on host machine or from internet trought colinux (using wget for example) all goes ok - if i try to connect to a netcat server or an openssh server that resieds on colinux from the host machine it doesn't do anything. - if i try to connect to a netcat server or an openssh server that resides on colinux from a machine in the lan all goes ok Doing more tests revealed that the problem is with TCP packets because i tried to set up a netcat udp server on port 53 and testing it trought nslookup shows that colinux machine recived the request. I get the same problem using ndis-bridge and using pcap-bridge: from kernel messages all seems to be ok! ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-03-16 21:17 Message: That should be simple. I have the same symptom on my Intel PCI-Express. My card is a "Realtek RTL8102E Family PCI-E Fast Ethernet NIC". I can not connect via ssh from Host to coLinux. tcpdump on coLinux or Wireshark on Windows let's see the problem: The card does not accept packets with checksum errors. To make it usable, go into network card "Hardware options" - "Extensions" - Properties: "Checksum" - and change the Value into "Disable". Here is an example session of ssh connect from host to coLinux (the failed case). tcpdump on coLinux: 20:44:36.847616 arp who-has 192.168.2.100 tell 192.168.2.104 20:44:36.847616 arp reply 192.168.2.100 is-at 00:21:85:56:fb:35 20:44:41.647688 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: TCP (6), length: 48) 192.168.2.104.22 > 192.168.2.100.1057: S, cksum 0xabbc (correct), 1094183181:1094183181(0) ack 309852530 win 5840 20:44:41.657689 IP (tos 0x0, ttl 128, id 434, offset 0, flags [DF], proto: TCP (6), length: 40) 192.168.2.100.1057 > 192.168.2.104.22: ., cksum 0x8637 (incorrect (-> 0xef50), ack 1 win 65535 20:44:53.647869 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: TCP (6), length: 48) 192.168.2.104.22 > 192.168.2.100.1057: S, cksum 0xabbc (correct), 1094183181:1094183181(0) ack 309852530 win 5840 20:44:53.647869 IP (tos 0x0, ttl 128, id 435, offset 0, flags [DF], proto: TCP (6), length: 40) 192.168.2.100.1057 > 192.168.2.104.22: ., cksum 0x8637 (incorrect (-> 0xef50), ack 1 win 65535 The same output with Wireshark on Windows: 6 5.016498 00:ff:99:88:b0:00 00:21:85:56:fb:35 ARP Who has 192.168.2.100? Tell 192.168.2.104 7 5.016521 00:21:85:56:fb:35 00:ff:99:88:b0:00 ARP 192.168.2.100 is at 00:21:85:56:fb:35 8 9.829057 192.168.2.104 192.168.2.100 TCP ssh > startron [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1460 9 9.829114 192.168.2.100 192.168.2.104 TCP [TCP Dup ACK 3#2] startron > ssh [ACK] Seq=1 Ack=1 Win=65535 [TCP CHECKSUM INCORRECT] Len=0 10 21.814002 192.168.2.104 192.168.2.100 TCP ssh > startron [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1460 11 21.814062 192.168.2.100 192.168.2.104 TCP [TCP Dup ACK 3#3] startron > ssh [ACK] Seq=1 Ack=1 Win=65535 [TCP CHECKSUM INCORRECT] Len=0 I leave this bug opened, because it would be nicer to calculate the checksum before submit it into the windows network stack. Disable the receiver is a workaround. ---------------------------------------------------------------------- Comment By: daniele_dll (daniele_dll) Date: 2009-03-16 18:45 Message: Note: when i upgraded i've launched the necessary remove/install driver as requested in readme file ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2688891&group_id=98788 |
