From: <ch...@to...> - 2004-03-23 16:25:17
|
This may be possible. I do not think that it is possible to have more than 1 virtual nic on coLinux yet but It probably does not matter because you are not limited by the speed of the hardware. So an alias on the 1 nic is probably good. ifconfig eth0 realPublicIpAddress netmask ..... ifconfig eth0:1 192.168.0.1 enable everything to foreward for now setup 2 TAP interfaces on windows one to do an native bridge to eth0 and the other to eth0:1 and only give windows a 192.168.0.? address and setup 192.168.0.1 as the windows gateway. You may want to try to create an image of smoothwall or another router type distro to make things easy you want to be able to toggle easily between pass everything and block everything while trying to get this configured check out some of the howto's on tldp.org for some networking info just making some guesses here I have not tried any of this chris > Hi, i've been playing with CoLinux and i've been thinking about how one > would configure a windows-colinux with a single public IP so that the > public IP was assigned to colinux. Then it (colinux) would share (NAT) > internet access to windows. That would effectivelly provide a Linux > Firewall, which can be configured with fun things like packet shaping and > all, in a Windows box with (i believe) little overhead for normal > DSL/Cable speeds. Having a computer services company of my own i could see > myself selling some form of this solution. Any ideas? > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id70&alloc_id638&opïick > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |