Re: [coLinux-users] vnc step by step needed

[baldyeti <e_...@ho...>]

I know there are several ways to setup networking for
colinux and the instructions on the wiki can be confusing.
As I said, I think your windows tun/tap address should be
on the same IP subnetwork as your virtual linux.

In my case I have

C:\temp>ipconfig /all
...
Ethernet adapter tuntap:
         Description . . . . . . . . . . . : TAP-Win32 Adapter V8 (coLinux)
         Physical Address. . . . . . . . . : 00-FF-77-A4-F2-4C
         Dhcp Enabled. . . . . . . . . . . : No
         IP Address. . . . . . . . . . . . : 192.168.0.1
         Subnet Mask . . . . . . . . . . . : 255.255.255.0
         Default Gateway . . . . . . . . . :

shoebox:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:ff:39:6d:48:00
           inet addr:192.168.0.106  Bcast:192.168.0.255
...

So: for me 192.168.0.x is the virtual IP network through
which host and guest communicate. In your case, either change
	the tun/tap address to 10.0.2.xxx
	or the linux addresss to 192.168.37.yyy

On the windows side you also need to enable connection sharing of
your main (physical) connection (10.252.248.152)

On 21/08/2009 22:50, Ben Brannen wrote:
> Looks like we are getting closer.  I can't ping colinux from windows.
> 
> colinux:~# ping 10.252.248.152
> PING 10.252.248.152 (10.252.248.152) 56(84) bytes of data.
> 64 bytes from 10.252.248.152: icmp_seq=1 ttl=255 time=30.0 ms
> 
> C:\>ping 10.0.2.15
> Pinging 10.0.2.15 with 32 bytes of data:
> Request timed out.
> ...
> Ping statistics for 10.0.2.15:
>     Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
> 
> -ben
>