[coLinux-devel] [ colinux-Bugs-2042470 ] 0.8.0-20080803 pcap/ndis-bridge stop working after hours

[SourceForge.net <no...@so...>]

Bugs item #2042470, was opened at 2008-08-08 10:56
Message generated for change (Comment added) made by xuefer
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2042470&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: None
Group: v0.8.x (devel)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Xuefer (xuefer)
Assigned to: Nobody/Anonymous (nobody)
>Summary: 0.8.0-20080803 pcap/ndis-bridge stop working after hours

Initial Comment:
after some hours i fond that ndis-bridge stop working, the process is still there but ping timeout

network interface on xp: Bridge [ lan, lo ]
gentoo config: eth0=ndis-bridge,lo,00:ff:4f:0d:e7:c0

other information is same as in:
http://sourceforge.net/tracker/index.php?func=detail&aid=1952057&group_id=98788&atid=622063

----------------------------------------------------------------------

>Comment By: Xuefer (xuefer)
Date: 2008-08-13 01:22

Message:
Logged In: YES 
user_id=185131
Originator: YES

reproduced with pcap again now. be aware that its Bridge [ lan, lo ], and
i pcap/ndis-bridge on "lo".

i can pcap-bridge but not ndis-bridge on Bridge, "lo" is the only chance
to use ndis-bridge for me.

----------------------------------------------------------------------

Comment By: Xuefer (xuefer)
Date: 2008-08-12 21:55

Message:
Logged In: YES 
user_id=185131
Originator: YES

i thought i had a reason why i was using Bridge instead of lo interface
for pcap-bridge (and now ndis-bridge). i remember now. it's because exact
the same problem as this ticket.

 a. IIRC, with pcap-bridge, when it "stopped" working, i ping windows
(host) from gentoo linux (colinux guest) and it starts working again. i'm
not sure if this is a "windows bridge" problem or just a "colinux with
windows bridge" problem
 b. current test result with ndis-bridge, when it "stopped" working i can
ping router from host and from guest, but not ping/tcp between host<->guest
however arp works for host<->guest

Network Configuration:
Bridge --- WAN ----(connected to)---> router
\--------- lo ---(ndis bridge)-------> colinux


----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2008-08-11 04:40

Message:
Logged In: YES 
user_id=579204
Originator: NO

Is fixed in SVN revision 1106.

Please download the latest version (devel-20080810) from snapshots
http://www.colinux.org/snapshots/


----------------------------------------------------------------------

Comment By: Henry N. (henryn)
Date: 2008-08-10 01:40

Message:
Logged In: YES 
user_id=579204
Originator: NO

Thanks for the entry here and in bug #1952057.

It is a memory leakage in kernel memory. I can reproduce it with netio.
Download netio*.zip from http://www.ars.de/ars/ars.nsf/docs/netio
Copy the file linux-i386 into coLinux.

Run "netio -s" on a server, or perhaps on a windows host.

Run this line in coLinux:
# while true; do ./netio -b 2k -u 192.168.2.102; sleep 5; done

Now, watch Windows Taskmanager in section "Kernel-memory (KB)" the value
for "Total".
For pcap-bridge the memory goes up to +60MB over normal and it goes down
at the "sleep 5".
For ndis-bridge the memory incrased +6MB on every test loop.

WARNING!
1. pcap-bridge crashes, if it receives 4KB segemnts. That's why I tested
with parameter "-b 2k". This is perhaps an other problem.
2. After longer running ndis-bridge Windows have problems on storing
files, and can crash on shutdown.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2042470&group_id=98788