The Idea is to make outgoing Networkconnections of
Colinux via the Colinux.exe.
From the view of the user, when debian makes an apt-get
install via ftp, in windows the colinux.exe connects to
The advantage would be, that users installing Colinux
the first time, do not need to worry about the
Even more such a colinux could be moved to another pc
and started there without touching the windowssystem,
i.e. without installing neither tapi nor wincap.
But the main reason is, that both networking mechanisms
lead to problems under certain conditions and even
a) when using "Internet Connection Sharing" for TAPI,
even some local Windows Programs use this way to
connect to internet. So if using an applicationlevel
Firewall (Tiny/KerioFW 2.0.x) it is impossible to block
these Applications without blocking colinux.
b) using WinCap doesnt work on some Networkcards
(mostly WLAN). Moreover installing WinCap is a
securityhole at its own, cause also other apps have
access to wincap.
If one needs colinux to have its own virtual
networkdevice, he can still install the Tapi-Drv.
But for connecting to the Internet, routing the traffic
directly through the colinux.exe, would be much better.
What do You think? Would that be to complicated to