Re: [coLinux-users] Simulating a whole subnet

[Ian B. <ib...@gm...>]

I mentioned this in another email, but I'm surprised the TAP device
doesn't have this functionality. I.E. A TAP device in Windows should
be able to communicate with a TAP device in ANY coLinux instance. That
way, if you program Window's TAP device with 192.168.10.1/24, and then
all the coLinuxes with 192.168.10.x/24 addresses on their ethernet
ports, they should all be able to talk to 192.168.10.1/24 and each
other flawlessly. Unless, of course, there is contention between each
coLinux and the Window's TAP device. (I.E. only one piece of software
at a time can connect to Window's TAP device). If this ISN'T
implemented, it would be worth it to take some serious looking at.

Ian

On Wed, 09 Feb 2005 11:53:10 +0100, Holger Krull <hol...@gm...> wrote:
> >  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 ?
> >
> Maybe use more than one network card in your host? I don't think you can setup virtual routing in colinux.
> 
> 
> -------------------------------------------------------
> 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
>