Re: [coLinux-devel] Strange problem with Win-TAP and coLinux

[John L. <jo...@su...>]

I've seen very similar problems when using apt-get to install large 
files(like kernel-source-2.4.24)
The download completes, then dpkg fails because the md5sum doesn't 
match.  Sounds like corrupted packets getting passed around, which makes 
me think it's the tap drivers, or the connection between colinux and the 
tap driver...

It seems to be only associated with large transfers, and not network 
load.  But at least apache works.  and php.  and postgres.

John




Ian Latter wrote:

>Hello Vlad,
>
>  I haven't seen the issues that you've reported - but I've seen some-
>thing else that's not right in the networking.
>
>  The only application included in the CHAOS file system is setiathome,
>and it fails to acquire a new workunit from the Berkeley servers.  What
>we see here is an ESTablished connection to their web server 
>(which suggests that networking "works") but we never retrieve any
>data (not even up to the first Mbyte).  Instead the connection hangs 
>with a send-q of about 350 or so.
>
>  We're testing this over two PCs (XP Pro SP1) with Bridging (mini mac)
>as the connection/networking mechanism.
>
>  I think it was the other Ian who mentioned a much later TAP driver
>from the openVPN project; maybe its worth trying that out ..  I might
>give that ago sometime in the next couple of days - see if it helps.
>
>
>
>
>----- Original Message -----
>  
>
>>From: "Vlad Doubrov" <vl...@w-...>
>>To: <col...@li...>
>>Subject:  Re: [coLinux-devel] Strange problem with Win-TAP and coLinux
>>Date: Tue, 03 Feb 2004 15:05:03 +0300
>>
>>Dan Aloni wrote:
>>
>>    
>>
>>>>The same happens when I try to transfer that file via SMB (smbd and
>>>>smbclient is installed on coLinux) - except that the file is getting
>>>>corrupted after "successful" download.
>>>>
>>>>Small files (less than 1 MB in size) get transferred very well.
>>>>
>>>>So, is it a bug in Win-TAP driver or coLinux? Any workarounds possible?
>>>>Or may be it's my misunderstood?
>>>>        
>>>>
>>>My guess is to try to using ifconfig to change eth0's MAC address.
>>>      
>>>
>>It doesn't help. According to SSH docs, "corrupted MAC on input" message
>>means that some packet was corrupted during data transfer, it doesn't
>>mean anything to ethernet MAC addresses. And as I already wrote, when I
>>try to transfer the same large file via samba it gets corrupted the
>>same way.
>>
>>I'm completely stuck out as I couldn't transfer anything larger than 1Mb
>>to the virtual linux. Does this problem appear in your enviroment? Or
>>perhaps some workarounds are possible?
>>
>>-- vlad
>>
>>
>>
>>
>>
>>-------------------------------------------------------
>>The SF.Net email is sponsored by EclipseCon 2004
>>Premiere Conference on Open Tools Development and Integration
>>See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
>>http://www.eclipsecon.org/osdn
>>_______________________________________________
>>coLinux-devel mailing list
>>coL...@li...
>>https://lists.sourceforge.net/lists/listinfo/colinux-devel
>>
>>    
>>
>
>--
>Ian Latter
>Internet and Networking Security Officer
>Macquarie University
>
> Meet me at the Australian Unix and open systems
>   User Group (AUUG) Security Symposium; 2004
>  http://www.auug.org.au/events/2004/security/
>
>
>
>-------------------------------------------------------
>The SF.Net email is sponsored by EclipseCon 2004
>Premiere Conference on Open Tools Development and Integration
>See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
>http://www.eclipsecon.org/osdn
>_______________________________________________
>coLinux-devel mailing list
>coL...@li...
>https://lists.sourceforge.net/lists/listinfo/colinux-devel
>  
>