You can subscribe to this list here.
2004 |
Jan
(64) |
Feb
(530) |
Mar
(266) |
Apr
(580) |
May
(360) |
Jun
(161) |
Jul
(185) |
Aug
(164) |
Sep
(123) |
Oct
(160) |
Nov
(59) |
Dec
(84) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(156) |
Feb
(95) |
Mar
(124) |
Apr
(81) |
May
(79) |
Jun
(179) |
Jul
(35) |
Aug
(64) |
Sep
(56) |
Oct
(57) |
Nov
(18) |
Dec
(41) |
2006 |
Jan
(65) |
Feb
(37) |
Mar
(59) |
Apr
(73) |
May
(65) |
Jun
(27) |
Jul
(54) |
Aug
(76) |
Sep
(103) |
Oct
(23) |
Nov
(45) |
Dec
(29) |
2007 |
Jan
(41) |
Feb
(47) |
Mar
(61) |
Apr
(24) |
May
(14) |
Jun
(6) |
Jul
(23) |
Aug
(30) |
Sep
(16) |
Oct
(9) |
Nov
(53) |
Dec
(36) |
2008 |
Jan
(19) |
Feb
(49) |
Mar
(74) |
Apr
(21) |
May
(24) |
Jun
(5) |
Jul
(9) |
Aug
(53) |
Sep
(26) |
Oct
(23) |
Nov
(32) |
Dec
(19) |
2009 |
Jan
(47) |
Feb
(49) |
Mar
(39) |
Apr
(61) |
May
(28) |
Jun
(19) |
Jul
(12) |
Aug
(10) |
Sep
(31) |
Oct
(16) |
Nov
(60) |
Dec
(26) |
2010 |
Jan
(17) |
Feb
(9) |
Mar
(32) |
Apr
(11) |
May
(24) |
Jun
(33) |
Jul
(5) |
Aug
(2) |
Sep
(7) |
Oct
(8) |
Nov
(17) |
Dec
(7) |
2011 |
Jan
(12) |
Feb
(16) |
Mar
(2) |
Apr
(12) |
May
(5) |
Jun
(10) |
Jul
(3) |
Aug
(3) |
Sep
(2) |
Oct
(1) |
Nov
(17) |
Dec
(1) |
2012 |
Jan
(9) |
Feb
(9) |
Mar
(8) |
Apr
(4) |
May
(2) |
Jun
(1) |
Jul
(4) |
Aug
(8) |
Sep
(11) |
Oct
(1) |
Nov
(2) |
Dec
(2) |
2013 |
Jan
|
Feb
(7) |
Mar
(4) |
Apr
(10) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
(3) |
2016 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
From: SourceForge.net <no...@so...> - 2008-08-29 16:26:33
|
Feature Requests item #1898496, was opened at 2008-02-21 08:05 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1898496&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: None Status: Open Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: prepackaged GUI image Initial Comment: The slashdot discussion (http://developers.slashdot.org/developers/04/04/12/211236.shtml?tid=106) shows quite well that many users would find it easier if there was a prepackaged version that comes with all the necessary programs and configs to easily run a UI (i.e. X11/KDE) version on top of coLinux. Something like this would preferably come with the necessary X server for the windows side of things and be sufficiently preconfigured ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-08-29 16:26 Message: Logged In: NO The following site contains a listing of available GUI toolkit bindings for python, including a section about UI-building toolkits (e.g. dialog editors): http://wiki.python.org/moin/GuiProgramming In addition, here's a site providing a full tutorial about PyQT programming: http://www.commandprompt.com/community/pyqt/book1 http://wiki.python.org/moin/PyQt PythonStudio includes a full GUI editor, as well: http://www.codeplex.com/IronPythonStudio ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-08-29 06:57 Message: Logged In: NO thinking about it, the most promising approach would probably be to simply implement this totally separate, using a scripting language and a GUI toolkit, i.e. something like python or ruby with GTK/QT bindings. This way, it would not unnecessarily affect any of the existing code, would be very much straight forward and also flexible and easily extendsible for future changes ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-08-29 06:24 Message: Logged In: NO something like this would probably be best implemented as a separate, standaline "profile manager", so that creating/editing and deleting profiles can be done via this app, and starting a profile would only entail passing the stored parameters to the corresponding binaries, this would keep the overhead to a minimum. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-08-29 06:03 Message: Logged In: NO see "andLinux" however, usability could still be somewhat improved for users with a non-nix background, in particular the whole setup process should either be more intuitive or simply provide some more GUI frontends, i.e. by allowing the most common actions to be directly done from the executables via UI means, rather than requiring users to pass lots of cryptic options via command line parameters. In this context, it would already be a significant improvement if the most basic and relevant parameters could be configured via some sort of GUI frontend, be it embedded or not, so that running a process without REQUIRED parameters automatically brings up a dialog for users to configure the most important parameters, and optionally save them as startup profiles, so that they may next time select a startup profile or create a new one. Similar to how firefox starts actually: provide a way for customization, preferably using lots of nifty tooltips and explanations and once a user has a working config, enable them to save and reuse configs ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1898496&group_id=98788 |
From: SourceForge.net <no...@so...> - 2008-08-29 06:57:27
|
Feature Requests item #1898496, was opened at 2008-02-21 08:05 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1898496&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: None Status: Open Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: prepackaged GUI image Initial Comment: The slashdot discussion (http://developers.slashdot.org/developers/04/04/12/211236.shtml?tid=106) shows quite well that many users would find it easier if there was a prepackaged version that comes with all the necessary programs and configs to easily run a UI (i.e. X11/KDE) version on top of coLinux. Something like this would preferably come with the necessary X server for the windows side of things and be sufficiently preconfigured ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-08-29 06:57 Message: Logged In: NO thinking about it, the most promising approach would probably be to simply implement this totally separate, using a scripting language and a GUI toolkit, i.e. something like python or ruby with GTK/QT bindings. This way, it would not unnecessarily affect any of the existing code, would be very much straight forward and also flexible and easily extendsible for future changes ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-08-29 06:24 Message: Logged In: NO something like this would probably be best implemented as a separate, standaline "profile manager", so that creating/editing and deleting profiles can be done via this app, and starting a profile would only entail passing the stored parameters to the corresponding binaries, this would keep the overhead to a minimum. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-08-29 06:03 Message: Logged In: NO see "andLinux" however, usability could still be somewhat improved for users with a non-nix background, in particular the whole setup process should either be more intuitive or simply provide some more GUI frontends, i.e. by allowing the most common actions to be directly done from the executables via UI means, rather than requiring users to pass lots of cryptic options via command line parameters. In this context, it would already be a significant improvement if the most basic and relevant parameters could be configured via some sort of GUI frontend, be it embedded or not, so that running a process without REQUIRED parameters automatically brings up a dialog for users to configure the most important parameters, and optionally save them as startup profiles, so that they may next time select a startup profile or create a new one. Similar to how firefox starts actually: provide a way for customization, preferably using lots of nifty tooltips and explanations and once a user has a working config, enable them to save and reuse configs ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1898496&group_id=98788 |
From: SourceForge.net <no...@so...> - 2008-08-29 06:29:19
|
Feature Requests item #2081864, was opened at 2008-08-29 06:29 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=2081864&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: None Status: Open Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: properly register coLinux as a service Initial Comment: if coLinux is fully registered as a service, it can be easily managed from the windows control panel, without necessarily requiring console commands to be executed manually by the user ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=2081864&group_id=98788 |
From: SourceForge.net <no...@so...> - 2008-08-29 06:25:04
|
Feature Requests item #1898496, was opened at 2008-02-21 08:05 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1898496&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: None Status: Open Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: prepackaged GUI image Initial Comment: The slashdot discussion (http://developers.slashdot.org/developers/04/04/12/211236.shtml?tid=106) shows quite well that many users would find it easier if there was a prepackaged version that comes with all the necessary programs and configs to easily run a UI (i.e. X11/KDE) version on top of coLinux. Something like this would preferably come with the necessary X server for the windows side of things and be sufficiently preconfigured ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-08-29 06:24 Message: Logged In: NO something like this would probably be best implemented as a separate, standaline "profile manager", so that creating/editing and deleting profiles can be done via this app, and starting a profile would only entail passing the stored parameters to the corresponding binaries, this would keep the overhead to a minimum. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-08-29 06:03 Message: Logged In: NO see "andLinux" however, usability could still be somewhat improved for users with a non-nix background, in particular the whole setup process should either be more intuitive or simply provide some more GUI frontends, i.e. by allowing the most common actions to be directly done from the executables via UI means, rather than requiring users to pass lots of cryptic options via command line parameters. In this context, it would already be a significant improvement if the most basic and relevant parameters could be configured via some sort of GUI frontend, be it embedded or not, so that running a process without REQUIRED parameters automatically brings up a dialog for users to configure the most important parameters, and optionally save them as startup profiles, so that they may next time select a startup profile or create a new one. Similar to how firefox starts actually: provide a way for customization, preferably using lots of nifty tooltips and explanations and once a user has a working config, enable them to save and reuse configs ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1898496&group_id=98788 |
From: SourceForge.net <no...@so...> - 2008-08-29 06:06:29
|
Feature Requests item #2081835, was opened at 2008-08-29 06:06 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=2081835&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: None Status: Open Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: add "andLinux" to repository of downloadable colinux images Initial Comment: it would be nice for users to also have the option to directly download an andLinux image ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=2081835&group_id=98788 |
From: SourceForge.net <no...@so...> - 2008-08-29 06:05:07
|
Feature Requests item #2081833, was opened at 2008-08-29 06:05 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=2081833&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: None Status: Open Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: installer:detect availability/lack of winpcap Initial Comment: the winpcap-related dialog during installation is even shown if it is available, it would be better if winpcap/and its version could be dynamically detected by the installer ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=2081833&group_id=98788 |
From: SourceForge.net <no...@so...> - 2008-08-29 06:03:05
|
Feature Requests item #1898496, was opened at 2008-02-21 08:05 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1898496&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: None Status: Open Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: prepackaged GUI image Initial Comment: The slashdot discussion (http://developers.slashdot.org/developers/04/04/12/211236.shtml?tid=106) shows quite well that many users would find it easier if there was a prepackaged version that comes with all the necessary programs and configs to easily run a UI (i.e. X11/KDE) version on top of coLinux. Something like this would preferably come with the necessary X server for the windows side of things and be sufficiently preconfigured ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-08-29 06:03 Message: Logged In: NO see "andLinux" however, usability could still be somewhat improved for users with a non-nix background, in particular the whole setup process should either be more intuitive or simply provide some more GUI frontends, i.e. by allowing the most common actions to be directly done from the executables via UI means, rather than requiring users to pass lots of cryptic options via command line parameters. In this context, it would already be a significant improvement if the most basic and relevant parameters could be configured via some sort of GUI frontend, be it embedded or not, so that running a process without REQUIRED parameters automatically brings up a dialog for users to configure the most important parameters, and optionally save them as startup profiles, so that they may next time select a startup profile or create a new one. Similar to how firefox starts actually: provide a way for customization, preferably using lots of nifty tooltips and explanations and once a user has a working config, enable them to save and reuse configs ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=1898496&group_id=98788 |
From: SourceForge.net <no...@so...> - 2008-08-28 02:21:45
|
Bugs item #927741, was opened at 2004-04-01 19:05 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=927741&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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Marti (sipsick) Assigned to: Dan Aloni (da-x) Summary: Lack of entropy - empty /dev/random Initial Comment: This is not exactly a bug, but a big misfeature. Since coLinux doesn't collect entropy, the entropy pool is constantly empty, which is the cause of /dev/random being empty. Applications that rely on it will just freeze don't work. I think coLinux should use some legacy methods for entropy collection, or at least temporarily provide urandom or other sources. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-08-28 02:21 Message: Logged In: NO $ equery uses apr [ Found these USE variables for dev-libs/apr-1.3.2 ] + + urandom : Use /dev/urandom instead of /dev/random it's lucky that i'm using gentoo so i can use urandom for it so my subversion works "just fine". good to know i can "Create a link from /dev/urandom to /dev/random" to slow problems beside apr. but if the entropy is not enough, it's unsecure. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2007-09-24 18:52 Message: Logged In: YES user_id=579204 Originator: NO The branch devel (from snapshot) with kernel 2.6.22 uses Networking interrupts for entropy. That is not the best, but better as blocking. ---------------------------------------------------------------------- Comment By: GingGangGoolies (simon_dainty) Date: 2006-08-16 18:52 Message: Logged In: YES user_id=1233451 While this doesn't resolve the issue it is a "quick fix" that may go some way to alleviating the noted problem: * Create a link from /dev/urandom to /dev/random ---------------------------------------------------------------------- Comment By: Mark Bulas (jalthar) Date: 2005-04-29 15:49 Message: Logged In: YES user_id=493291 This is a huge issue for me as well. I've actually resorted to doing the following on my coLinux installation: mv /dev/random /dev/random.orig ln /dev/urandom /dev/random ...as this appears to be the only way to get any kind of random-number stuff out of the system. May not be very random, so you can't trust this for any kind of real cryptographic security, but at least programs that rely upon /dev/random (Subversion, et al) will now work without manual intervention. ---------------------------------------------------------------------- Comment By: Marius Huse Jacobsen (mahuja) Date: 2004-09-12 20:04 Message: Logged In: YES user_id=206105 In many cases, it's better that it remains 'unsolved' - for things like crypto, it's 'not sending' versus 'sending weakly encrypted'. If your life depends on the confidentiality of a message, you'd prefer it not being sent. ---------------------------------------------------------------------- Comment By: Clifford Caoile (piyo) Date: 2004-09-03 22:41 Message: Logged In: YES user_id=3562 According to the wiki's page "RandomNotes" (http://www.colinux.org/wiki/index.php/RandomNotes), you can work around this bug/misfeature by typing something in the ftlk console. This will serve as the entropy source for a little while at least. For example when using Subversion and committing a source change (svn commit), you may need to do this workaround for about 5 seconds. (Monkeys to typewriters: start!) Why can't colinux collect entropy from the network as a stop-gap feature? I have heard that collecting entropy from the network is not random enough (or a security problem), though. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-04-10 07:15 Message: Logged In: NO There seems to be similar issue in UML too. Agree with you that it is quite a bit misfeature. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=927741&group_id=98788 |
From: SourceForge.net <no...@so...> - 2008-08-27 06:33:44
|
Bugs item #2077641, was opened at 2008-08-27 09:33 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2077641&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: eugenesan (eugenesan) Assigned to: Nobody/Anonymous (nobody) Summary: Randoms Windows XPSP3 hangs Initial Comment: Hi, I've noticed that builds created in last several months randomly crashes or hangs my host system. In earlier versions BSOD with linux.sys failure would appear and on builds since ~1/7/2008 Windows just hangs... I must notice that there where also some changes to my host system(not sure if changes and crashes appeared simultaneously): * CPU Pentium M => Core2Duo (IBM T43->T61) * Windows SP2 => SP3 * No other notable changes performed In addition crashes appears regardless usage of: * cobd or scsi * cobd async or sync * pcap-bridnge or ndis-bridge My coLinux starts as service using following command: "C:\Program Files\coLinux\colinux-daemon.exe" --run-service:D:\My Apps\Batch "coLinux" mem=512 kernel="C:\Program Files\coLinux\vmlinux" exec0="D:\My Apps\pulseaudio\pulseaudio.exe" scsi0=disk,"\\.\PhysicalDrive0" cofs0=c:\ cofs1=d:\ root=/dev/sda2 eth1=ndis-bridge,"Local","00:xx:xx:xx:xx:2B" eth2=ndis-bridge,"VirtualCoLinux","00:xx:xx:xx:xx:00" eth3=tuntap,"VirtualCoLinux","00:xx:xx:xx:xx:60" ttys0=COM5,"BAUD=115200 PARITY=n DATA=8 STOP=1 dtr=on rts=on" * cofs almost never used * ttys almost never used, but serial physically hooked to device and probably gets some data on RX once a while. * VirtualCoLinux is coLinux TAP device used both as Host-Only and NAT gateway (I am using VMWARE network stack for NAT/DHCP). * partitions (of course) never cross-mounted * no signs of errors of any kind from linux side(but, maybe, some random networking outages) * Crashes tends to appear only when is xserver running (via freenx). Lately system hangs on almost every X session init :-( I am looking into effective way for debugging that issue and possible suggestions about problems my configuration may have. Thanks ahead ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2077641&group_id=98788 |
From: coLinux a. <col...@he...> - 2008-08-24 04:11:19
|
The autobuild system has detected a new revision in the source repository. Review last changed from changelog.txt, also attached in mail. Download the compiled version: http://www.henrynestler.com/colinux/autobuild/devel-20080823/ colinux-0.8.0-20080823.src.tgz (692432 Bytes) daemons-0.8.0-20080823.dbg.zip (1348625 Bytes) daemons-0.8.0-20080823.zip (1046616 Bytes) modules-2.6.22.18-co-0.8.0-20080823.tgz (2602705 Bytes) vmlinux-2.6.22.18-co-0.8.0-20080823.zip (1762587 Bytes) Note, the autobuild compilation does not include an installer. Remember to reload the driver with these commands: colinux-daemon.exe --remove-driver colinux-daemon.exe --install-driver Inside coLinux please update modules as follow: rm -rf /lib/modules/*-co-* tar -xzf modules-*-co-*-20080823.tgz -C / The autobuild compilations are not official releases of Cooperative Linux software. There is no warranty that any autobuild version is stable. If use this autobuild version, please give us feedback of your experience. Job runs on machine with 64 bit version of gcc 4.1.2. A service from http://gcc.gnu.org/wiki/CompileFarm -- Lots of fun with newest version, Henry Nestler ------------------------------------------------------------------------ r1118 | henryn | 2008-08-23 14:15:00 +0000 (Sat, 23 Aug 2008) | 2 lines Changed paths: M /branches/devel/patch/base-2.6.22.diff * IRQF_DISABLED global for all virtual interupts. Avoids nested hardware interrupts inside proxy_interrupt_handler. ------------------------------------------------------------------------ |
From: coLinux a. <col...@he...> - 2008-08-22 04:11:41
|
The autobuild system has detected a new revision in the source repository. Review last changed from changelog.txt, also attached in mail. Download the compiled version: http://www.henrynestler.com/colinux/autobuild/devel-20080821/ colinux-0.8.0-20080821.src.tgz (692289 Bytes) daemons-0.8.0-20080821.dbg.zip (1348617 Bytes) daemons-0.8.0-20080821.zip (1046604 Bytes) modules-2.6.22.18-co-0.8.0-20080821.tgz (2602706 Bytes) vmlinux-2.6.22.18-co-0.8.0-20080821.zip (1762591 Bytes) Note, the autobuild compilation does not include an installer. Remember to reload the driver with these commands: colinux-daemon.exe --remove-driver colinux-daemon.exe --install-driver Inside coLinux please update modules as follow: rm -rf /lib/modules/*-co-* tar -xzf modules-*-co-*-20080821.tgz -C / The autobuild compilations are not official releases of Cooperative Linux software. There is no warranty that any autobuild version is stable. If use this autobuild version, please give us feedback of your experience. Job runs on machine with 64 bit version of gcc 4.1.2. A service from http://gcc.gnu.org/wiki/CompileFarm -- Lots of fun with newest version, Henry Nestler ------------------------------------------------------------------------ r1117 | henryn | 2008-08-21 21:13:38 +0000 (Thu, 21 Aug 2008) | 6 lines Changed paths: M /branches/devel/patch/base-2.6.22.diff M /branches/devel/patch/cobd-async-2.6.22.diff * Improvement for co_callback interrupt handling. co_idle_processor: Disable interrupts before call co_callback. proxy_interrupt_handler is called from assembler with disabled interrupts. co_callback is running completely on disabled interrupts now. Remove save/restore flags for co_callback handling. ------------------------------------------------------------------------ |
From: coLinux a. <col...@he...> - 2008-08-21 04:13:27
|
The autobuild system has detected a new revision in the source repository. Review last changed from changelog.txt, also attached in mail. Download the compiled version: http://www.henrynestler.com/colinux/autobuild/devel-20080820/ colinux-0.8.0-20080820.src.tgz (692338 Bytes) daemons-0.8.0-20080820.dbg.zip (1348623 Bytes) daemons-0.8.0-20080820.zip (1046608 Bytes) modules-2.6.22.18-co-0.8.0-20080820.tgz (2602803 Bytes) vmlinux-2.6.22.18-co-0.8.0-20080820.zip (1762379 Bytes) Note, the autobuild compilation does not include an installer. Remember to reload the driver with these commands: colinux-daemon.exe --remove-driver colinux-daemon.exe --install-driver Inside coLinux please update modules as follow: rm -rf /lib/modules/*-co-* tar -xzf modules-*-co-*-20080820.tgz -C / The autobuild compilations are not official releases of Cooperative Linux software. There is no warranty that any autobuild version is stable. If use this autobuild version, please give us feedback of your experience. Job runs on machine with 64 bit version of gcc 4.1.2. A service from http://gcc.gnu.org/wiki/CompileFarm -- Lots of fun with newest version, Henry Nestler ------------------------------------------------------------------------ r1116 | henryn | 2008-08-20 20:08:57 +0000 (Wed, 20 Aug 2008) | 3 lines Changed paths: M /branches/devel/patch/base-2.6.22.diff * co_handle_jiffies: write_seqlock_irq replaced with write_seqlock_irqsave. Bugfix recursions of proxy_interrupt_handler and later kmalloc deadlocks. ------------------------------------------------------------------------ |
From: coLinux a. <col...@he...> - 2008-08-20 04:11:48
|
The autobuild system has detected a new revision in the source repository. Review last changed from changelog.txt, also attached in mail. Download the compiled version: http://www.henrynestler.com/colinux/autobuild/devel-20080819/ colinux-0.8.0-20080819.src.tgz (692377 Bytes) daemons-0.8.0-20080819.dbg.zip (1348617 Bytes) daemons-0.8.0-20080819.zip (1046607 Bytes) modules-2.6.22.18-co-0.8.0-20080819.tgz (2602790 Bytes) vmlinux-2.6.22.18-co-0.8.0-20080819.zip (1762381 Bytes) Note, the autobuild compilation does not include an installer. Remember to reload the driver with these commands: colinux-daemon.exe --remove-driver colinux-daemon.exe --install-driver Inside coLinux please update modules as follow: rm -rf /lib/modules/*-co-* tar -xzf modules-*-co-*-20080819.tgz -C / The autobuild compilations are not official releases of Cooperative Linux software. There is no warranty that any autobuild version is stable. If use this autobuild version, please give us feedback of your experience. Job runs on machine with 64 bit version of gcc 4.1.2. A service from http://gcc.gnu.org/wiki/CompileFarm -- Lots of fun with newest version, Henry Nestler ------------------------------------------------------------------------ r1115 | henryn | 2008-08-19 19:19:48 +0000 (Tue, 19 Aug 2008) | 7 lines Changed paths: M /branches/devel/patch/base-2.6.22.diff Fix for "BUG at ...ux-2.6.22.18-source/include/linux/cooperative_internal.h:100". Found by heavy network traffic with testing tool "netio". In co_callback passage page must free before calling co_message_add_to_incoming, because kmalloc needs to call host system for mapping pages. Revert parts of SVN revision 869, and use temp_storage as buffer. ------------------------------------------------------------------------ r1114 | henryn | 2008-08-19 18:28:17 +0000 (Tue, 19 Aug 2008) | 1 line Changed paths: M /branches/devel/patch/base-2.6.22.diff * Bug in __alloc_pages: After label "nopage:" page is NULL, and should no access. ------------------------------------------------------------------------ |
From: SourceForge.net <no...@so...> - 2008-08-19 18:16:29
|
Bugs item #2046284, was opened at 2008-08-11 13:07 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2046284&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.7.x (release) >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Paul Rouse (p_rouse) Assigned to: Henry N. (henryn) Summary: Slirp built-in DNS broken by 0.7.3-2 Initial Comment: The built-in DNS on 10.0.2.3 in slirp appears to have been broken by the update 0.7.3-2 to colinux-slirp-net-daemon.exe to fix bug 1995862 ("udp forwarded packets over slirp have incorrect source ip"). The issue is that the reply packets to the DNS requests now appear to come from the real DNS server, rather than the virtual one on 10.0.2.3. With the original 0.7.3 release tcpdump gives: 11:44:02.799135 IP 10.0.2.15.32772 > 10.0.2.3.53: 38764+ A? sourceforge.net. (33) 11:44:02.809134 IP 10.0.2.3.53 > 10.0.2.15.32772: 38764 1/0/0 A 216.34.181.60 (49) With the updated slirp daemon tcpdump shows: 11:49:45.149746 IP 10.0.2.15.32776 > 10.0.2.3.53: 23720+ A? sourceforge.net. (33) 11:49:45.149746 IP 172.21.1.201.53 > 10.0.2.15.32776: 23720 1/0/0 A 216.34.181.60 (49) 11:49:45.149746 IP 10.0.2.15 > 172.21.1.201: ICMP 10.0.2.15 udp port 32776 unreachable, length 85 Surely the original behaviour is what you want in the special case of DNS on 10.0.2.3. I am using a static configuration for the slirp interface, giving 10.0.2.3 explicitly as the DNS server, and the address 172.21.1.201 is the real DNS server which Windows is using. ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2008-08-19 20:16 Message: Logged In: YES user_id=579204 Originator: NO Thanks. File colinux-slirp-net-daemon-0.7.3-3.zip is available on SF now. ---------------------------------------------------------------------- Comment By: Paul Rouse (p_rouse) Date: 2008-08-18 21:59 Message: Logged In: YES user_id=260279 Originator: YES Thank you -- yes, that solves the DNS problem. I don't have a test for Bug #1995862 (that was someone else's) so I won't comment on that. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-08-17 22:55 Message: Logged In: YES user_id=579204 Originator: NO Ok, I see. Thanks for reporting. This should fix it: http://www.henrynestler.com/colinux/testing/stable-0.7.3/20080817-slirp/colinux-slirp-net-daemon-0.7.3-3.zip Hope the Bug #1995862 is working too now. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2046284&group_id=98788 |
From: SourceForge.net <no...@so...> - 2008-08-19 18:06:13
|
Bugs item #1995862, was opened at 2008-06-17 11:33 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1995862&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.7.x (release) >Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Mike Frysinger (vapier) Assigned to: Nobody/Anonymous (nobody) Summary: udp forwarded packets over slirp have incorrect source ip Initial Comment: after upgrading from coLinux 0.7.1 to 0.7.3, my TFTP connection failed. the coLinux setup is: eth0=slirp,,tcp:22:22/tcp:333:22/tcp:10000:10000/udp:69:69 connecting from an external machine (named "G5") to the windows machine which forwards port 69 (tftp) to the colinux system which is running a tftp server running tcpdump against 0.7.1 shows: 01:34:47.410000 IP G5.60808 > 10.0.2.15.tftp: 15 RRQ "moo" netascii running tcpdump against 0.7.3 shows: 01:44:45.645802 IP 10.0.2.2.33431 > 10.0.2.15.tftp: 15 RRQ "moo" netascii for some reason the forwarded packet had the source IP changed from the real external machine (G5) to the windows' side of the slirp tunnel (10.0.2.2). this means the tftp server then attempts to reply to "10.0.2.2" instead of "G5" and things obviously fail. merely replacing 'colinux-slirp-net-daemon.exe' in 0.7.3 with the version from 0.7.1 allows things to work as expected under 0.7.3 tcp forwarded packets work with both versions though, so it seems like a udp-specific issue ? ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2008-08-19 20:06 Message: Logged In: YES user_id=579204 Originator: NO OK, thanks. Changes are in SVN revision 1112 (devel) and 1113 (stable) now. ---------------------------------------------------------------------- Comment By: Mike Frysinger (vapier) Date: 2008-08-19 07:35 Message: Logged In: YES user_id=114429 Originator: YES my udp tftp server still works with that version ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-08-17 22:56 Message: Logged In: YES user_id=579204 Originator: NO Vapier, on the 0.7.3-2 was an error with DNS, related from the change for the bug you opened. I was changing the UDP receiver source again to handle both casees correctly. Check the working tftp server with this update please: http://www.henrynestler.com/colinux/testing/stable-0.7.3/20080817-slirp/colinux-slirp-net-daemon-0.7.3-3.zip ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-06-27 22:39 Message: Logged In: YES user_id=579204 Originator: NO Some lines in source was missing to change between SVN revisions 479 and 480, you have mailed me. Many thanks for your details. Bug has been fixed in SVN revision 1060 (stable) and 1061 (devel) now. An update colinux-slirp-net-daemon-0.7.3-2.zip is available from SF file releases: http://downloads.sourceforge.net/colinux/coLinux-0.7.2-src.tar.gz?download ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1995862&group_id=98788 |
From: SourceForge.net <no...@so...> - 2008-08-19 05:36:00
|
Bugs item #1995862, was opened at 2008-06-17 05:33 Message generated for change (Comment added) made by vapier You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1995862&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.7.x (release) Status: Open Resolution: Fixed Priority: 5 Private: No Submitted By: Mike Frysinger (vapier) Assigned to: Nobody/Anonymous (nobody) Summary: udp forwarded packets over slirp have incorrect source ip Initial Comment: after upgrading from coLinux 0.7.1 to 0.7.3, my TFTP connection failed. the coLinux setup is: eth0=slirp,,tcp:22:22/tcp:333:22/tcp:10000:10000/udp:69:69 connecting from an external machine (named "G5") to the windows machine which forwards port 69 (tftp) to the colinux system which is running a tftp server running tcpdump against 0.7.1 shows: 01:34:47.410000 IP G5.60808 > 10.0.2.15.tftp: 15 RRQ "moo" netascii running tcpdump against 0.7.3 shows: 01:44:45.645802 IP 10.0.2.2.33431 > 10.0.2.15.tftp: 15 RRQ "moo" netascii for some reason the forwarded packet had the source IP changed from the real external machine (G5) to the windows' side of the slirp tunnel (10.0.2.2). this means the tftp server then attempts to reply to "10.0.2.2" instead of "G5" and things obviously fail. merely replacing 'colinux-slirp-net-daemon.exe' in 0.7.3 with the version from 0.7.1 allows things to work as expected under 0.7.3 tcp forwarded packets work with both versions though, so it seems like a udp-specific issue ? ---------------------------------------------------------------------- >Comment By: Mike Frysinger (vapier) Date: 2008-08-19 01:35 Message: Logged In: YES user_id=114429 Originator: YES my udp tftp server still works with that version ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-08-17 16:56 Message: Logged In: YES user_id=579204 Originator: NO Vapier, on the 0.7.3-2 was an error with DNS, related from the change for the bug you opened. I was changing the UDP receiver source again to handle both casees correctly. Check the working tftp server with this update please: http://www.henrynestler.com/colinux/testing/stable-0.7.3/20080817-slirp/colinux-slirp-net-daemon-0.7.3-3.zip ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-06-27 16:39 Message: Logged In: YES user_id=579204 Originator: NO Some lines in source was missing to change between SVN revisions 479 and 480, you have mailed me. Many thanks for your details. Bug has been fixed in SVN revision 1060 (stable) and 1061 (devel) now. An update colinux-slirp-net-daemon-0.7.3-2.zip is available from SF file releases: http://downloads.sourceforge.net/colinux/coLinux-0.7.2-src.tar.gz?download ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1995862&group_id=98788 |
From: SourceForge.net <no...@so...> - 2008-08-18 19:59:40
|
Bugs item #2046284, was opened at 2008-08-11 11:07 Message generated for change (Comment added) made by p_rouse You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2046284&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.7.x (release) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Paul Rouse (p_rouse) Assigned to: Henry N. (henryn) Summary: Slirp built-in DNS broken by 0.7.3-2 Initial Comment: The built-in DNS on 10.0.2.3 in slirp appears to have been broken by the update 0.7.3-2 to colinux-slirp-net-daemon.exe to fix bug 1995862 ("udp forwarded packets over slirp have incorrect source ip"). The issue is that the reply packets to the DNS requests now appear to come from the real DNS server, rather than the virtual one on 10.0.2.3. With the original 0.7.3 release tcpdump gives: 11:44:02.799135 IP 10.0.2.15.32772 > 10.0.2.3.53: 38764+ A? sourceforge.net. (33) 11:44:02.809134 IP 10.0.2.3.53 > 10.0.2.15.32772: 38764 1/0/0 A 216.34.181.60 (49) With the updated slirp daemon tcpdump shows: 11:49:45.149746 IP 10.0.2.15.32776 > 10.0.2.3.53: 23720+ A? sourceforge.net. (33) 11:49:45.149746 IP 172.21.1.201.53 > 10.0.2.15.32776: 23720 1/0/0 A 216.34.181.60 (49) 11:49:45.149746 IP 10.0.2.15 > 172.21.1.201: ICMP 10.0.2.15 udp port 32776 unreachable, length 85 Surely the original behaviour is what you want in the special case of DNS on 10.0.2.3. I am using a static configuration for the slirp interface, giving 10.0.2.3 explicitly as the DNS server, and the address 172.21.1.201 is the real DNS server which Windows is using. ---------------------------------------------------------------------- >Comment By: Paul Rouse (p_rouse) Date: 2008-08-18 19:59 Message: Logged In: YES user_id=260279 Originator: YES Thank you -- yes, that solves the DNS problem. I don't have a test for Bug #1995862 (that was someone else's) so I won't comment on that. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-08-17 20:55 Message: Logged In: YES user_id=579204 Originator: NO Ok, I see. Thanks for reporting. This should fix it: http://www.henrynestler.com/colinux/testing/stable-0.7.3/20080817-slirp/colinux-slirp-net-daemon-0.7.3-3.zip Hope the Bug #1995862 is working too now. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2046284&group_id=98788 |
From: SourceForge.net <no...@so...> - 2008-08-18 07:15:03
|
Bugs item #2055697, was opened at 2008-08-17 15:45 Message generated for change (Comment added) made by riteshsarraf You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2055697&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.7.x (release) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Ritesh Raj Sarraf (riteshsarraf) Assigned to: Nobody/Anonymous (nobody) Summary: colinux slirp daemon keeps crashing Initial Comment: I'm using coLinux (andLinux precisely) to use my favorite torrent app, ktorrent. Many of the times, coLinux keeps crashing in colinux-slirp-daemon.exe I'll attach the crash logs. ---------------------------------------------------------------------- >Comment By: Ritesh Raj Sarraf (riteshsarraf) Date: 2008-08-18 12:45 Message: Logged In: YES user_id=382018 Originator: YES I just looked into Event Viewer. There is nothing logged related to coLinux. :-( ---------------------------------------------------------------------- Comment By: Ritesh Raj Sarraf (riteshsarraf) Date: 2008-08-18 12:31 Message: Logged In: YES user_id=382018 Originator: YES THank you. I tried that. But Windows didn't allow me to copy paste that particular data. I'll see again to figure out how more info can be extracted. From my use, I can say is that colinux-slirp-daemon.exe is at fault. It keeps crashing very often. The crash is triggered especially when heavy network is done (I can't define how heavy. For me it was just a torrent app with 50-60k bandwidth utilization). Crashes are ugly and bad. So I moved to native coLinux (I was using andLinux). Now, I've configured my network with WinPCAP in Bridged mode. My setup is now running for 12+ hours without any problems. I'm still using the same applications. Hence, I'm sure it is a bug with colinux-slirp-daemon.exe. I'll try to reproduce the bug with the old setup once again and see if I can get the information that you're asking for. And btw, thank you very much for coLinux. It is one great application I can give to my Windows colleagues to enjoy Linux. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-08-17 19:05 Message: Logged In: YES user_id=579204 Originator: NO Hello Ritesh, the files you have send does not help to find the bug. It's a list of files only. We need informations about the crash position in the file, an instruction pointer or current cpu register values. One or more hexadecimal address numbers related to the colinux-slirp-net-daemon. Perhaps you would find such in your Windows event logger. Or, from the window, you have seen the crash, open the option "more details". ---------------------------------------------------------------------- Comment By: Ritesh Raj Sarraf (riteshsarraf) Date: 2008-08-17 15:46 Message: Logged In: YES user_id=382018 Originator: YES File Added: colinux-slirp-daemon-crash.txt ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2055697&group_id=98788 |
From: SourceForge.net <no...@so...> - 2008-08-18 07:01:06
|
Bugs item #2055697, was opened at 2008-08-17 15:45 Message generated for change (Comment added) made by riteshsarraf You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2055697&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.7.x (release) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Ritesh Raj Sarraf (riteshsarraf) Assigned to: Nobody/Anonymous (nobody) Summary: colinux slirp daemon keeps crashing Initial Comment: I'm using coLinux (andLinux precisely) to use my favorite torrent app, ktorrent. Many of the times, coLinux keeps crashing in colinux-slirp-daemon.exe I'll attach the crash logs. ---------------------------------------------------------------------- >Comment By: Ritesh Raj Sarraf (riteshsarraf) Date: 2008-08-18 12:31 Message: Logged In: YES user_id=382018 Originator: YES THank you. I tried that. But Windows didn't allow me to copy paste that particular data. I'll see again to figure out how more info can be extracted. From my use, I can say is that colinux-slirp-daemon.exe is at fault. It keeps crashing very often. The crash is triggered especially when heavy network is done (I can't define how heavy. For me it was just a torrent app with 50-60k bandwidth utilization). Crashes are ugly and bad. So I moved to native coLinux (I was using andLinux). Now, I've configured my network with WinPCAP in Bridged mode. My setup is now running for 12+ hours without any problems. I'm still using the same applications. Hence, I'm sure it is a bug with colinux-slirp-daemon.exe. I'll try to reproduce the bug with the old setup once again and see if I can get the information that you're asking for. And btw, thank you very much for coLinux. It is one great application I can give to my Windows colleagues to enjoy Linux. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-08-17 19:05 Message: Logged In: YES user_id=579204 Originator: NO Hello Ritesh, the files you have send does not help to find the bug. It's a list of files only. We need informations about the crash position in the file, an instruction pointer or current cpu register values. One or more hexadecimal address numbers related to the colinux-slirp-net-daemon. Perhaps you would find such in your Windows event logger. Or, from the window, you have seen the crash, open the option "more details". ---------------------------------------------------------------------- Comment By: Ritesh Raj Sarraf (riteshsarraf) Date: 2008-08-17 15:46 Message: Logged In: YES user_id=382018 Originator: YES File Added: colinux-slirp-daemon-crash.txt ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2055697&group_id=98788 |
From: coLinux a. <col...@he...> - 2008-08-18 04:07:16
|
The autobuild system has detected a new revision in the source repository. Review last changed from changelog.txt, also attached in mail. Download the compiled version: http://www.henrynestler.com/colinux/autobuild/devel-20080817/ colinux-0.8.0-20080817.src.tgz (692294 Bytes) daemons-0.8.0-20080817.dbg.zip (1348609 Bytes) daemons-0.8.0-20080817.zip (1046596 Bytes) Note, the autobuild compilation does not include an installer. Remember to reload the driver with these commands: colinux-daemon.exe --remove-driver colinux-daemon.exe --install-driver The vmlinux and modules are up to date. Please use last version from http://www.henrynestler.com/colinux/autobuild/devel-20080727/ The autobuild compilations are not official releases of Cooperative Linux software. There is no warranty that any autobuild version is stable. If use this autobuild version, please give us feedback of your experience. Job runs on machine with 64 bit version of gcc 4.1.2. A service from http://gcc.gnu.org/wiki/CompileFarm -- Lots of fun with newest version, Henry Nestler ------------------------------------------------------------------------ r1112 | henryn | 2008-08-17 21:05:05 +0000 (Sun, 17 Aug 2008) | 1 line Changed paths: M /branches/devel/src/colinux/user/slirp/udp.c * Bug #2046284: DNS resolver answers from 10.0.2.3, hide real DNS ------------------------------------------------------------------------ |
From: SourceForge.net <no...@so...> - 2008-08-17 20:56:19
|
Bugs item #1995862, was opened at 2008-06-17 11:33 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1995862&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.7.x (release) >Status: Open Resolution: Fixed Priority: 5 Private: No Submitted By: Mike Frysinger (vapier) Assigned to: Nobody/Anonymous (nobody) Summary: udp forwarded packets over slirp have incorrect source ip Initial Comment: after upgrading from coLinux 0.7.1 to 0.7.3, my TFTP connection failed. the coLinux setup is: eth0=slirp,,tcp:22:22/tcp:333:22/tcp:10000:10000/udp:69:69 connecting from an external machine (named "G5") to the windows machine which forwards port 69 (tftp) to the colinux system which is running a tftp server running tcpdump against 0.7.1 shows: 01:34:47.410000 IP G5.60808 > 10.0.2.15.tftp: 15 RRQ "moo" netascii running tcpdump against 0.7.3 shows: 01:44:45.645802 IP 10.0.2.2.33431 > 10.0.2.15.tftp: 15 RRQ "moo" netascii for some reason the forwarded packet had the source IP changed from the real external machine (G5) to the windows' side of the slirp tunnel (10.0.2.2). this means the tftp server then attempts to reply to "10.0.2.2" instead of "G5" and things obviously fail. merely replacing 'colinux-slirp-net-daemon.exe' in 0.7.3 with the version from 0.7.1 allows things to work as expected under 0.7.3 tcp forwarded packets work with both versions though, so it seems like a udp-specific issue ? ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2008-08-17 22:56 Message: Logged In: YES user_id=579204 Originator: NO Vapier, on the 0.7.3-2 was an error with DNS, related from the change for the bug you opened. I was changing the UDP receiver source again to handle both casees correctly. Check the working tftp server with this update please: http://www.henrynestler.com/colinux/testing/stable-0.7.3/20080817-slirp/colinux-slirp-net-daemon-0.7.3-3.zip ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-06-27 22:39 Message: Logged In: YES user_id=579204 Originator: NO Some lines in source was missing to change between SVN revisions 479 and 480, you have mailed me. Many thanks for your details. Bug has been fixed in SVN revision 1060 (stable) and 1061 (devel) now. An update colinux-slirp-net-daemon-0.7.3-2.zip is available from SF file releases: http://downloads.sourceforge.net/colinux/coLinux-0.7.2-src.tar.gz?download ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1995862&group_id=98788 |
From: SourceForge.net <no...@so...> - 2008-08-17 20:55:55
|
Bugs item #2046284, was opened at 2008-08-11 13:07 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2046284&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.7.x (release) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Paul Rouse (p_rouse) >Assigned to: Henry N. (henryn) Summary: Slirp built-in DNS broken by 0.7.3-2 Initial Comment: The built-in DNS on 10.0.2.3 in slirp appears to have been broken by the update 0.7.3-2 to colinux-slirp-net-daemon.exe to fix bug 1995862 ("udp forwarded packets over slirp have incorrect source ip"). The issue is that the reply packets to the DNS requests now appear to come from the real DNS server, rather than the virtual one on 10.0.2.3. With the original 0.7.3 release tcpdump gives: 11:44:02.799135 IP 10.0.2.15.32772 > 10.0.2.3.53: 38764+ A? sourceforge.net. (33) 11:44:02.809134 IP 10.0.2.3.53 > 10.0.2.15.32772: 38764 1/0/0 A 216.34.181.60 (49) With the updated slirp daemon tcpdump shows: 11:49:45.149746 IP 10.0.2.15.32776 > 10.0.2.3.53: 23720+ A? sourceforge.net. (33) 11:49:45.149746 IP 172.21.1.201.53 > 10.0.2.15.32776: 23720 1/0/0 A 216.34.181.60 (49) 11:49:45.149746 IP 10.0.2.15 > 172.21.1.201: ICMP 10.0.2.15 udp port 32776 unreachable, length 85 Surely the original behaviour is what you want in the special case of DNS on 10.0.2.3. I am using a static configuration for the slirp interface, giving 10.0.2.3 explicitly as the DNS server, and the address 172.21.1.201 is the real DNS server which Windows is using. ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2008-08-17 22:55 Message: Logged In: YES user_id=579204 Originator: NO Ok, I see. Thanks for reporting. This should fix it: http://www.henrynestler.com/colinux/testing/stable-0.7.3/20080817-slirp/colinux-slirp-net-daemon-0.7.3-3.zip Hope the Bug #1995862 is working too now. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2046284&group_id=98788 |
From: SourceForge.net <no...@so...> - 2008-08-17 13:35:06
|
Bugs item #2055697, was opened at 2008-08-17 12:15 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2055697&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.7.x (release) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Ritesh Raj Sarraf (riteshsarraf) Assigned to: Nobody/Anonymous (nobody) Summary: colinux slirp daemon keeps crashing Initial Comment: I'm using coLinux (andLinux precisely) to use my favorite torrent app, ktorrent. Many of the times, coLinux keeps crashing in colinux-slirp-daemon.exe I'll attach the crash logs. ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2008-08-17 15:35 Message: Logged In: YES user_id=579204 Originator: NO Hello Ritesh, the files you have send does not help to find the bug. It's a list of files only. We need informations about the crash position in the file, an instruction pointer or current cpu register values. One or more hexadecimal address numbers related to the colinux-slirp-net-daemon. Perhaps you would find such in your Windows event logger. Or, from the window, you have seen the crash, open the option "more details". ---------------------------------------------------------------------- Comment By: Ritesh Raj Sarraf (riteshsarraf) Date: 2008-08-17 12:16 Message: Logged In: YES user_id=382018 Originator: YES File Added: colinux-slirp-daemon-crash.txt ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2055697&group_id=98788 |
From: SourceForge.net <no...@so...> - 2008-08-17 10:16:24
|
Bugs item #2055697, was opened at 2008-08-17 15:45 Message generated for change (Comment added) made by riteshsarraf You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2055697&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.7.x (release) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Ritesh Raj Sarraf (riteshsarraf) Assigned to: Nobody/Anonymous (nobody) Summary: colinux slirp daemon keeps crashing Initial Comment: I'm using coLinux (andLinux precisely) to use my favorite torrent app, ktorrent. Many of the times, coLinux keeps crashing in colinux-slirp-daemon.exe I'll attach the crash logs. ---------------------------------------------------------------------- >Comment By: Ritesh Raj Sarraf (riteshsarraf) Date: 2008-08-17 15:46 Message: Logged In: YES user_id=382018 Originator: YES File Added: colinux-slirp-daemon-crash.txt ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2055697&group_id=98788 |
From: SourceForge.net <no...@so...> - 2008-08-17 10:15:32
|
Bugs item #2055697, was opened at 2008-08-17 15:45 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2055697&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.7.x (release) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Ritesh Raj Sarraf (riteshsarraf) Assigned to: Nobody/Anonymous (nobody) Summary: colinux slirp daemon keeps crashing Initial Comment: I'm using coLinux (andLinux precisely) to use my favorite torrent app, ktorrent. Many of the times, coLinux keeps crashing in colinux-slirp-daemon.exe I'll attach the crash logs. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2055697&group_id=98788 |