From: Anders E. C (KI/EAB) <and...@er...> - 2004-09-01 07:22:00
|
Dont put them all on the 192.168.0/24 subnet. That makes the routing from one colinux to the other (virtually) impossible. Make one colinux live on 192.168.1/24, the other on 192.168.2/24, and tell the "1" colinux to route to the other via host 2., i.e. route add 192.168.2.0 netmask 255.255.255.0 gw 192.168.0.45 (if host has that ip address on the "0" backbone). hth, /A -----Original Message----- From: col...@li... [mailto:col...@li...]On Behalf Of Vijay Velusamy Sent: den 31 augusti 2004 23:15 To: col...@li... Subject: [coLinux-users] Communicaton between virtual machines I have installed colinux (with Fedora core 1) on two of my desktops at home (essentially I got one working, and copied hard-disk image overm and changed the IP settings). I am able to reach both the virtual machines from either hostmachine (ping), however, I am unable to ping between the virtual machines. For example, say the host machines have IP addresses 192.168.0.199, 192.168.0.198 and the virtual machines have 192.168.0.150, 192.168.0.151. I am able to ping from 199 & 198 to 150 and 151. But I am not able to ping between 150 & 151 itself. Any ideas on what might be the issue here? TIA Vijay ----- Original Message ----- From: <ti...@fu...> To: "mohan" <Mo...@va...> Cc: "Claude LeFrancois (QB/EMC)" <cla...@er...>; <col...@li...> Sent: Thursday, August 26, 2004 3:16 AM Subject: RE: [coLinux-users] NFS performance and colinux > > This is general what I do to get X and colinux working. > - Install cygwin with X (or full cygwin, takes a bit longer) > - Open cygwin shell and start the X server with 'X <options>' > > I use the following options > -ac No authentication required > -multiwindow Use windows desktop as window manager, works fine > and faster than using extra X window manager > -clipboard Clipboard is not enabled by default > -nodecoration I'm not sure if this makes any sense with -multiwindow > -xkblayout fi I'm from Finland.. > -xkblayout pc105 Supposedly helps to get some keys working > -xkbvariant nodeadkeys > -xkbrules xfree86 > > If you google "cygwin X" then you can find better description of some of > these parameters. However, not for -ac, because it is 'standard' X server > parameter, for that, and another option -query, you need to consult "man > X" perhaps, on system that has that man page. Or google. > > I also add & to the end so that I can use the cygwin shell for other > things. > > In the colinux side, you just install the X programs and run them > with DISPLAY=192.168.1.1:0.0, for example: > > DISPLAY=192.168.1.1:0.0 xterm & > > You will need -ac, or -query. With -query 192.168.1.1 you will probably > need to install gdm or similar display manager to colinux system. That > IMHO is quite waste while -ac -multiwindow works just fine and you don't > have to install lots of packages just to get X working. > > > Is there any documentation guide on 2.6.7 kernel (debian/fedora) using > > colinux 2.6.7 with x-server. Appreciate if someone in this group can > > assist me in getting it to work for me. > > > -- > timo > > > > ------------------------------------------------------- > SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 > Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users |
From: Tomas F. <to...@eu...> - 2004-09-01 23:56:05
|
Anders Eriksson C (KI/EAB) wrote: > Dont put them all on the 192.168.0/24 subnet. That makes the > routing from one colinux to the other (virtually) impossible. Unless you use "bridged" mode, of course, in which case routing should not be issue and everything can cooperate on the same subnet. > Make one colinux live on 192.168.1/24, the other on 192.168.2/24, > and tell the "1" colinux to route to the other via host 2., i.e. > route add 192.168.2.0 netmask 255.255.255.0 gw 192.168.0.45 (if > host has that ip address on the "0" backbone). This is why I love the "bridged" capability; less complicated ;) // Tomas |