Menu
▾
▴
colinux-users
|
From: Alain <whi...@fr...> - 2005-02-09 09:20:10
|
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
|
|
From: Sam M. <pa...@gm...> - 2005-02-09 09:58:46
|
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 > |
|
From: Alain <whi...@fr...> - 2005-02-09 10:48:39
|
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 |
|
From: Holger K. <hol...@gm...> - 2005-02-09 10:53:18
|
> 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. |
|
From: Ian B. <ib...@gm...> - 2005-02-09 13:00:50
|
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 > |
|
From: Holger K. <hol...@gm...> - 2005-02-09 13:27:54
|
> 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. > Maybe this could be achieved by installing several tap devices in Windows and create the required subnets by bridgeing them. But i did not try this. |
|
From: Ian B. <ib...@gm...> - 2005-02-09 14:00:51
|
Actually, that sounds like it would have the desired effect. Install about 5 TAP devices, run 5 coLinuxes, and then bridge on the Windows side.. not a bad idea. In theory, it sounds sane. Ian On Wed, 09 Feb 2005 14:27:47 +0100, Holger Krull <hol...@gm...> wrote: > > 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. > > > > Maybe this could be achieved by installing several tap devices in Windows and create the required subnets by bridgeing them. But i did not try this. > > |
|
From: Alexander S. <20...@us...> - 2005-02-09 18:57:34
|
On Wed, 09 Feb 2005 10:20:13 +0100, Alain wrote: > How can I create the network connexions in the colinux subnet ? Bridging to the MS Loopback adapter using PCAP should work fine. (and does not need several TAP instances) Kind regards, Alexander |
|
From: Ian B. <ib...@gm...> - 2005-02-09 20:47:28
|
So you're saying to make all the colinux instances bridge to the loopback adapter, and then assign a .1 address or something on the Windows side and they sohuld all see each other? Ian On Wed, 9 Feb 2005 19:57:20 +0100, Alexander Schremmer <20...@us...> wrote: > On Wed, 09 Feb 2005 10:20:13 +0100, Alain wrote: > > > How can I create the network connexions in the colinux subnet ? > > Bridging to the MS Loopback adapter using PCAP should work fine. > (and does not need several TAP instances) > > Kind regards, > Alexander > > > ------------------------------------------------------- > 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 > |
|
From: Alexander S. <20...@us...> - 2005-02-09 20:59:40
|
On Wed, 9 Feb 2005 15:47:11 -0500, Ian Bonnycastle wrote: > So you're saying to make all the colinux instances bridge to the > loopback adapter, and then assign a .1 address or something on the > Windows side and they sohuld all see each other? Exactly. If I understand the bridging concept correctly, this should work. Kind regards, Alexander |
|
From: Ian B. <ib...@gm...> - 2005-02-09 22:32:06
|
Ok, cool, I'll give that a whirl sometime. Ian On Wed, 9 Feb 2005 21:59:28 +0100, Alexander Schremmer <20...@us...> wrote: > On Wed, 9 Feb 2005 15:47:11 -0500, Ian Bonnycastle wrote: > > > So you're saying to make all the colinux instances bridge to the > > loopback adapter, and then assign a .1 address or something on the > > Windows side and they sohuld all see each other? > > Exactly. If I understand the bridging concept correctly, this should work. > > Kind regards, > Alexander > > ------------------------------------------------------- > 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 > |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X