From: raghukisore <nra...@gm...> - 2013-01-08 03:46:03
|
All the manual available on net put eth0 and eth1 on different subnets. while eth0 slirp is for connecting colinux to web...for services like wget, apt-get, and eth1 tuntap is for connecting to host computer. I am starting the colinux using a script file name start-Fedora-10.sh that came along during the colinux set up process. I selected the Fedora 10 option during the installation process. The documentation says all networking should be up and running automatically. But i already spent 8-10 days and still cannot get the communication from host computer to colinux side.. everything else seems to be fine. i mean i am able to launch apps (like fedora, gvim, xeyes, xterm, kscope, gnome-session etc) on colinux side and see the interface on my host computer. but i am not able to set up ssh or scp session (winscp) from host to colinux side. Basically, I am not able to ping either eth0 or eth1 interfaces from host computer. I am not sure if this has something to do with correct;y configuring the following setting inside start-Fedora-10.sh eth0=slirp,,tcp:5900:5900 ro \ eth1=tuntap,,tcp:5900:5900 ro The above 2 lines have something to do with port mapping to in comming requests. I just need some way to move files between host and colinux filesystem. I tried samba share. did not work as colinux 0.7.9 somehow doesn't recognize cofs file system. Alternatively is there any way to use USB drive to copy files between the two File systems?? Thanks Raghu. Arturo R. wrote: > > On Thu, Jan 3, 2013 at 9:35 PM, raghukisore <nra...@gm...> > wrote: > > <snip> > > >> Here is the my eth0 and eth1 configuration for reference. >> >> /etc/sysconfig/network-scripts/ifcfg-eth0 >> DEVICE=eth0 >> IPADDR=10.0.2.15 >> NETMASK=255.255.255.0 >> BOOTPROTO=static >> ONBOOT=yes >> TYPE=Ethernet >> BROADCAST=10.0.2.255 >> GATEWAY=10.0.2.2 >> >> > <snip> > > >> windows TAP-WIN32 Adapter V8 setting are >> IP Address: 10.0.3.17 >> subnet mask: 255.255.254.0 >> > > I don't have a lot of networking knowledge, but I think the IP for your > TAP-WIN32 adapter should be in the 10.0.2.x subnet in order to be able to > reach the internal coLinux services. > > -- > Arturo R. > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. SALE $99.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122412 > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > > -- View this message in context: http://old.nabble.com/Connecting-to-Fedora10-on-CoLinux-from-Host-operating-system-%28Windows-7%29-using-VNC-viewer-tp34857793p34871586.html Sent from the colinux-users mailing list archive at Nabble.com. |