I`d like to know your opinion on a following solution: small and basic coLinux debian distro functioning as a virtual router for Windows box running that coLinux. I was inspired by: http://colinux.wikia.com/wiki/Network#Keep_Windows_off_the_network_--_surf_via_Linux

Would it be possible to force all Windows traffic to coLinux machine and through it, to Internet? Can we achieve total separation of windows box, like with hardware router box used? Would it be resource-wise in regard of cpu/mem and hdd space usage, comparing to native Windows software firewall/IDS solutions?

Kind regards

Olaf Siejka

2008/7/7, colinux-users-request@lists.sourceforge.net <colinux-users-request@lists.sourceforge.net>:
Send coLinux-users mailing list submissions to

To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to

You can reach the person managing the list at

When replying, please edit your Subject line so it is more specific
than "Re: Contents of coLinux-users digest..."

Today's Topics:

   1. port forwarding problem at colinux (Menghan Zheng)
   2. Re: port forwarding problem at colinux
      (Josep Maria Antol?n Segura)


Message: 1
Date: Mon, 07 Jul 2008 23:26:55 +0800
From: Menghan Zheng <thuskyblue@gmail.com>
Subject: [coLinux-users] port forwarding problem at colinux
To: colinux-users@lists.sourceforge.net
Message-ID: <487235BF.7020608@gmail.com>
Content-Type: text/plain; charset=GB2312

I installed Debian/testing on windows xp sp3
I config my networks like this:

on XP: I have a static ip:
on Debian: my /etc/network/interfaces is like:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static

I installed virtual network adapter as the tuntap way
eth1=tuntap(from example.conf)

then all goes well, colinux could connect www.google.com, and my XP can
connect my colinux
But now i have to start a service in my colinux at port 23(you're right,
it's telnet).I want to share the service to the IPs outside my local
that is to say: ip( can telnet my colinux at port 23.
how should i config my colinux network?

//I'm sorry for my poor English.

Keep In Touch!
Electronics Engineering Department, Tsinghua University

Dorm Tel: 8610 5153 4319
Mobile: 86 13401088180
MSN: zhengmenghan0010@hotmail.com
Email: zhengmenghan0010@gmail.com, zmh05@mails.tsinghua.edu.cn


Message: 2
Date: Mon, 07 Jul 2008 19:17:29 +0200
From: Josep Maria Antol?n Segura <jaz@pastnotecut.org>
Subject: Re: [coLinux-users] port forwarding problem at colinux
To: Menghan Zheng <thuskyblue@gmail.com>
Cc: colinux-users@lists.sourceforge.net
Message-ID: <1215451049.48724fa97d8d2@imp4.online.net>
Content-Type: text/plain; charset=ISO-8859-1

Your configuration is a bit unusual, (meaning that some of the solutions do not
apply to you), yet there are still possibilities:

First of all, your configuration only allows you to use colinux via NAT, because
else, you would need a secondary *internet* IP for it.

Usually, a router would do the NAT for you, so you would redirect packets
entering a specific port to the colinux machine. In your case, you need a
software NAT package installed in Windows, which would then map the ports. And
you're lucky: there's a mode of colinux that let's you do it: "Slirp".


Briefly: you need to specify in the config file, the ports that you need to
access from internet, and configure linux as dhcp (or static, with the info on
that page)

Note that the slirp-net-daemon shipped with the current stable release has a
minor isssue with packets, and there's an updated on on sourceforge


  _ _  /~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-\
  o o  | Josep Ma [JAZ]                 |
  *   | ICQ UIN: 7014661               |
  `-?  | Messenger: jazet_e@hotmail.com |


Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08


coLinux-users mailing list

End of coLinux-users Digest, Vol 27, Issue 3