Re: [coLinux-users] Simulating a whole subnet

[Sam M. <pa...@gm...>]

It would be much easier to run the Windows machine to do everything
you want colinux1 to do, that way you just run multiple coLinux
processes (and installations) and set up Windows to bridge every
single one of the lan connections (you'd need to create multiple lan
devices and get coLinux to network properly).

The other solution is to run coLinux from within coLinux. Essentially
the same as before, but instead of 'bridging' the connections, just
use a bit of Linux routing and network configuration to achieve what
your after. You would make sure each 'sub-coLinux' process connected
to the parent coLinux process as a different network device (ie eth0
would be its connection to Windows, eth1 would be coLinux2, eth2 would
be coLinux3, etc). That way they appear as different Linux boxes
connecting to the parent, eth0 is the default gateway and you perform
what you want on coLinux1.

This is the only way to run things, and this is complicated, so I'd be
tempted to put it into the too hard basket. coLinux isn't designed to
run in this manner, but if you like, you could try to make it that
way. VirtualPC supports this kind of functionality if you are
seriously interested (and it is much easier to implement).

Also, coLinux on coLinux could raise some issues as well. The first
solution would be the best IMHO.

Sam

On Wed, 09 Feb 2005 10:20:13 +0100, Alain <whi...@fr...> wrote:
> Hello,
> 
> I have various instances of colinux (0.6.1) working at the same time
> under windows XP. They are connected to Windows using a bridge. I would
> like to organise them differently, in order to simulate the topology of
> a real network connected to the Internet:
> 
> Internet ------ Windows ------- colinux1 ---+--- colinux2
>                 NAT             NAT         |
>                 firewall        firewall    +--- colinux3
>                                             |
>                                             +--- colinux4
> 
>  From the point of view of the colinux stations, Windows would be in the
> Internet zone (like an ISP proxy or so). Colinux1 is the firewall and
> server of the colinux stations subnet: it does NAT masquerading, DHCP,
> HTTP, etc...
> 
> How can I create the network connexions in the colinux subnet ?
> 
> Best regards
> 
> Alain
> 
> --
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.300 / Virus Database: 265.8.6 - Release Date: 07/02/2005
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>