Re: [coLinux-users] Simulating a whole subnet

[Alain <whi...@fr...>]

Thank you for your answer Sam,

I am surprised reading it is a hard task.
The simpliest case should simulate a point to point physical connexion 
between two virtual ethernet cards (merely an asynchronous buffer ?). A 
more difficult case would be to simulate a bridge (like a software HUB 
or basic switch). I suppose that if this is not already done, the pieces 
of software necessary to do this could derivate from existing projects. 
Am I wrong ? Has anyone suggestions to do this ?

Alain

Sam Moffatt wrote:
> 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


-- 
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